looking-up-docs

Name: looking-up-docs
Author: alexei-led

5installs5forks

How to install looking-up-docs?

alexei-led/cc-thingz/looking-up-docs

$npx -y skills add alexei-led/cc-thingz --skill looking-up-docs

Installs into the current project.

Summary

Get grounded, version-correct docs for a library, framework, CLI, or API. Never answer syntax or API questions from memory when lookup tools are available.

Files · 1

View on GitHub

SKILL.md

1	# Documentation Lookup
2
3	Get grounded, version-correct docs for a library, framework, CLI, or API.
4	Never answer syntax or API questions from memory when lookup tools are available.
5
6	## Scope
7
8	Use this skill for:
9
10	- API signatures, options, config keys, syntax, and examples.
11	- Versioned API behavior of a known library, framework, language, CLI, or
12	standard library when the question is how to call or configure it.
13	- Context7 docs lookup, including explicit `ctx7`, `Context7`, or `/org/project`
14	library-ID requests.
15	- Confirming versioned API behavior before writing code against an external API.
16
17	Do not use this skill for:
18
19	- Comparisons, recommendations, market research, current-state questions,
20	release-behavior questions, or best-practice surveys; route to `researching-web`.
21	- Repo-specific questions; search local files first.
22	- External queries containing secrets, credentials, personal data, private
23	payloads, or proprietary code.
24
25	## Reference Files
26
27	Read only what the question needs:
28
29	- `references/context7-cli.md` — Context7 lookup commands, selection rules,
30	limits, and fallbacks.
31	- `references/official-sources.md` — primary docs and registries by ecosystem.
32	- `references/web-tools.md` — platform web tools, query templates, and source
33	quality rules.
34
35	## Lookup Chain
36
37	Run tiers in order. Stop at the first tier that yields a grounded answer. State
38	which tier produced the answer and whether fallback was used.
39
40	### Tier 0 — Identify Package and Version
41
42	Find the exact package, module, CLI, language version, or framework version from
43	local evidence.
44
45	If no local version is available, state `version unknown` and prefer latest
46	stable official docs. Do not invent a version.
47
48	### Tier 1 — Context7
49
50	Use `references/context7-cli.md` for Context7 library resolution and docs fetch.
51	Best fit: versioned library and framework docs.
52
53	Escalate when Context7 is unavailable, rate-limited, returns no useful match
54	after one rephrase and one alternate library name, or returns docs for the wrong
55	version.
56
57	### Tier 2 — Official Docs and Registries
58
59	Use `references/official-sources.md` for language standard libraries, package
60	registries, and canonical project docs. Prefer primary docs or registry-linked
61	docs for the exact version.
62
63	Use web tools only for source discovery. Ground final syntax in URL-cited primary
64	sources.
65
66	### Tier 3 — GitHub Releases, Tags, and Source
67
68	Use GitHub only when primary docs or registry links are missing, incomplete, or
69	version-mismatched. Follow `references/official-sources.md` fallback rules.
70
71	Do not treat random issues, PR comments, blogs, or generated summaries as
72	authoritative API docs. Use them only as clues to primary sources.
73
74	### Tier 4 — Source Discovery or Gap Report
75
76	Use broad web research only to find primary docs after focused lookup fails. If
77	the question becomes a comparison, trade-off, current-state, or release-behavior
78	task, stop and route to `researching-web`. If no grounded source exists, report
79	the gap, the version needed vs found, and the safest next step.
80
81	## Limits and Failure Handling
82
83	- Never send secrets, credentials, private payloads, personal data, or
84	proprietary code to any external tier.
85	- Always use a real, specific query; never use a one-word placeholder.
86	- Do not loop a tier indefinitely: one rephrase and one alternate name per tier,
87	then escalate.
88	- If docs are version-mismatched, state the mismatch and escalate to exact-version
89	registry docs, release notes, or matching GitHub tag/source.
90	- If all tiers fail, report the gap and do not fabricate syntax.
91	- If external lookup would expose private data, refuse the external query and
92	answer from local context only, noting the limitation.
93
94	## Response Contract
95
96	Return a concise answer, not a workflow transcript, unless the user asks for the
97	lookup process.
98
99	Include:
100
101	1. Library/framework/API and version, or `version unknown`.
102	2. Tier that produced the answer, and fallback used if any.
103	3. Syntax or example guidance grounded in the source.
104	4. Source URL, Context7 library ID, or GitHub tag/source path for each claim.
105	5. Boundary note when the request is actually comparison, current-state,
106	release-behavior, or broad research.
107
108	If the user asks to describe the workflow, descr

People who liked this also viewed

6 picks

Type

grill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.SkillsJul 2026537k182k
lark-minutes飞书妙记：搜索妙记、查看妙记基础信息、下载/上传音视频、读取或编辑妙记的产物内容、改标题、替换说话人/关键词、申请妙记查看/编辑权限。当给出minute_token、本地音视频文件，要查/改/转妙记产物，或用户明确要主动申请妙记权限时使用；本地音视频转纪要/逐字稿优先走本 skill，不要用 ffmpeg/whisper 本地转写。不负责：获取会议关联妙记，或仅按自然语言标题定位纪要SkillsJul 2026379k16k
lark-markdown飞书 Markdown：查看、创建、上传、编辑和比较 Markdown 文件。当用户需要创建或编辑 Markdown 文件、读取、修改、局部 patch 或比较差异时使用。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。SkillsJul 2026295k16k
docxUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', SkillsJul 2026157k163k
edit-articleSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026154k181k
lark-note飞书会议纪要（Note）直查：已知 note_id 时查询纪要详情、展示类型、关联文档 token，并读取 unified 原始逐字记录。当用户已持有 note_id，或从文档显式 vc-node-id 获得 note_id 时使用。不负责会议/日程/妙记定位、文档标题搜索或 Docx 正文读取。SkillsJul 2026154k16k

looking-up-docs

5installs5forks

View on GitHub

How to install looking-up-docs?

alexei-led/cc-thingz/looking-up-docs

$npx -y skills add alexei-led/cc-thingz --skill looking-up-docs

Installs into the current project.

Summary

Get grounded, version-correct docs for a library, framework, CLI, or API. Never answer syntax or API questions from memory when lookup tools are available.

Files · 1

View on GitHub

SKILL.md

1	# Documentation Lookup
2
3	Get grounded, version-correct docs for a library, framework, CLI, or API.
4	Never answer syntax or API questions from memory when lookup tools are available.
5
6	## Scope
7
8	Use this skill for:
9
10	- API signatures, options, config keys, syntax, and examples.
11	- Versioned API behavior of a known library, framework, language, CLI, or
12	standard library when the question is how to call or configure it.
13	- Context7 docs lookup, including explicit `ctx7`, `Context7`, or `/org/project`
14	library-ID requests.
15	- Confirming versioned API behavior before writing code against an external API.
16
17	Do not use this skill for:
18
19	- Comparisons, recommendations, market research, current-state questions,
20	release-behavior questions, or best-practice surveys; route to `researching-web`.
21	- Repo-specific questions; search local files first.
22	- External queries containing secrets, credentials, personal data, private
23	payloads, or proprietary code.
24
25	## Reference Files
26
27	Read only what the question needs:
28
29	- `references/context7-cli.md` — Context7 lookup commands, selection rules,
30	limits, and fallbacks.
31	- `references/official-sources.md` — primary docs and registries by ecosystem.
32	- `references/web-tools.md` — platform web tools, query templates, and source
33	quality rules.
34
35	## Lookup Chain
36
37	Run tiers in order. Stop at the first tier that yields a grounded answer. State
38	which tier produced the answer and whether fallback was used.
39
40	### Tier 0 — Identify Package and Version
41
42	Find the exact package, module, CLI, language version, or framework version from
43	local evidence.
44
45	If no local version is available, state `version unknown` and prefer latest
46	stable official docs. Do not invent a version.
47
48	### Tier 1 — Context7
49
50	Use `references/context7-cli.md` for Context7 library resolution and docs fetch.
51	Best fit: versioned library and framework docs.
52
53	Escalate when Context7 is unavailable, rate-limited, returns no useful match
54	after one rephrase and one alternate library name, or returns docs for the wrong
55	version.
56
57	### Tier 2 — Official Docs and Registries
58
59	Use `references/official-sources.md` for language standard libraries, package
60	registries, and canonical project docs. Prefer primary docs or registry-linked
61	docs for the exact version.
62
63	Use web tools only for source discovery. Ground final syntax in URL-cited primary
64	sources.
65
66	### Tier 3 — GitHub Releases, Tags, and Source
67
68	Use GitHub only when primary docs or registry links are missing, incomplete, or
69	version-mismatched. Follow `references/official-sources.md` fallback rules.
70
71	Do not treat random issues, PR comments, blogs, or generated summaries as
72	authoritative API docs. Use them only as clues to primary sources.
73
74	### Tier 4 — Source Discovery or Gap Report
75
76	Use broad web research only to find primary docs after focused lookup fails. If
77	the question becomes a comparison, trade-off, current-state, or release-behavior
78	task, stop and route to `researching-web`. If no grounded source exists, report
79	the gap, the version needed vs found, and the safest next step.
80
81	## Limits and Failure Handling
82
83	- Never send secrets, credentials, private payloads, personal data, or
84	proprietary code to any external tier.
85	- Always use a real, specific query; never use a one-word placeholder.
86	- Do not loop a tier indefinitely: one rephrase and one alternate name per tier,
87	then escalate.
88	- If docs are version-mismatched, state the mismatch and escalate to exact-version
89	registry docs, release notes, or matching GitHub tag/source.
90	- If all tiers fail, report the gap and do not fabricate syntax.
91	- If external lookup would expose private data, refuse the external query and
92	answer from local context only, noting the limitation.
93
94	## Response Contract
95
96	Return a concise answer, not a workflow transcript, unless the user asks for the
97	lookup process.
98
99	Include:
100
101	1. Library/framework/API and version, or `version unknown`.
102	2. Tier that produced the answer, and fallback used if any.
103	3. Syntax or example guidance grounded in the source.
104	4. Source URL, Context7 library ID, or GitHub tag/source path for each claim.
105	5. Boundary note when the request is actually comparison, current-state,
106	release-behavior, or broad research.
107
108	If the user asks to describe the workflow, descr

People who liked this also viewed

6 picks

Type