Claude Cursor Skill

looking-up-docs

Imported from alexei-led/cc-thingz/dist/pi/skills/looking-up-docs.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download alexei-led-cc-thingz-dist_pi_skills_looking-up-docs-0a6445b.zip · 3 KB

Install

skills CLI npx skills add https://github.com/alexei-led/cc-thingz/tree/master/dist/pi/skills/looking-up-docs
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install alexei-led-cc-thingz@llmmart
Git git clone https://github.com/alexei-led/cc-thingz.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole alexei-led/cc-thingz collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Documentation Lookup

Answer API, syntax, and config questions from version-correct sources. When a lookup tool is available, do not answer syntax from memory.

Never put secrets, credentials, personal data, private payloads, or proprietary code into an external query. Strip them and still look up the public docs; if the question cannot be asked without them, answer from local context and say so.

Lookup chain

Stop at the first tier that grounds the answer.

  • Tier 0, version: find the exact package and version from manifests, lockfiles, or tool output. If there is none, say version unknown and use the latest stable docs. Never invent a version.
  • Tier 1, Context7: follow references/context7-cli.md. Treat Tier 1 as exhausted when Context7 is unavailable, rate-limited, returns the wrong version, or finds nothing after one rephrase and one alternate library name.
  • Tier 2, official docs and registries: use references/official-sources.md. Use web search only to discover primary sources (the researching-web skill covers platform web tools), then cite the primary URL.
  • Tier 3, GitHub: releases, tags, and source at the matching tag, when docs are missing, incomplete, or version-mismatched. Issues, PR comments, blogs, and generated summaries are clues, not authority.
  • Tier 4, gap report: state the version needed versus found, what you tried, and the safest next step. Do not fabricate syntax.

If the request turns into a comparison, current-state, or release-behavior question, hand it to researching-web and offer a docs lookup for the chosen library afterwards.

Response

Give the answer, not a transcript of the lookup, unless the user asks for the process. Include:

  1. Library and version, or version unknown.
  2. The tier that produced the answer and any fallback used.
  3. Syntax or example grounded in the source.
  4. A source URL, Context7 library ID, or GitHub tag and path for each claim.
Files (cc-thingz)
  • references
    • context7-cli.md 1.1 KB
      Loading…
    • official-sources.md 2 KB
      Loading…
  • SKILL.md 3 KB
    ---
    {"description":"Find exact, version-correct library/API/framework docs through one lookup workflow. Use when the user says \"look up docs\", \"how to use\", \"API for\", \"syntax for\", \"examples of\", \"show me the docs\", mentions \"ctx7\"/\"Context7\", passes a `/org/project` library ID, or needs API signatures, config keys, syntax, examples, or versioned docs. NOT for comparisons, current-state or release-behavior questions, best-practice surveys, or recent ecosystem news — use researching-web.","name":"looking-up-docs"}
    ---
    <!-- Pi platform guidance -->
    <!-- Use installed tool names. Discover callable tools before batching independent calls in codemode; model-only UI/orchestration tools must be called directly. -->
    <!-- Read required skill/instruction files through direct read when exposed or through Code Mode. If an optional pruning extension is installed, verify its output protection semantics; do not assume nested-path protection. Code Mode composes calls; subagents or controllers own durable workflows. Async subagents notify natively: yield rather than poll. -->
    
    
    # Documentation Lookup
    
    Answer API, syntax, and config questions from version-correct sources. When a
    lookup tool is available, do not answer syntax from memory.
    
    Never put secrets, credentials, personal data, private payloads, or proprietary
    code into an external query. Strip them and still look up the public docs; if
    the question cannot be asked without them, answer from local context and say
    so.
    
    ## Lookup chain
    
    Stop at the first tier that grounds the answer.
    
    - Tier 0, version: find the exact package and version from manifests,
      lockfiles, or tool output. If there is none, say `version unknown` and use
      the latest stable docs. Never invent a version.
    - Tier 1, Context7: follow [references/context7-cli.md](references/context7-cli.md).
      Treat Tier 1 as exhausted when Context7 is unavailable, rate-limited, returns
      the wrong version, or finds nothing after one rephrase and one alternate
      library name.
    - Tier 2, official docs and registries: use
      [references/official-sources.md](references/official-sources.md). Use web
      search only to discover primary sources (the researching-web skill covers
      platform web tools), then cite the primary URL.
    - Tier 3, GitHub: releases, tags, and source at the matching tag, when docs are
      missing, incomplete, or version-mismatched. Issues, PR comments, blogs, and
      generated summaries are clues, not authority.
    - Tier 4, gap report: state the version needed versus found, what you tried,
      and the safest next step. Do not fabricate syntax.
    
    If the request turns into a comparison, current-state, or release-behavior
    question, hand it to researching-web and offer a docs lookup for the chosen
    library afterwards.
    
    ## Response
    
    Give the answer, not a transcript of the lookup, unless the user asks for the
    process. Include:
    
    1. Library and version, or `version unknown`.
    2. The tier that produced the answer and any fallback used.
    3. Syntax or example grounded in the source.
    4. A source URL, Context7 library ID, or GitHub tag and path for each claim.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.