Draft and rewrite general-purpose editorial, business, product, support, and internal written content when no more specialized writing skill is the better fit. Use when the main task is producing a clear, audience-aware first draft or clean rewrite for general communications, explainers, summaries, newsletters, product education, internal memos, or mixed-format content. Treat this as a broad editorial drafting skill, not the default for conversion copy, blog strategy, technical documentation, or UX microcopy.
Write clear, useful content that matches audience, channel, and goal.
This skill is the general editorial drafting fallback for the catalog. It exists for solid first drafts, clean rewrites, and mixed-format writing tasks that do not clearly belong to a more specialized writing skill. It should not cannibalize copywriting, blog writing, documentation, technical writing, or UX microcopy.
Use this skill for:
Do not use this skill for:
Route to content-writer when the main need is:
If a more specific writing format clearly fits, prefer that specialist skill.
content-writer should be the fallback, not the default winner.
Before drafting, identify:
If important details are missing, make minimal assumptions and surface them.
Return outputs such as:
Aim for a draft that can be reviewed or sent, not a placeholder.
Clarify:
Decide the backbone first:
Structure usually matters more than wordsmithing.
Default to:
Tune voice based on use case:
Use only supported facts from provided context or trusted sources. If facts are missing, use placeholders or caveats instead of inventing specifics.
Remove:
Prefer:
Avoid:
Use content-writer for:
Do not use content-writer for:
A strong result should:
Use prompt.md for drafting stance and response shape.
Use guides/qa-checklist.md before finalizing.
Use examples/README.md for output patterns.
Use meta/skill.json for boundaries and metadata.