write
Write prose that avoids AI tells through an iterative workflow. Gathers your context, writes using research-backed principles, reviews via writing-reviewer agent, auto-fixes HIGH+ issues, loops until clean. Use for articles, blog posts, emails, marketing copy, social media. Triggers: write content, draft article, write blog post, write email, write copy.
What this skill does
**User request**: $ARGUMENTS
Write prose content that reads as authentically human, not AI-generated.
## Goal
Gather the writer's context (the 70%) → write content applying human-writing principles → review via writing-reviewer → auto-fix HIGH+ issues → loop until reviewer finds no HIGH+ issues → deliver.
## Input Detection
Adapt based on what's provided:
| Input | Entry Point |
|-------|-------------|
| **Topic only** | Gather context → outline → write → review loop |
| **Topic + outline** | Gather context → write from outline → review loop |
| **Rough draft** | Gather context for gaps → rewrite applying principles → review loop |
| **Finished text** | Skip writing, run review loop only (editing mode) |
| **No input** | Ask what to write |
## Gather Context (The 70%)
Before writing anything, gather the writer's substance. This is the primary quality driver — prompting and editing are the remaining 30%.
Ask via AskUserQuestion:
- **What's your take?** Key points, thesis, or argument you want to make
- **Personal experience?** Specific anecdotes, examples, observations to include
- **Opinions?** What do you believe about this? What's your angle?
- **Specifics?** Names, numbers, dates, details that ground the piece
- **Audience?** Who reads this and what should they walk away with?
- **Tone?** How should this feel? (Conversational, authoritative, provocative, casual)
If the user provides a rough draft, extract their existing substance and ask only about gaps.
## Write
Invoke the `writing:human-writing` skill to apply research-backed writing principles during generation.
Write the content to `draft-{topic-slug}.md` in the current working directory. Use a slugified version of the topic for the filename.
Incorporate the user's context as the core substance. Apply the principles from human-writing: avoid kill-list vocabulary, vary sentence length and structure, break symmetry, include specificity, take positions, embrace imperfection.
## Review Loop
After writing (or receiving finished text for editing):
1. **Review**: Invoke the `writing-reviewer` agent on the draft file
2. **Auto-fix**: Fix all CRITICAL and HIGH severity `AUTO_FIXABLE` issues
3. **Report**: Present MEDIUM and LOW issues to the user (informational, not blocking)
4. **Present NEEDS_HUMAN_INPUT**: Show HIGH+ `NEEDS_HUMAN_INPUT` issues to user with options; skip if user declines
5. **Loop**: If fixes were applied, re-review. Continue until reviewer finds no HIGH+ issues.
**Convergence guard**: If a fix cycle introduces new HIGH+ issues (total HIGH+ count increases instead of decreasing), stop and present the situation to the user rather than continuing to loop.
## Constraints
| Constraint | Why |
|------------|-----|
| **Context before content** | Never generate prose without the writer's substance first |
| **Converge, don't cap** | No arbitrary iteration limit — run until no HIGH+ issues |
| **Convergence guard** | Stop if fixes create new problems — don't oscillate |
| **DRY** | Delegate principles to human-writing, review to writing-reviewer |
| **File output** | Write to `draft-{topic-slug}.md` in cwd |
| **Atomic** | Working draft updated in place; user sees final clean version |
## Output
Report when done:
- File path
- Review iterations completed
- Issues fixed (auto) vs reported (to user)
- NEEDS_HUMAN_INPUT items presented and their resolution
- Summary of key changes made during review cycles
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.