Run npm run format to ensure consistent formatting
Rules
Don't rewrite documentation that's already correct — only fix drift
Match existing documentation style and structure
Tool descriptions in docs should be more detailed than the inputSchema description (docs are for humans, schema is for AI agents)
If a tool was removed, remove its documentation section entirely — don't leave stubs
Keep skill.md focused on AI agent patterns, not human-readable reference
1---2name: update-docs3description: Update documentation after tool changes — TOOLS.md, skill.md, README, INSTALLATION.md4argument-hint: '[tool-name or "all" to audit all docs]'5metadata:6 source: https://skillmd.com/skills/testdino-hq/update-docs7---89Update documentation: $ARGUMENTS1011## Workflow1213### Step 1 — Determine Scope1415If a specific tool is named:1617- Read the tool's source file to understand current behavior18- Check `docs/TOOLS.md` for the tool's existing documentation19- Check `docs/skill.md` for any references2021If "all" is specified:2223- Read all tool source files24- Compare against `docs/TOOLS.md` for drift25- Check tool count in `README.md`2627### Step 2 — Check for Drift2829For each tool in scope, verify:30311. **TOOLS.md**32 - Does the documented tool name match `toolDefinition.name`?33 - Does the parameter list match `inputSchema.properties`?34 - Are required/optional fields correctly documented?35 - Do example requests match the actual schema?36 - Are enum values listed and up to date?37382. **skill.md**39 - Are workflow references to tools still accurate?40 - Do decision trees point to the right tools?41 - Are parameter quick-reference tables current?42433. **README.md**44 - Is the tool count correct?45 - Are all tool names listed?46 - Do feature descriptions match reality?47484. **INSTALLATION.md**49 - Are setup instructions still valid?50 - Is the package name and version reference correct?5152### Step 3 — Update5354Fix any drift found. Follow the existing documentation style — don't reinvent the format.5556For TOOLS.md, each tool section should include:5758- Tool name and description59- Parameters table (name, type, required/optional, description)60- Example usage (request + response)61- Notes on when to use vs similar tools6263### Step 4 — Verify6465- Read the updated docs to confirm they're accurate66- Check for broken markdown formatting67- Run `npm run format` to ensure consistent formatting6869## Rules7071- Don't rewrite documentation that's already correct — only fix drift72- Match existing documentation style and structure73- Tool descriptions in docs should be more detailed than the inputSchema description (docs are for humans, schema is for AI agents)74- If a tool was removed, remove its documentation section entirely — don't leave stubs75- Keep skill.md focused on AI agent patterns, not human-readable reference
Run npx get-skill add testdino-hq/update-docs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Update Docs It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
testdino-hq (@testdino-hq) published this skill. Their other Agent Skills are listed on their SkillMD profile.