Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

read-docs阅读文档

Agent Skill

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

总安装

218

周安装

9

GitHub Stars

公开资料未说明

下载量

71
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:read-docs(阅读文档)
来源仓库:https://github.com/nielsmadan/agentic-coding
仓库路径:skills/read-docs
安装命令:
npx skills add https://github.com/nielsmadan/agentic-coding --skill read-docs
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/nielsmadan/agentic-coding --skill read-docs

简介

read-docs 用于辅助文档、README 和 Markdown 内容的整理与改写。

  • 适合提炼结构、统一术语或检查链接,提升内容可读性。
  • 保留项目已有事实,避免将未确认信息写成确定结论。
  • 涉及对外文案时需注意语气,防止过度营销或夸大能力。
  • read-docs 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Read Docs

Search internal documentation for project-specific information.

Usage

/read-docs auth                    # Search for auth-related docs
/read-docs database schema         # Search for database/schema docs
/read-docs                         # List available documentation

Search Strategy

  1. Check for docs/ folder - Primary documentation location
  2. Search filenames - Glob for keyword matches in file names
  3. Search contents - Grep for keyword matches in file contents
  4. Prioritize results:

- Exact filename match (e.g., "auth" → docs/auth.md) - Filename contains keyword (e.g., "auth" → docs/authentication-guide.md) - Content matches (e.g., "auth" mentioned in docs/architecture.md)

Locations Searched

In order of priority:

  1. docs/**/*.md - Primary documentation
  2. CLAUDE.md - Project conventions
  3. README.md - Project overview
  4. *.md in project root - Other documentation

Gotchas

  • The search cap of 5 files means relevant docs can be silently skipped. If the most relevant doc ranks 6th, it will be listed but never read.
  • Trust code over docs when they conflict — docs may describe an intended design that was never implemented or was later changed.

Workflow

With keywords:

  1. Search filenames for keyword matches:

- Glob pattern: docs/**/*{keyword}*

  1. Search file contents for keyword matches:

- Grep pattern: {keyword} path: docs/ and root *.md files

  1. Rank matches by priority:

- Exact filename match (e.g., "auth" → docs/auth.md) - Filename contains keyword (e.g., "auth" → docs/authentication-guide.md) - Content match with keyword in a heading (e.g., ## Auth in docs/architecture.md) - Content match in body text

  1. Read up to 5 top-ranked matches and summarize findings.
  2. For multi-word queries (e.g., "database schema"), search each word separately AND as a phrase. Prioritize files that match all words over files matching only one.
  3. If more than 5 files match, list the remaining filenames without reading them so the user knows what else is available.

Without keywords:

List available documentation:

  • Glob pattern: docs/**/*.md
  • Glob pattern: *.md (root-level docs)

Present a structured overview of available documentation:

  1. Group files by directory (e.g., docs/api/, docs/guides/, root-level)
  2. For each file, show the filename and its first heading (or first non-empty line if no heading exists)
  3. If more than 20 files exist, summarize by directory with file counts and list only the top-level structure instead of enumerating every file

Output

Summarize findings:

  1. Documents found - List with brief description of each
  2. Key information - Relevant excerpts for the query
  3. Related docs - Other documents that may be useful

Examples

Search internal docs before implementing auth feature:

/read-docs auth

Searches docs/ filenames and contents for auth-related documentation. Finds docs/auth.md and references in docs/architecture.md, then summarizes relevant patterns, token handling conventions, and any documented gotchas before you start coding.

Check for documented gotchas before refactor:

/read-docs database migration

Searches for migration-related docs and surfaces any documented pitfalls, required steps, or past issues logged in docs/log/. Presents key findings so you can avoid known problems during the refactor.

Troubleshooting

No docs/ folder found in project

Solution: Fall back to searching root-level .md files (README.md, CLAUDE.md, CONTRIBUTING.md). If the project has no documentation at all, use research-online for external references or check inline code comments via Grep for conventions.

Documentation is stale or contradicts code

Solution: Trust the code over the documentation when they conflict. Note the discrepancy in your response so the user can update the docs, and verify behavior by reading the actual source files rather than relying on the outdated documentation.

Notes

  • This skill is for internal project docs, not external library docs
  • For external library documentation, use research-online
  • If no docs/ folder exists, search root.md files only

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.92%
按下载量换算27

Claude

29.61%
按下载量换算21

Cursor

20.43%
按下载量换算15

Gemini CLI

8.78%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills