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.
87
81%
Does it follow best practices?
Impact
98%
1.55xAverage score across 3 eval scenarios
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 is a solid skill description that clearly communicates when to use it and what it provides. It has strong trigger terms specific to the Nuxt/MDC ecosystem and good completeness with an explicit 'Use when' clause. The main weakness is that the capabilities described are somewhat abstract (style guide, structure patterns) rather than listing concrete discrete actions.
Suggestions
Make capabilities more concrete by listing specific actions, e.g., 'Structures frontmatter, applies heading hierarchy, inserts MDC components like ::alert and ::code-group' instead of abstract 'content structure patterns and MDC component usage'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (blog posts, documentation markdown files) and mentions some actions (writing style guide, content structure patterns, MDC component usage), but doesn't list multiple concrete discrete actions—it's more about guidelines than specific operations like 'create', 'format headers', 'insert components'. | 2 / 3 |
Completeness | Clearly answers both 'what' (provides writing style guide, content structure patterns, MDC component usage, overrides brevity rules) and 'when' (explicitly starts with 'Use when writing blog posts or documentation markdown files'). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'blog posts', 'documentation', 'markdown files', 'writing style', 'MDC', 'nuxt-content', 'nuxt-ui'. These cover terms users would naturally use when requesting help with content writing in a Nuxt ecosystem. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with its specific niche: Nuxt content/MDC-based blog and documentation writing with specific style rules. The combination of MDC components, nuxt-content, nuxt-ui, and writing style guidance creates a clear, non-overlapping niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%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 documentation writing skill with strong progressive disclosure and actionable guidance. The quick reference tables, concrete example, and checklist make it immediately usable. Minor weaknesses include some redundancy between the 'Available References' and 'Loading Files' sections, and the workflow could have slightly more explicit validation steps.
Suggestions
Merge the 'Available References' and 'Loading Files' sections into a single section to eliminate redundancy and save tokens.
Condense the 'Writing Standard' override section to a single line like: '**Override**: Use proper grammar and complete sentences here — brevity rules do NOT apply to documentation.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables for quick reference, but some sections are slightly redundant (e.g., the 'Loading Files' section repeats what's already in 'Available References'). The 'Writing Standard' section explains things Claude can infer from a shorter directive. Could be tightened. | 2 / 3 |
Actionability | Provides concrete writing patterns with specific examples, a complete markdown example showing real output, clear modal verb definitions, and a checklist with measurable criteria (e.g., 'Active voice 85%+'). The guidance is specific and directly usable. | 3 / 3 |
Workflow Clarity | The workflow has 4 steps with a reference to the checklist for verification, which is good. However, step 3 says 'if any item fails, revise and re-check' but doesn't specify what to do if issues persist. The feedback loop is present but implicit rather than explicit with clear validation checkpoints. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview, well-signaled one-level-deep references to writing-style.md and content-patterns.md, explicit guidance on when to load each file, and cross-references to related skills (nuxt-content, nuxt-ui). The checklist approach for selective loading is particularly well done. | 3 / 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
- onmax/nuxt-skills
- Commit
3110745
- 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.