document-writer
Use when writing blog posts or documentation markdown files - provides writing style guide (active voice, present tense), content structure patterns, and MDC component usage. Overrides brevity rules for proper grammar. Use nuxt-content for MDC syntax, nuxt-ui for component props.
100
Does it follow best practices?
Validation for skill structure
Discovery
100%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 is a strong skill description that clearly defines its purpose for Nuxt-based content writing with specific style guidelines and component usage. It effectively uses the 'Use when' pattern, includes natural trigger terms, and establishes a distinct niche. The cross-references to related skills (nuxt-content, nuxt-ui) add helpful context for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'writing style guide (active voice, present tense)', 'content structure patterns', 'MDC component usage', and 'Overrides brevity rules for proper grammar'. Also specifies related skills to use. | 3 / 3 |
Completeness | Clearly answers both what (provides writing style guide, content structure patterns, MDC component usage) and when (writing blog posts or documentation markdown files) with explicit 'Use when' clause at the start. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'blog posts', 'documentation', 'markdown files', 'writing style', 'MDC', 'nuxt-content', 'nuxt-ui'. Good coverage of both general and technical terms. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting Nuxt-specific blog/documentation writing with MDC components. The combination of 'blog posts', 'documentation markdown', 'MDC', and Nuxt-specific references creates a distinct trigger profile unlikely to conflict with general writing or coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%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-crafted skill that efficiently communicates documentation writing standards for the Nuxt ecosystem. It excels at progressive disclosure by keeping the main file scannable while pointing to detailed references, provides actionable examples and patterns, and includes a clear workflow with validation. The explicit override of brevity rules for documentation writing is a smart contextual adaptation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using tables for quick reference and avoiding unnecessary explanations. It assumes Claude understands concepts like MDC, composables, and markdown syntax without over-explaining. | 3 / 3 |
Actionability | Provides concrete examples throughout: specific writing patterns with actual code snippets, a complete markdown example, clear component mappings, and an actionable checklist. The workflow is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 4-step workflow with explicit validation checkpoint ('if any item fails, revise and re-check'). The checklist provides concrete verification criteria for the writing task. | 3 / 3 |
Progressive Disclosure | Excellent structure with quick reference tables inline and detailed content appropriately delegated to one-level-deep references (writing-style.md, content-patterns.md). Clear guidance on when to load each file. | 3 / 3 |
Total | 12 / 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.
- 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.