docs
GitHub管理用户请求的文档创建与协作，如PRD、规格书等。通过docs connector引导并生成文档结构，支持评论编辑，区分于代码注释或普通聊天回复。
Trigger Scenarios
用户要求创建或分享文档（如spec, PRD, runbook）
用户同意创建文档的建议
用户提供可能是文档的链接需验证
Install
npx skills add asgeirtj/system_prompts_leaks --skill docs -g -y
SKILL.md
Frontmatter
{
"name": "docs",
"description": "docs (living docs people share, comment on and edit; use only when the user asks for one: names a doc, document, page, memo, spec, PRD, runbook or write-up, asks for somewhere to share or keep editing something, or says yes to your doc offer; a plan, comparison, summary or notes asked in chat stays in chat (at most a one-line doc offer); a report, status update, recap or \"something I can send them\" with no form named → ask first: reply, doc or file?; tabs hold tables and live charts too; a pasted claude.ai\/code\/artifact\/… link may be a doc: check with docs tools first; not HTML pages, apps or plain chat answers; a .docx\/.pptx\/.xlsx\/PDF asked for by name → that format's skill): asked for one → no docs-connector instructions in context? call the docs connector's `guide` with topic.instructions first, then create the doc (headings only, no body) before any search, file read or plan, even with files attached. Documenting code means docstrings or repo docs, not a doc."
}
Everything about docs is served by the docs connector — follow its instructions (they say what to call first). If no docs tools are present (they may be listed as pages tools on some accounts), say so.
Version History
- 4a725c5 Current 2026-09-23 08:17
