// Comprehensive writing review — spawns analyser agents for thorough quality and voice assessment. Use when the user asks for a "full check", "thorough review", "comprehensive edit", or wants detailed quality analysis of their writing.
This skill should be used when the user invokes "/personal:dev" with a subcommand. Subcommands: init (project + task setup), new (create task from description or GH issue), complete (finish a task), renumber (reorder task priorities), prime (load project context).
This skill should be used when the user invokes "/personal:morning" to start their morning planning session. Provides briefing, task overview, and guided day planning conversation.
Danny's writing and editing guide. Use when writing, editing, or reviewing text of any kind. Covers general writing principles, Danny's distinctive voice, style rules, and anti-slop patterns. Use for blog posts, docs, emails, proposals, personal essays, knowledge base articles, GitHub issues, or any other non-trivial text intended for others to read. Also use for quality checking and deslopping.
Remove AI slop and corporate bullshit from text — produces clean, natural, human-sounding writing. Use when the user asks to "unslopify", "deslop", "remove slop", "clean up AI text", or wants text cleaned of AI-sounding language without applying Danny's specific voice.
Rewrite text in Danny's distinctive voice — conversational, substantive, cuts through bullshit. Use when the user asks to "danify", "rewrite in my voice", "make this sound like me", or wants text transformed into Danny's writing style.
Quick writing quality check — scans for slop, style issues, spelling/grammar errors. Use when the user asks for a "quick check", "quick review", "scan for issues", or wants a fast quality pass without full voice analysis.
| name | fullcheck |
| description | Comprehensive writing review — spawns analyser agents for thorough quality and voice assessment. Use when the user asks for a "full check", "thorough review", "comprehensive edit", or wants detailed quality analysis of their writing. |
| argument-hint | [file/dir/text] |
| disable-model-invocation | true |
Thorough quality review using writing-analyser subagents. Use this for important documents that need a proper edit.
Figure out what to check:
Launch writing-analyser subagents in parallel using the Task tool. Split the work sensibly:
For a single document:
For multiple documents:
Give each agent clear instructions about what to focus on and pass the file path(s) or text.
Once the agents return, compile their reports into a single comprehensive review:
## Overall Assessment
[2-3 sentences: what's the text doing well, what needs the most work]
## Critical Issues
[Must fix — slop, errors, broken clarity]
## Warnings
[Should fix — weak language, structural problems, voice misses]
## Suggestions
[Nice to have — polish, enhancement opportunities]
## CLI Tool Output
[If agents ran write-good/proselint, include notable findings here]
Keep the compiled report concise and actionable. The user wants to know what to fix, not read an essay about their essay.