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 (blog posts and documentation markdown) and what it provides (style guide, structure patterns, MDC components). The Nuxt-specific terminology makes it highly distinctive. The main weakness is that the capabilities are described somewhat abstractly as guidelines rather than concrete actions.
Suggestions
List more specific concrete actions, e.g., 'Structures headings, formats code blocks, inserts MDC components like callouts and tabs' to improve specificity.
| 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 | Explicitly answers both 'what' (provides writing style guide, content structure patterns, MDC component usage, overrides brevity rules) and 'when' (writing blog posts or documentation markdown files), with a clear 'Use when' clause at the start. | 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 due to the specific combination of Nuxt content/UI ecosystem, MDC syntax, and writing style guidelines for blog/documentation. Unlikely to conflict with generic writing or generic Nuxt component skills due to the narrow focus. | 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 skill that excels at progressive disclosure and actionability, with clear references to companion files and concrete examples. The main weaknesses are minor verbosity (explaining things Claude already knows like modal verb meanings) and a workflow that could be slightly more detailed in its validation steps. Overall it's a solid documentation writing guide that would produce consistent results.
Suggestions
Remove the modal verbs table — Claude already understands can/should/must semantics; if project-specific usage differs from standard English, only then document it.
Trim the 'When to Use' section and 'Documentation must be' bullets, as these restate what the skill description and override statement already convey.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary content like the 'When to Use' section (Claude can infer this) and the modal verbs table which Claude already knows. The 'Documentation must be' bullet list is somewhat redundant after the override statement. However, the tables and quick references are well-structured and dense. | 2 / 3 |
Actionability | Provides concrete writing patterns with specific examples, a complete markdown example showing real usage, clear component mapping table, and an actionable checklist. The guidance is specific enough to produce consistent output (e.g., 'Subject-first', '2-4 sentences per paragraph', '85%+ active voice'). | 3 / 3 |
Workflow Clarity | The workflow has 4 steps and step 3 includes a feedback loop ('if any item fails, revise and re-check'), which is good. However, the workflow is thin — it doesn't specify how to validate callout types match intent beyond 'verify', and the loading step could be more explicit about decision criteria. The checklist serves as a validation checkpoint but is separated from the workflow. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview in SKILL.md, well-signaled one-level-deep references to writing-style.md and content-patterns.md, cross-references to related skills (nuxt-content, nuxt-ui), and explicit guidance on when to load each file. 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
48efc7a
- 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.