Automated summary
A code documentation agent that writes and updates Markdown documents under docs/generated/, pointing at code through symbol links instead of embedding code blocks.
Strengths
- Clearly separates generated docs (docs/generated/) from hand-written ones, which it never modifies
- Uses `[symbol](path/file)` reference pointers instead of code snippets, reducing documentation drift
- Ships a `check` subcommand to surface stale documents, broken references and orphan docs
- Finds documents via Glob/Grep on frontmatter and an INDEX.md instead of opening files one by one
Limitations
- Relies entirely on the docs/generated/ convention and a maintained INDEX.md to work correctly
- Staleness detection is driven by code_refs paths, not by the actual content of the code
- Documentation output is intentionally sparse, with little to no concrete code examples
Use it when a project needs structured, indexed design-intent documentation kept in sync with code changes.
Avoid it for tutorials, user guides or documentation that needs rich code samples, which this skill deliberately excludes.
Security analysis
SafeThe skill is a documentation assistant that only reads and writes Markdown files under docs/generated/, using standard Read/Write/Edit/Glob/Grep operations. There is no network access, no shell execution, no credential handling, and it explicitly forbids modifying files outside the generated docs directory, which is a protective guardrail rather than a risk.
No concerns found
How this analysis is madeExamples
/docs write "auth flow design" src/auth//docs check/docs write "billing webhook handling"name: docs version: 0.0.2 category: productivity description: "Code documentation agent — write/update docs with /docs write, check status with /docs check. Minimal code blocks, reference pointer based." argument-hint: "<write|check> [topic] [code-path]"
Input
$ARGUMENTS
Instructions
Document Root
Documents managed by this skill are stored under docs/generated/.
They are organized by category subdirectories: docs/generated/<category>/<slug>.md
Documents outside docs/generated/ are considered manually written and must never be modified.
Tool Usage Rules
Always use the tools below for document search and management. Do not open files one by one — search smartly using patterns.
| Purpose | Tool | Usage |
|---------|------|-------|
| Find document files | Glob | docs/generated/**/*.md pattern to get full document list |
| Search frontmatter | Grep | Filter by title:, category: patterns |
| Read existing docs | Read | Read frontmatter + body (only necessary documents) |
| Verify code references | Glob | Check if file paths in code_refs exist |
| Create documents | Write | Create new document files |
| Update documents | Edit | Update specific parts of existing documents |
| Scan INDEX | Read | Read docs/generated/INDEX.md for category structure and document list |
Subcommand Routing
The first word of $ARGUMENTS determines the subcommand.
| First word | Action |
|------------|--------|
| write | Read and execute references/write-procedure.md |
| check | Read and execute references/check-procedure.md |
| (none / help) | Print usage below and stop |
When run without a subcommand:
## docs
Code documentation agent — systematically records development knowledge.
### Commands
| Command | Description |
|---------|-------------|
| write <topic> [code-path] | Write or update a document on the topic |
| check | Check all document status (stale, broken refs, orphan docs) |
### Features
- Uses `[symbol](file-path)` reference pointers instead of code blocks
- Organized by category folders under `docs/generated/`
- INDEX.md based document indexing
Argument Parsing
Parse the remaining arguments after removing the subcommand keyword (write / check).
write arguments:
- First argument: topic (required) — title/topic of the document
- Second argument: code-path (optional) — path to related code (file or directory)
Examples:
/docs write "auth flow design"→ topic only/docs write "auth flow" src/auth/→ topic + code-path
check arguments: None.
Document Writing Principles
- Minimize code blocks: Do not include code snippets directly in documents. Instead, use markdown links in the form
[symbol](project-root-relative/file-path)as references. - Focus on design intent: Record "why it was done this way" rather than "what was done".
- Protect manual documents: Never modify documents outside
docs/generated/.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/code-documentation-agent-mryiqhgg/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/code-documentation-agent-mryiqhgg' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/code-documentation-agent-mryiqhgg/download' --output '.skill-downloads/code-documentation-agent-mryiqhgg/SKILL.md.part' && mv '.skill-downloads/code-documentation-agent-mryiqhgg/SKILL.md.part' '.skill-downloads/code-documentation-agent-mryiqhgg/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/code-documentation-agent-mryiqhgg/SKILL.md' && test -s '.skill-downloads/code-documentation-agent-mryiqhgg/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/docs' && cp -R '.skill-downloads/code-documentation-agent-mryiqhgg' '.claude/skills/docs'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/code-documentation-agent-mryiqhgg'openskills read 'code-documentation-agent-mryiqhgg'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/code-documentation-agent-mryiqhgg/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Supabase Docs Authoring
Documentation
Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.
Create Architecture Decision Record
Documentation
Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.
Plan update with deep research
Documentation
Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.