document-writer
tessl i github:onmax/nuxt-skills --skill document-writerUse 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.
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
Implementation
73%This is a well-structured skill that efficiently organizes writing guidance with good progressive disclosure to reference files. The main weakness is limited actionability - while it tells Claude what patterns to follow, it lacks concrete before/after examples of documentation writing or executable templates. The checklist provides validation but the workflow for actually writing documentation could be more explicit.
Suggestions
Add a concrete before/after example showing a poorly-written paragraph transformed using the writing patterns
Include a brief workflow sequence: 'When writing docs: 1. Draft content 2. Apply writing patterns 3. Verify against checklist 4. Add appropriate callouts'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference instead of verbose explanations. It assumes Claude knows what Nuxt, MDC, and documentation writing are without explaining basics. | 3 / 3 |
Actionability | Provides concrete patterns and examples in tables, but lacks executable code examples. The writing patterns show format but not complete before/after examples of actual documentation content. | 2 / 3 |
Workflow Clarity | The checklist at the end provides validation criteria, but there's no clear workflow sequence for writing documentation. Missing explicit steps like 'draft → review against checklist → revise' for the writing process. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear one-level-deep references to writing-style.md and content-patterns.md. The 'Load based on context' section clearly signals when to access each reference file. | 3 / 3 |
Total | 10 / 12 Passed |
Activation
100%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 |
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.