New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Doc Maintenance

by paperclipai in paperclipai/paperclip

Keep project docs aligned with recent code and feature changes — detect drift, update affected pages, and add release-relevant notes without rewriting unchanged sections.

MITAuto-check passedDevelopment

Install Doc Maintenance

skills CLI
$ npx skills add paperclipai/paperclip --skill doc-maintenance -a claude-code

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

GitHub CLI
$ gh skill install paperclipai/paperclip doc-maintenance --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/paperclipai/paperclip.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/skills-catalog/catalog/bundled/docs/doc-maintenance .claude/skills/doc-maintenance && 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
doc-maintenance
GitHub stars
100k
Token cost
~1.1k tokens
SKILL.md length
625 words
Files
1
Skills in repo
60
Repo updated
First seen
Licence
MIT

At a glance

Keep project docs aligned with recent code and feature changes — detect drift, update affected pages, and add release-relevant notes without rewriting unchanged sections.

  • Works in 8 steps: Establish the baseline. Get the commit… → Enumerate user-visible changes. Read… → Map changes to docs. For each change,… → …
  • Development work in your project
  • SKILL.md covers When to use, When not to use, The pass and Style baseline, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Doc Maintenance is an agent skill from paperclipai/paperclip. Keep project docs aligned with recent code and feature changes — detect drift, update affected pages, and add release-relevant notes without rewriting unchanged sections.

Its SKILL.md is about 1.1k 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. The repository describes itself as: The open-source app everyone uses to manage agents at work. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/doc-maintenance”

Workflow steps

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

  1. Establish the baseline. Get the commit range you are documenting against (since last release tag, since last merged-doc commit, or since a…
  2. Enumerate user-visible changes. Read commits and PR descriptions. List, for each change, what a user can now do differently.
  3. Map changes to docs. For each change, find every page that mentions the affected concept. Common targets: README, CLI reference, API…
  4. Update precisely. Edit only the lines that need to change. Do not rewrap paragraphs you did not modify — it pollutes the diff.
  5. Add new entries where needed. New CLI flag → CLI reference entry. New env var → configuration reference entry. New endpoint → API…
  6. Update examples and snippets. Code blocks in docs are wrong faster than prose. Re-run any example that touches new behavior.
  7. Write the release note. One sentence per user-visible change. Group by Added / Changed / Fixed / Deprecated / Removed. Link to the…
  8. Cross-check. Search the docs for the old behavior wording and remove or update stragglers.

What it can do on your machine

Read from SKILL.md and the folder at commit de9ab8e. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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

Doc Maintenance loads about 1.1k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 625 words of instructions outside code blocks.

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

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 paperclipai/paperclip at commit de9ab8e, republished under its MIT licence (© paperclipai). 625 words, ~1,117 tokens.

Download SKILL.mdSave it as .claude/skills/doc-maintenance/SKILL.md (or your agent's skills folder).
name
doc-maintenance
description
Keep project docs aligned with recent code and feature changes — detect drift, update affected pages, and add release-relevant notes without rewriting unchanged sections.
key
paperclipai/bundled/docs/doc-maintenance
recommendedForRoles
engineer, product, devrel
tags
docs, documentation, release-notes

Doc Maintenance

Keep the documentation honest with minimum churn. The goal is alignment between docs and behavior, not stylistic rewrites or cosmetic re-organization. Reviewers should be able to read a diff and see "this updates docs to match recent behavior changes".

When to use

  • A PR or recent set of merges changed user-visible behavior: CLI flags, API shapes, default values, configuration keys, endpoints, environment variables, supported versions.
  • A user-reported bug traced back to outdated documentation.
  • A release is being cut and the docs need a pass against the merged commits.
  • A new feature shipped but only the engineer's PR description describes how to use it.

When not to use

  • The change is internal-only (private helper rename, refactor) with no user-visible impact.
  • You want to "improve the docs" without a behavior anchor. That is a separate scoped project, not maintenance — make a plan first.

The pass

  1. Establish the baseline. Get the commit range you are documenting against (since last release tag, since last merged-doc commit, or since a specific PR).
  2. Enumerate user-visible changes. Read commits and PR descriptions. List, for each change, what a user can now do differently.
  3. Map changes to docs. For each change, find every page that mentions the affected concept. Common targets: README, CLI reference, API reference, configuration reference, migration guide, FAQ, examples.
  4. Update precisely. Edit only the lines that need to change. Do not rewrap paragraphs you did not modify — it pollutes the diff.
  5. Add new entries where needed. New CLI flag → CLI reference entry. New env var → configuration reference entry. New endpoint → API reference entry. Don't only add it to the changelog.
  6. Update examples and snippets. Code blocks in docs are wrong faster than prose. Re-run any example that touches new behavior.
  7. Write the release note. One sentence per user-visible change. Group by Added / Changed / Fixed / Deprecated / Removed. Link to the relevant PRs and docs section.
  8. Cross-check. Search the docs for the old behavior wording and remove or update stragglers.

Style baseline

  • Voice: second person ("you can pass --json to ..."). Avoid "we" except in narrative pages.
  • Tense: present, not future. The behavior exists once shipped.
  • Headings: imperative ("Configure the cache") or noun-phrase ("Cache configuration"), match the surrounding page.
  • Code blocks: include the language tag so syntax highlighting works.
  • Cross-links: link the first mention of a concept on each page; do not link every occurrence.
  • Avoid promising future behavior. If something is unreleased, mark it experimental or omit it.
Show full SKILL.md (214 more words)Show less

Drift detection

A doc page is drifting if any of these are true:

  • It documents a flag, key, or endpoint that no longer exists.
  • An example does not run as written.
  • A default value in the docs does not match the code.
  • A supported-versions list excludes a version the project actually supports, or includes one it dropped.
  • A "Coming soon" section references a feature that shipped or was cancelled.

When you find drift, fix it in the same pass and note it in the release note's Fixed group.

Release-note rules

  • One sentence per item. If two sentences are needed, the item is likely two items.
  • User impact first, internal cause second. Faster cold start (avoid full bundle download on first run) beats Refactor bootstrap loader.
  • Link the PR for engineering readers and the docs page for users.
  • Mark breaking changes explicitly: **Breaking:** prefix. Include migration steps inline or via link.

Anti-patterns

  • Massive doc PRs that bundle stylistic rewrites with real updates. Reviewers cannot tell which lines reflect actual behavior changes.
  • "Updated docs" commit messages with no detail. Make the commit say what changed and why.
  • Adding to the changelog without updating the reference docs the changelog points to.
  • Marking a feature as available before its code lands. Documentation must follow behavior, not promise it.

© paperclipai, 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 packages/skills-catalog/catalog/bundled/docs/doc-maintenance of paperclipai/paperclip.

Open the folder on GitHubat commit de9ab8e

Compare with similar skills

Doc Maintenance 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.

Doc Maintenance compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Doc Maintenance this skillpaperclipai/paperclip100k—~1.1kAutomated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from paperclipai/paperclip

All 60 skills in this repo

  • Garden Inbox

    paperclipai/paperclip

    Scan a Paperclip user's Mine inbox, classify reversible archive candidates, request checkbox confirmation, and archive only accepted selections.

    100k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Paperclip

    paperclipai/paperclip

    Interact with the Paperclip control plane API for task coordination and governance.

    100k GitHub stars~9.6k tokensUpdated today
    Auto-check passed

  • Paperclip

    paperclipai/paperclip

    A skill your agent uses for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and…

    100k GitHub stars~18k tokensUpdated today
    Auto-check passed

  • Design Guide

    paperclipai/paperclip

    Paperclip UI design system guide for building consistent, reusable frontend components.

    100k GitHub starsUsed in 1 repo~3.1k tokens
    Auto-check passed

  • Paperclip Page

    paperclipai/paperclip

    Publish static HTML pages and asset folders to the Paperclip S3/CloudFront page host.

    100k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Paperclip Create Agent

    paperclipai/paperclip

    Create new agents in Paperclip with governance-aware hiring.

    100k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed

Categories

Questions about Doc Maintenance

What does Doc Maintenance do?

Keep project docs aligned with recent code and feature changes — detect drift, update affected pages, and add release-relevant notes without rewriting unchanged sections. Doc Maintenance is an agent skill from paperclipai/paperclip. Keep project docs aligned with recent code and feature changes — detect drift, update affected pages, and add release-relevant notes without rewriting unchanged sections.

When should I use Doc Maintenance?

Doc Maintenance fits situations like: development work in your project.

How do I install Doc Maintenance in Claude Code?

Run `npx skills add paperclipai/paperclip --skill doc-maintenance -a claude-code`. Or copy the skill folder (packages/skills-catalog/catalog/bundled/docs/doc-maintenance in paperclipai/paperclip) into .claude/skills/doc-maintenance in your project. Claude Code loads it when a task matches its description.

How do I install Doc Maintenance in Codex?

Run `npx skills add paperclipai/paperclip --skill doc-maintenance -a codex`. Or copy the skill folder (packages/skills-catalog/catalog/bundled/docs/doc-maintenance in paperclipai/paperclip) into .agents/skills/doc-maintenance in your project. Codex loads it when a task matches its description.

Can I use Doc Maintenance 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 paperclipai/paperclip --skill doc-maintenance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/doc-maintenance, .gemini/skills/doc-maintenance, .github/skills/doc-maintenance and .opencode/skills/doc-maintenance in your project.

What does Doc Maintenance need to run?

SKILL.md names no scripts, command-line tools or credentials: Doc Maintenance is instructions for the agent only.

Does Doc Maintenance 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 Doc Maintenance 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 Doc Maintenance use?

Doc Maintenance 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 Doc Maintenance use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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 Doc Maintenance?

Skills that share tags, products or a category with Doc Maintenance: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Doc Maintenance?

paperclipai (a GitHub organization) maintains it in paperclipai/paperclip, which has 99,905 GitHub stars. The repository holds 60 skills in this directory. The repository was last updated on October 11, 2026.

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