Agent skill

Documentation

by extra-org in extra-org/extra

Keep the repository's documentation accurate, honest, and synchronized with the code.

MITAuto-check passedDevelopment

Install Documentation

skills CLI
$ npx skills add extra-org/extra --skill documentation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install extra-org/extra documentation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/extra-org/extra.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/documentation .claude/skills/documentation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
documentation
GitHub stars
113
Token cost
~848 tokens
SKILL.md length
402 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

Keep the repository's documentation accurate, honest, and synchronized with the code.

  • Works in 6 steps: Identify scope. Decide which file(s) the… → Write the change concisely; add an… → For a new binding decision, add… → …
  • Tasks that involve Architecture decision records
  • SKILL.md covers Purpose, When to Use This Skill, Files to Read First and Core Principles, plus 4 more sections
  • Calls make

What it does

Documentation is an agent skill from extra-org/extra. Keep the repository's documentation accurate, honest, and synchronized with the code. Use when editing docs, README, AGENTS.md, or ADRs.

Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Architecture decision records, Agent instruction files and Technical documentation. The repository describes itself as: Turn your product into an AI-powered assistant. The licence is MIT.

When your agent uses it

  • Tasks that involve Architecture decision records
  • Tasks that involve Agent instruction files
  • Tasks that involve Technical documentation

Example prompts

  • “/documentation”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Identify scope. Decide which file(s) the change belongs in (README vs.
  2. Write the change concisely; add an example or flow if it aids
  3. For a new binding decision, add docs/adr/NNNN-title.md using the
  4. Sync cross-references: update indexes (docs/README.md,
  5. Verify honesty: re-read for any claim that overstates current status.
  6. Validate with make check.

What it can do on your machine

Read from SKILL.md and the folder at commit 023b0a0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • make

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Documentation loads about 848 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 402 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~848

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from extra-org/extra at commit 023b0a0, republished under its MIT licence (© extra-org). 402 words, ~848 tokens.

Download SKILL.mdSave it as .claude/skills/documentation/SKILL.md (or your agent's skills folder).
name
documentation
description
Keep the repository's documentation accurate, honest, and synchronized with the code. Use when editing docs, README, AGENTS.md, or ADRs.
generated
true
source
.ai/skills/documentation.md
<!--
This file is generated by tools/skills.
Do not edit this file directly.
Edit .ai/skills/documentation.md and run `make generate-ai`.
-->

Skill: Documentation

Purpose

Keep the repository's documentation accurate, honest, and synchronized with the code, so future agents and users can trust it.

When to Use This Skill

  • Editing anything in docs/, the README.md, or AGENTS.md.
  • Adding or changing an ADR.
  • Shipping a behavior/contract change that documentation must reflect.

Files to Read First

  • AGENTS.md
  • docs/README.md (reading order and index).
  • The specific doc/ADR you are changing and any code it describes.
  • .ai/skills/skill-authoring.md if the doc is a skill.

Core Principles

  • Be honest about status. Clearly separate what exists from what is planned; use accurate status markers (✅ done / ⏳ planned).
  • Never claim unimplemented features work. The project is in the foundation phase — don't describe the runtime/compiler/API as functioning.
  • Docs follow code. Update docs in the same change as the behavior they describe; don't let them drift.
  • Decisions go in ADRs. A binding architectural decision is recorded as an ADR, not buried in prose.
  • Show, don't just tell. Prefer examples, flows, and small diagrams where they clarify.
  • Right file for the right scope: README = user-facing; AGENTS.md = repo-wide rules for agents; ADRs = architectural decisions; docs/ = design.

Process

  1. Identify scope. Decide which file(s) the change belongs in (README vs. AGENTS.md vs. docs vs. ADR) — don't scatter the same content.
  2. Write the change concisely; add an example or flow if it aids understanding.
  3. For a new binding decision, add docs/adr/NNNN-title.md using the existing ADR format (Status, Context, Decision, Consequences, Alternatives, Enforcement).
  4. Sync cross-references: update indexes (docs/README.md, .ai/README.md) and any links.
  5. Verify honesty: re-read for any claim that overstates current status.
  6. Validate with make check.
Show full SKILL.md (140 more words)Show less

Checklist Before Finishing

  • No unimplemented feature described as working; status markers accurate.
  • Docs updated in the same change as the behavior/contract.
  • Architectural decisions captured in an ADR (not just prose).
  • Correct file chosen for the scope (README / AGENTS / docs / ADR).
  • Examples/flows added where helpful.
  • Cross-references and indexes updated.
  • Consistent with AGENTS.md, README, docs, and ADRs.
  • make check passes.

Common Mistakes to Avoid

  • Documenting aspirational behavior as if it already works.
  • Editing a contract in prose without a supporting ADR.
  • Letting README/AGENTS/docs drift out of sync after a code change.
  • Duplicating the same content across multiple files.
  • Large rewrites that lose existing structure and history.

Expected Final Report

State: which docs/ADRs were created or changed and why; confirmation that no unimplemented feature is claimed as working; any new ADR added; which indexes and cross-references were updated; and the make check result.

© extra-org, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/documentation of extra-org/extra.

Open the folder on GitHubat commit 023b0a0

Compare with similar skills

Documentation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Documentation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Documentation this skillextra-org/extra113—~848Automated safety check: PassMIT
Rememberantonio-orionus/Arroxy389—~571Automated safety check: PassMIT
Ad DriftCorridorTech/PoseCap220—~1.8kAutomated safety check: NotesApache-2.0
Documentdcodesdev/LetterSpace100—~461Automated safety check: PassMIT
Choruz Prose StandardinclusionAI/Choruz979—~1.6kAutomated safety check: PassApache-2.0
Expectationscitypaul/.dotfiles739—~1.2kAutomated safety check: PassCustom licence

Similar skills

  • Remember

    antonio-orionus/Arroxy

    Persists a durable Arroxy lesson — a gotcha, user preference, workflow rule, or design decision — to the right tracked file (project memory, AGENTS.md, CONTEXT.md, dev-docs, or an ADR) so any coding…

    389 GitHub stars~571 tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Ad Drift

    CorridorTech/PoseCap

    Read-only drift audit — compare AGENTS.md, ARCHITECTURE.md, ADR statuses, feature specs in doc/specs/, and documentation discipline against what the code actually does.

    220 GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check: notes
  • Document

    dcodesdev/LetterSpace

    Use this when writing or updating documentation — a README, docs/ page, CLAUDE.md, changelog entry, or doc comments — or when the user says 'document this'.

    100 GitHub stars~461 tokensUpdated 5 days ago
    DevelopmentAuto-check passed
  • Choruz Prose Standard

    inclusionAI/Choruz

    A skill your agent uses when writing, reviewing, restoring, trimming, or auditing prose in this repository, including deciding where documentation or comments are required across Markdown, Rust doc…

    979 GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Expectations

    citypaul/.dotfiles

    Decide where a learning, gotcha, or decision should live so it is not lost, and capture it there while context is fresh.

    739 GitHub stars~1.2k tokensUpdated 5 days ago
    DevelopmentAuto-check passed
  • Ad Review

    CorridorTech/PoseCap

    Two-axis fresh-context code review per WORKFLOW §10. An agent skill from CorridorTech/PoseCap.

    220 GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check: notes

More from extra-org/extra

All 14 skills in this repo
  • Testing

    extra-org/extra

    How to write and run fast, deterministic, behavior-focused pytest tests that never touch real external systems.

    113 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • Architecture Review

    extra-org/extra

    Guard the project's architecture invariants. An agent skill from extra-org/extra.

    113 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed
  • The standard for writing Python here — small, typed, explicit, testable modules with side effects pushed to the edges.

    113 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Skill Authoring

    extra-org/extra

    How to create or restructure a skill so the .ai/skills/ system stays consistent, operational, and trustworthy.

    113 GitHub stars~1k tokensUpdated 1 mo ago
    Auto-check passed
  • Code Review

    extra-org/extra

    Senior-level code review for the agent platform — architecture and boundaries first, then correctness, security, testability, and simplicity.

    113 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Git Workflow

    extra-org/extra

    Work safely with Git — keep changes scoped and reviewable, never overwrite the user's work, and produce clear history.

    113 GitHub stars~781 tokensUpdated 1 mo ago
    Auto-check: notes

Questions about Documentation

What does Documentation do?

Keep the repository's documentation accurate, honest, and synchronized with the code. Documentation is an agent skill from extra-org/extra. Keep the repository's documentation accurate, honest, and synchronized with the code.

When should I use Documentation?

Documentation fits situations like: tasks that involve Architecture decision records; tasks that involve Agent instruction files; tasks that involve Technical documentation.

How do I install Documentation in Claude Code?

Run `npx skills add extra-org/extra --skill documentation -a claude-code`. Or copy the skill folder (.claude/skills/documentation in extra-org/extra) into .claude/skills/documentation in your project. Claude Code loads it when a task matches its description.

How do I install Documentation in Codex?

Run `npx skills add extra-org/extra --skill documentation -a codex`. Or copy the skill folder (.claude/skills/documentation in extra-org/extra) into .agents/skills/documentation in your project. Codex loads it when a task matches its description.

Can I use Documentation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add extra-org/extra --skill documentation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/documentation, .gemini/skills/documentation, .github/skills/documentation and .opencode/skills/documentation in your project.

What does Documentation need to run?

Going by SKILL.md and its folder, Documentation needs the command-line tools its instructions call (make).

Does Documentation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Documentation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Documentation use?

Documentation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Documentation use?

About 848 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Documentation?

Skills that share tags, products or a category with Documentation: Remember (antonio-orionus/Arroxy, 389 stars), Ad Drift (CorridorTech/PoseCap, 220 stars), Document (dcodesdev/LetterSpace, 100 stars) and Choruz Prose Standard (inclusionAI/Choruz, 979 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Documentation?

extra-org (a GitHub organization) maintains it in extra-org/extra, which has 113 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 7, 2026.

Source: extra-org/extra on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.