A documentation update workflow for cluster-cli, a command-line tool. It checks the implementation of features, keyboard shortcuts, command options, integrations, health scoring, configuration, and output formats before updating the documentation.

Use it after changing cluster-cli features, key bindings, command-line flags, subcommands, integrations, health calculations, configuration, or JSON output.

It reduces the risk of documentation describing behavior that the code does not actually have. It keeps documentation aligned when the tool changes.

How sharat/cluster-cli configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to sharat/cluster-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/sharat/cluster-cli/main/.agents/skills/update-docs/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/sharat/cluster-cli

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sharat/cluster-cli/update-docs/github.svg)](https://agentmods.dev/skills/sharat/cluster-cli/update-docs)

Your own site

<a href="https://agentmods.dev/skills/sharat/cluster-cli/update-docs"><img src="https://agentmods.dev/badge/skills/sharat/cluster-cli/update-docs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sharat/cluster-cli/update-docs"><img src="https://agentmods.dev/badge/skills/sharat/cluster-cli/update-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,574 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00033	$0.01574
Opus 5.5	$0.00013	$0.00630
Sonnet 5.5	$0.00007	$0.00315
Haiku 4.5	$0.00003	$0.00157

Measured yesterday against content hash 10a6aac790ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

update-docs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/update-docs/SKILL.md · 154 lines

How it starts

The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Update Documentation Skill

Use this skill when cluster-cli features, key bindings, CLI flags, or MCP tools have changed and the documentation needs to be regenerated.

When to Use

New features added (timeline view, workload popup, export, etc.)
Key bindings changed or added (dashboard, pod detail, node detail, timeline)
CLI flags or subcommands modified (status, incidents, pods, nodes, logs, mcp)
MCP tools added, removed, or changed (get_cluster_health, list_pods, etc.)
Health scoring algorithm updated
Configuration options changed

Steps

1. Read the Code as Source of Truth

Before updating any documentation, read the actual implementation:

Key bindings: src/events/handler.rs - all keyboard shortcuts
CLI interface: src/cli.rs - all flags, subcommands, aliases
MCP tools: src/mcp.rs - tool names, parameters, descriptions
Health scoring: src/data/health.rs - penalties, thresholds, constants
Timeline: src/data/timeline.rs and src/ui/views/timeline.rs
Configuration: src/config.rs - all config fields
JSON schema: src/json_output.rs - headless API structure

Critical: Never document features that don't exist in the code. Verify every key binding, flag, and tool.

2. Update Documentation Files

Update each affected file in docs/:

overview.md: High-level features, architecture, troubleshooting
installation.md: Installation methods, platforms, prerequisites
quick-start.md: 5-minute getting started guide
ui.md: Complete key binding reference for all views
health.md: Health score calculation, incident system, thresholds
configuration.md: Config file, CLI args, environment variables
headless.md: JSON API for all subcommands
mcp.md: MCP server setup, tools, examples for all AI clients
timeline.md: Timeline features, entry types, precursor detection
README.md: Documentation index with links

3. Regenerate the Landing Page

Read the full file on GitHub · 154 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

landing-page-template.md 7.0 KB

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 154 lines · 33 tokens per session scan A 10a6aac790ae

Subscribe to this mod's changes

update-docs is a skill published in the GitHub repository sharat/cluster-cli (9 stars, last pushed 16d ago), licensed MIT. It adds 33 tokens to every session and 1,574 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-07.

Writing and docs

update-docs next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
update-docssharat/cluster-cli	Skill	9	16d ago	MIT	A	33	Claude Code, Codex
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	yesterday	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	today	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code

cluster-cli: Skill for Claude Code