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.
86
80%
Does it follow best practices?
Impact
98%
1.55xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/document-writer/SKILL.mdQuality
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 excels at trigger term coverage and completeness with an explicit 'Use when' clause and cross-references to related skills. The main weakness is that the capabilities described are somewhat abstract (style guide, structure patterns) rather than listing concrete discrete actions.
Suggestions
Add more specific concrete actions, e.g., 'Formats headings, applies MDC components like ::callout and ::code-group, structures frontmatter' 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 | 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' and adds cross-references to related skills). | 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 of Nuxt content/MDC-based blog and documentation writing. The combination of writing style guidance with MDC component usage and references to nuxt-content and nuxt-ui creates a clear, non-overlapping identity. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
70%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 progressive disclosure and clear workflow. Its main weaknesses are moderate verbosity (explaining things Claude already knows like modal verb meanings and basic grammar rules) and reliance on external reference files for the core actionable content, making the skill itself more of a routing document than a self-contained guide. The example and checklist add good concrete value.
Suggestions
Remove the modal verbs table and 'Documentation must be' bullet list—Claude already understands grammar and modal verb semantics; replace with project-specific conventions if any exist.
Inline the most critical writing-style patterns (e.g., top 3-5 rules) directly in the skill rather than requiring a file load for basic prose tasks, so the skill is actionable without external references.
| 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 explaining basic grammar expectations is also somewhat redundant. However, the tables and quick references are well-structured and dense. | 2 / 3 |
Actionability | Provides a concrete example and a checklist, which are helpful. However, the actual writing guidance is mostly delegated to reference files rather than being directly actionable in the skill itself. The quick reference tables give patterns but are thin on executable detail—the skill relies heavily on loading external files for the real substance. | 2 / 3 |
Workflow Clarity | The 4-step workflow is clear and appropriately sequenced, with step 3 explicitly including a validation/revision feedback loop ('if any item fails, revise and re-check'). The checklist at the end serves as a concrete validation checkpoint. For a writing-focused skill, this level of workflow clarity is sufficient. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview in the skill body, 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 to load files selectively rather than all at once. The checklist format for file loading is a nice touch. | 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
00fb59d
- 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.