update-docs
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.
86
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at trigger term coverage and completeness, providing extensive natural language triggers and clear 'when to use' guidance. The main weakness is the lack of specific concrete actions in the 'what it does' portion - it only mentions 'guided workflow' without detailing what specific documentation tasks it performs (e.g., generating API docs, updating code examples, validating links).
Suggestions
Expand the capability description to list specific actions like 'generates API references, updates code examples, validates documentation links, scaffolds new doc pages'
Restructure to lead with concrete capabilities before the trigger terms for better readability
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Next.js documentation) and mentions 'guided workflow for updating documentation based on code changes', but lacks specific concrete actions like 'generate API references', 'update code examples', or 'validate doc links'. | 2 / 3 |
Completeness | Explicitly answers both 'what' (provides guided workflow for updating Next.js documentation based on code changes) and 'when' (extensive list of trigger phrases and file patterns with 'Use when' equivalent structure). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including user phrases ('update documentation for my changes', 'check docs for this PR', 'what docs need updating'), file paths ('docs/', 'docs/01-app'), and file types ('MDX', '.mdx files'). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific Next.js documentation focus, explicit file paths like 'docs/01-app' and 'docs/02-pages', and MDX file type references that clearly distinguish it from generic documentation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability and workflow clarity. The step-by-step processes are clear with proper validation checkpoints, and the commands/templates are executable. The main weakness is that the inline templates add significant length that could be externalized for better progressive disclosure.
Suggestions
Move the API Reference and Guide templates to a separate `references/DOC-TEMPLATES.md` file and reference it from the main skill
Remove explanatory phrases like 'Use this when adding documentation for entirely new features' - the section heading already conveys this
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy. The templates section is verbose and could be referenced externally. Some explanatory text like 'Use this when adding documentation for entirely new features' is unnecessary padding. | 2 / 3 |
Actionability | Provides fully executable commands (git diff, pnpm lint), concrete file paths, complete MDX templates, and specific mapping tables. The guidance is copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit sequencing (Step 1, 2, 3...), validation checkpoints (pnpm lint, prettier-fix), and a comprehensive validation checklist before committing. The 'show user, wait for confirmation, apply' feedback loop is explicit. | 3 / 3 |
Progressive Disclosure | References external files (DOC-CONVENTIONS.md, CODE-TO-DOCS-MAPPING.md) appropriately, but the templates section is a large inline block that could be split into a separate TEMPLATES.md file. The skill is over 200 lines with content that could be externalized. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- vercel/next.js
- Commit
55bb48d
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.