JavaScript Concept Fact Checker
leonardomso/33-js-concepts
Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.
A skill your agent uses when documentation needs creating, checking, or maintaining — docs may have drifted from code, pre-release doc verification, updating docs after finishing code work, adding…
Install Maintaining Documentation
$ npx skills add obra/dotfiles --skill maintaining-documentation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install obra/dotfiles maintaining-documentation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/obra/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/maintaining-documentation .claude/skills/maintaining-documentation && rm -rf skills-srcUse ~/.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/
Install the "maintaining-documentation" agent skill from https://github.com/obra/dotfiles/tree/main/.claude/skills/maintaining-documentation into .claude/skills/maintaining-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintaining-documentation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/obra/dotfiles/tree/main/.claude/skills/maintaining-documentationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add obra/dotfiles --skill maintaining-documentation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install obra/dotfiles maintaining-documentation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/obra/dotfiles.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/maintaining-documentation .agents/skills/maintaining-documentation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "maintaining-documentation" agent skill from https://github.com/obra/dotfiles/tree/main/.claude/skills/maintaining-documentation into .agents/skills/maintaining-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintaining-documentation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add obra/dotfiles --skill maintaining-documentation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install obra/dotfiles maintaining-documentation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/obra/dotfiles.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/maintaining-documentation .cursor/skills/maintaining-documentation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "maintaining-documentation" agent skill from https://github.com/obra/dotfiles/tree/main/.claude/skills/maintaining-documentation into .cursor/skills/maintaining-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintaining-documentation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/obra/dotfiles.git --path .claude/skills/maintaining-documentation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add obra/dotfiles --skill maintaining-documentation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install obra/dotfiles maintaining-documentation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/obra/dotfiles.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/maintaining-documentation .gemini/skills/maintaining-documentation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "maintaining-documentation" agent skill from https://github.com/obra/dotfiles/tree/main/.claude/skills/maintaining-documentation into .gemini/skills/maintaining-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintaining-documentation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install obra/dotfiles maintaining-documentationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add obra/dotfiles --skill maintaining-documentation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/obra/dotfiles.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/maintaining-documentation .github/skills/maintaining-documentation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "maintaining-documentation" agent skill from https://github.com/obra/dotfiles/tree/main/.claude/skills/maintaining-documentation into .github/skills/maintaining-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintaining-documentation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add obra/dotfiles --skill maintaining-documentation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install obra/dotfiles maintaining-documentation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/obra/dotfiles.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/maintaining-documentation .opencode/skills/maintaining-documentation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "maintaining-documentation" agent skill from https://github.com/obra/dotfiles/tree/main/.claude/skills/maintaining-documentation into .opencode/skills/maintaining-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintaining-documentation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
maintaining-documentation- GitHub stars
- 116
- Token cost
- ~3.9k tokens
- SKILL.md length
- 2,185 words
- Files
- 10 (incl. scripts, references)
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- None found
At a glance
A skill your agent uses when documentation needs creating, checking, or maintaining — docs may have drifted from code, pre-release doc verification, updating docs after finishing code work, adding…
- Works in 5 steps: the doc is evergreen; → the claim is mechanical — an… → a single live (non-test) counterpart… → …
- Documentation needs creating
- SKILL.md covers Overview, Dispatch — read the flow file…, STOP: classify before you edit… and Scope & exclusions, plus 8 more sections
- Runs Python scripts from its folder; calls git
What it does
Maintaining Documentation is an agent skill from obra/dotfiles. Use when documentation needs creating, checking, or maintaining — docs may have drifted from code, pre-release doc verification, updating docs after finishing code work, adding or enforcing project terminology, deciding where a new doc should live, or a routine re-audit of previously verified docs.
Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts and reference files (for example `references/audit.md`, `references/dictionary.md` and `references/incremental.md`).
It sits in Writing & Content, covering Technical writing.
When your agent uses it
- Documentation needs creating
- Maintaining — docs may have drifted from code
- Pre-release doc verification
- Updating docs after finishing code work
Example prompts
- “/maintaining-documentation”
Requirements
- Python 3
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- the doc is evergreen;
- the claim is mechanical — an identifier/path, CLI flag, config/env
- a single live (non-test) counterpart exists in the code, so the right
- it's a local token replacement that leaves the surrounding sentence
- a missing counterpart is confirmed removed vs. renamed via git history
What it can do on your machine
Read from SKILL.md and the folder at commit df3be56. 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
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Maintaining Documentation loads about 3.9k tokens when it runs, and up to ~7.3k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 2,185 words of instructions outside code blocks.
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); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 2,185 words (~3,901 tokens).
“A doc is a set of claims about reality; this skill keeps a project's docs matching reality over time. The same law binds every flow: decide whether a doc is even supposed to track current reality (classify first), auto-fix only…”
- name
- maintaining-documentation
Files
SKILL.md and 9 other files (scripts, references) in .claude/skills/maintaining-documentation of obra/dotfiles.
- SKILL.md
- references/audit.md
- references/dictionary.md
- references/incremental.md
- references/new-docs.md
- references/write-path.md
- scripts/docmaint
- scripts/docmaint_test.py
- templates/DICTIONARY-template.md
- templates/INDEX-template.md
Open the folder on GitHubat commit df3be56
Compare with similar skills
Maintaining 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Maintaining Documentation this skillobra/dotfiles | 116 | — | ~3.9k | Automated safety check: Pass | None | |
| JavaScript Concept Fact Checkerleonardomso/33-js-concepts | 67k | 1 repos | ~5k | Automated safety check: Pass | MIT | |
| Beads Documentation Style Guidegastownhall/beads | 28k | — | ~3.2k | Automated safety check: Pass | MIT | |
| JavaScript Concept Page Workflowleonardomso/33-js-concepts | 67k | — | ~3.9k | Automated safety check: Pass | MIT | |
| JS Concept Resource Curatorleonardomso/33-js-concepts | 67k | — | ~4.9k | Automated safety check: Pass | MIT | |
| Technical Writing Standardcursor/plugins | 10k | 10 repos | ~2.4k | Automated safety check: Pass | None |
Similar skills
Beads Documentation Style Guide
gastownhall/beads
Sets the house style for the beads user docs: the canonical concept model, required terminology, prose and diagram conventions, and checks before docs work is done.
JavaScript Concept Page Workflow
leonardomso/33-js-concepts
Orchestrates five skills to produce a complete JavaScript concept documentation page, from resource curation through writing, tests, fact-checking and SEO.
JS Concept Resource Curator
leonardomso/33-js-concepts
Finds, vets, writes up and maintains external articles, videos and courses for JavaScript concept pages, including audits for broken and outdated links.
- Official
Technical Writing Standard
cursor/plugins
Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.
Writing Docs
nukeop/nuclear
A skill your agent uses when writing or editing documentation in packages/docs.
More from obra/dotfiles
All 12 skills in this repoChronicle
obra/dotfiles
Allows you to view the user's screen as well as several hours of history.
E2E Scenario Testing
obra/dotfiles
A skill your agent uses when verifying a running application end-to-end through its real interface — a web UI, a CLI, or a TUI — by writing and executing agent-run "scenario cards" against a freshly…
Roborev Fix
obra/dotfiles
A skill your agent uses when the user asks to fix open failing reviews, invokes $roborev-fix, or provides job IDs; do not use when the user only pastes review findings with no request to discover or…
Syncing Obsidian
obra/dotfiles
A skill your agent uses when reading or writing files in an Obsidian vault that is synced with obsync.
MCP CLI
obra/dotfiles
Use MCP servers on-demand via the mcp CLI tool - discover tools, resources, and prompts without polluting context with pre-loaded MCP integrations
Roborev Design Review
obra/dotfiles
Request a design review for a commit and present the results
Related
Categories
Questions about Maintaining Documentation
What does Maintaining Documentation do?
A skill your agent uses when documentation needs creating, checking, or maintaining — docs may have drifted from code, pre-release doc verification, updating docs after finishing code work, adding…. Maintaining Documentation is an agent skill from obra/dotfiles. Use when documentation needs creating, checking, or maintaining — docs may have drifted from code, pre-release doc verification, updating docs after finishing code work, adding or enforcing project terminology, deciding where a new doc should live, or a routine re-audit of previously verified docs.
When should I use Maintaining Documentation?
Maintaining Documentation fits situations like: documentation needs creating; maintaining — docs may have drifted from code; pre-release doc verification; updating docs after finishing code work.
How do I install Maintaining Documentation in Claude Code?
Run `npx skills add obra/dotfiles --skill maintaining-documentation -a claude-code`. Or copy the skill folder (.claude/skills/maintaining-documentation in obra/dotfiles) into .claude/skills/maintaining-documentation in your project. Claude Code loads it when a task matches its description.
How do I install Maintaining Documentation in Codex?
Run `npx skills add obra/dotfiles --skill maintaining-documentation -a codex`. Or copy the skill folder (.claude/skills/maintaining-documentation in obra/dotfiles) into .agents/skills/maintaining-documentation in your project. Codex loads it when a task matches its description.
Can I use Maintaining 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 obra/dotfiles --skill maintaining-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/maintaining-documentation, .gemini/skills/maintaining-documentation, .github/skills/maintaining-documentation and .opencode/skills/maintaining-documentation in your project.
What does Maintaining Documentation need to run?
Going by SKILL.md and its folder, Maintaining Documentation needs Python for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: Python 3.
Does Maintaining Documentation access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Maintaining 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Maintaining Documentation use?
No licence was found for Maintaining Documentation or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Maintaining Documentation use?
About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.4k tokens, read only when the agent opens those files.
What are the alternatives to Maintaining Documentation?
Skills that share tags, products or a category with Maintaining Documentation: JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars), Beads Documentation Style Guide (gastownhall/beads, 28k stars), JavaScript Concept Page Workflow (leonardomso/33-js-concepts, 67k stars) and JS Concept Resource Curator (leonardomso/33-js-concepts, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Maintaining Documentation?
obra (a GitHub user) maintains it in obra/dotfiles, which has 116 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 11, 2026.
Source: obra/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.