New: 97,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

Docs Updater

by hex in hex/claude-council

Docs must be updated or restructured to match code that already changed: README, reference pages, CLI help or config docs.

MITAuto-check passedDevelopment

Install Docs Updater

skills CLI
$ npx skills add hex/claude-council --skill docs-updater -a claude-code

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

GitHub CLI
$ gh skill install hex/claude-council docs-updater --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/hex/claude-council.git skills-src && mkdir -p .claude/skills && cp -r skills-src/mods/council-pane/specialists/docs-updater .claude/skills/docs-updater && 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
docs-updater
GitHub stars
843
Token cost
~930 tokens
SKILL.md length
548 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Docs must be updated or restructured to match code that already changed: README, reference pages, CLI help or config docs.

  • Works in 3 steps: List the pages or files in scope and the… → Read the project's docs conventions:… → Change no production code. If the docs…
  • Development work in your project
  • SKILL.md covers Scope, Inventory before editing, Find the source of truth and Rewrite, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Docs Updater is an agent skill from hex/claude-council. Docs must be updated or restructured to match code that already changed: README, reference pages, CLI help or config docs.

Its SKILL.md is about 930 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: Claude Code plugin that asks several AI coding agents the same question and shows their answers side by side. Gemini, OpenAI, Grok, Perplexity, Kimi and any model OpenRouter… The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/docs-updater”

Workflow steps

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

  1. List the pages or files in scope and the code changes they must reflect.
  2. Read the project's docs conventions: style guide, frontmatter, link
  3. Change no production code. If the docs reveal a code bug, report it.

What it can do on your machine

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

Docs Updater loads about 930 tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 548 words of instructions outside code blocks.

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

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 hex/claude-council at commit 23867e1, republished under its MIT licence (© hex). 548 words, ~930 tokens.

Download SKILL.mdSave it as .claude/skills/docs-updater/SKILL.md (or your agent's skills folder).
name
docs-updater
description
Docs must be updated or restructured to match code that already changed: README, reference pages, CLI help or config docs.

Docs Updater

Bring documentation in line with the code as it is now. Every behaviour claim must be checked against the code. No fact may disappear unless there is proof it is obsolete.

Scope

  1. List the pages or files in scope and the code changes they must reflect. If the task names only the code change, find the docs that mention the affected commands, flags, config keys, endpoints or errors.
  2. Read the project's docs conventions: style guide, frontmatter, link format, generated-docs tooling. If a page is generated, edit the generator or its source, never the output.
  3. Change no production code. If the docs reveal a code bug, report it.

Inventory before editing

For each page, list every fact it states before you rewrite it:

  • commands, subcommands, flags, environment variables, config keys, defaults, allowed values, units;
  • limits, timeouts, precedence rules, fallbacks, ordering, rate limits;
  • permissions, auth, safety and destructive-action behaviour;
  • setup requirements: versions, operating systems, dependencies, credentials;
  • error messages, symptoms and recovery steps;
  • examples, expected output, tables and links.

Give each fact one fate:

  • keep: it stays on this page;
  • move: name the destination page and section;
  • delete: name the code, schema or --help output that proves it obsolete.

Find the source of truth

Check every behaviour-sensitive claim against the nearest authority:

  • config: the schema, type definitions or parsing code;
  • CLI: the command definitions and the real --help output;
  • runtime behaviour: the implementing code and its tests;
  • APIs: the handler code, the schema or contract tests.

Existing docs are secondary evidence only. Never infer a default, permission or timeout from a name or from the old text. Run the command or read the code. A reference table missing a public field, default or limit is a correctness bug, not a style issue.

Show full SKILL.md (254 more words)Show less

Rewrite

  • Open with what the reader can do and why the page exists.
  • Put the recommended path before alternatives.
  • Keep the common case in the main flow. Move exhaustive tables and rare detail to a reference page and link to it where it is needed.
  • Keep one canonical place for each fact. Link rather than duplicate.
  • Update examples so they run against the current code. Run them where you can and record which ones you ran.
  • Write troubleshooting from observable symptoms.
  • Leave no placeholder such as TODO, TBD or "see docs".

Compare old and new

After editing, go through the inventory:

  • every fact is kept, moved (and present at its destination), or deleted with its proof;
  • links resolve, including anchors to moved sections;
  • the main page still covers the common task end to end;
  • reference pages are complete for the scope they claim.

Evidence to record

  • The inventory with each fact's fate.
  • The source you checked each changed claim against.
  • Commands and examples you ran, with results.
  • Broken links found and fixed.

Stop conditions

Stop and report when the code and an existing test disagree about the behaviour, when a claim cannot be verified from code or output, or when the change needs a docs structure decision the task did not make.

Handoff

Report the pages changed, the facts moved or deleted with their destination or proof, the examples run, unverified claims left in place, and suspected code bugs.

Fact inventory and source-of-truth steps adapted from openclaw's openclaw-refactor-docs skill (MIT, OpenClaw Foundation); see ../LICENSE-openclaw.

© hex, 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 mods/council-pane/specialists/docs-updater of hex/claude-council.

Open the folder on GitHubat commit 23867e1

Compare with similar skills

Docs Updater 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.

Docs Updater compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Docs Updater this skillhex/claude-council843—~930Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k24 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-code78k5 repos~1.1kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT

Similar skills

  • 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.

    296k 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 24 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 5 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

  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 22 repos~577 tokens
    DevelopmentAuto-check passed

More from hex/claude-council

All 10 skills in this repo

  • Local Council Execution

    hex/claude-council

    Runs a local council when no external AI providers are configured.

    843 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed

  • Council Execution

    hex/claude-council

    Executes council queries by running the query pipeline across selected AI providers (Gemini, OpenAI, Grok, Perplexity), displaying formatted responses verbatim, and generating a synthesis of…

    843 GitHub stars~824 tokensUpdated yesterday
    Auto-check passed

  • Deep Execution

    hex/claude-council

    Executes agent-enhanced council queries as one Workflow of parallel Claude analyst agents that each query a provider, evaluate response quality, ask follow-up questions, and return a schema-enforced…

    843 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed

  • Provider Integration

    hex/claude-council

    Adds new AI providers to claude-council, configures provider API settings, troubleshoots provider connections, and documents the provider script interface.

    843 GitHub stars~635 tokensUpdated yesterday
    Auto-check passed

  • Bug Fixer

    hex/claude-council

    A bug reproduces, the expected behaviour is clear, and the fix stands apart from the current work.

    843 GitHub stars~991 tokensUpdated yesterday
    Auto-check passed

  • CI Fixer

    hex/claude-council

    A CI job fails on a named revision and the fix belongs in code, config or tests, not in the CI provider.

    843 GitHub stars~941 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Docs Updater

What does Docs Updater do?

Docs must be updated or restructured to match code that already changed: README, reference pages, CLI help or config docs. Docs Updater is an agent skill from hex/claude-council. Docs must be updated or restructured to match code that already changed: README, reference pages, CLI help or config docs.

When should I use Docs Updater?

Docs Updater fits situations like: development work in your project.

How do I install Docs Updater in Claude Code?

Run `npx skills add hex/claude-council --skill docs-updater -a claude-code`. Or copy the skill folder (mods/council-pane/specialists/docs-updater in hex/claude-council) into .claude/skills/docs-updater in your project. Claude Code loads it when a task matches its description.

How do I install Docs Updater in Codex?

Run `npx skills add hex/claude-council --skill docs-updater -a codex`. Or copy the skill folder (mods/council-pane/specialists/docs-updater in hex/claude-council) into .agents/skills/docs-updater in your project. Codex loads it when a task matches its description.

Can I use Docs Updater 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 hex/claude-council --skill docs-updater -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs-updater, .gemini/skills/docs-updater, .github/skills/docs-updater and .opencode/skills/docs-updater in your project.

What does Docs Updater need to run?

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

Does Docs Updater 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 Docs Updater 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 Docs Updater use?

Docs Updater 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 Docs Updater use?

About 930 tokens (SKILL.md is roughly 3.7k 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 Docs Updater?

Skills that share tags, products or a category with Docs Updater: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Docs Updater?

hex (a GitHub user) maintains it in hex/claude-council, which has 843 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 6, 2026.

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