메뉴
Look up API, option, config, or usage details for any library declared in ./sources.txt by walking its local documentation tree. Use when the user asks how a documented feature works, requests an example, or asks for a version check.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | doc-library |
| description | Look up API, option, config, or usage details for any library declared in ./sources.txt by walking its local documentation tree. Use when the user asks how a documented feature works, requests an example, or asks for a version check. |
The repository is a versioned documentation library. This skill guides a
precise, file-grounded lookup against local snapshots, scaled to however
many libraries are currently declared in ./sources.txt.
Invoke this skill when the user asks about:
sources.txt first)./sources.txt. Skip blank lines and lines starting with #.name|repo|ref|sparse_path|mode. The doc tree for that entry lives at
./<name>/ (or ./.<name>/ if the name is dot-prefixed).name from sources.txt. If the
question references a library not present in sources.txt, that
library is not in scope — say so and stop.name in sources.txt has no matching sibling directory, the
snapshot is unsynced — recommend ./scripts/add.sh.sources.txt is the single source of truth. The human-readable
"Documentation Sources" table in ./README.md is a cache; if the two
disagree, sources.txt wins.
name in sources.txt../<name>/. Use the in-repo path structure as the authoritative
index..md file(s) and read the section that
addresses the question. Prefer the most specific file over a
top-level overview.<name>/<rest-of-path>.md.ref field in sources.txt and/or
the Updated date in README.md) alongside the citation so the
user can confirm the snapshot matches their project.repo URL from
sources.txt) for the latest version, or add the source to
sources.txt and re-run ./scripts/add.sh.sources.txt (read-only
snapshots).skill tool.When answering, use this shape:
Library: <name from sources.txt>
Version: <ref / updated date>
Source: <relative path to the .md file>
Reference: <short paraphrase or quote>
If a single question spans multiple libraries, repeat the block per library.
Review code for correctness, security, performance, and maintainability using a systematic checklist. Use when the reviewer agent is asked to assess any code change or existing code.
Systematically investigate a bug through evidence-based root cause analysis. Use when the debugger agent is working a reproduction, isolation, or fix-proposal step.
Classify an incoming request by type and complexity before routing to a specialist agent. Use when a request needs to be categorized to determine which agent and pipeline to invoke.
Produce architecture decisions, system designs, and integration patterns. Use when a feature spans more than one subsystem or when a design decision must be documented before implementation starts.
Decompose a profiled request into a concrete, ordered list of agent tasks. Use after profiling any M, L, or compound request to produce the task list the planner emits.