| name | description |
|---|---|
blog-edit |
Review AI Wow blog posts for style and clarity improvements. Checks for brevity, directness, unnecessary hedging, and maintains the author's informal, punchy style. |
This skill reviews AI Wow blog posts for style and clarity improvements.
- The user will provide a blog post file path or content to review
- Review for style and clarity improvements using the guidelines below
- Provide numbered, specific feedback with line references
- Format: quote → issue → rewrite
- Review for style improvements
- Apply the writing quality priorities below
- Only flag meaningful improvements that significantly enhance clarity and impact
When editing, check adherence to these principles of cooperative communication:
- Quantity: Is the text informative enough without being excessive? Flag over-explanation and filler.
- Quality: Are claims supported? Flag unsupported assertions or false confidence.
- Relation: Is everything relevant? Flag tangents and content that doesn't serve the reader.
- Manner: Is it clear and well-ordered? Flag ambiguity, obscurity, and unnecessary complexity.
- Brevity: Flag verbose passages, redundancy, overexplanation, and opportunities to be more concise
- Directness: Remove unnecessary hedging (e.g., "I think", "I believe", "perhaps", "maybe", "somewhat"). Replace hedging conditionals with assertions: "If you're getting serious about..." → "When you get serious about..."
- Unnecessary detail: Cut details that don't add meaningful information or context. Flag prepositional phrases and clauses that can be removed without losing the point (e.g., "when I'm at my desk", "in my experience", "for the most part")
- Unnecessary adjectives: Cut adjectives that don't add meaning (e.g., "very", "really", "quite")
- Active voice: Prefer active constructions over passive voice
- Present tense over continuous: Prefer simple present ("I use") over present continuous ("I'm using") unless the continuous aspect is truly needed to convey ongoing action. Present continuous often adds unnecessary wordiness.
- Sentence variety: Flag monotonous sentence structures or repetitive patterns
- Precision: Replace vague words with specific ones. Fix common misusages: "less than 5" → "fewer than 5" (use "fewer" for countable items)
- Wordy phrases: Replace multi-word phrases with simpler equivalents (e.g., "make sure to request it by saying" → "say", "in order to" → "to", "due to the fact that" → "because")
- Awkward parentheticals: Flag parenthetical asides that interrupt flow; often the information can be integrated more smoothly or removed (e.g., "since (currently) it doesn't" → "as it doesn't")
- Titles: Prefer imperative or declarative titles over questions. "What progress did I make on my OKRs?" → "Make an OKR progress report"
- Links and references: Flag inline mentions of tools or concepts that could be linked to a relevant page on the site. Suggest adding section anchors to links for specificity where appropriate
- Be direct and confident - state claims rather than hedging them
- Professional but accessible - conversational without being unprofessional
- Action-oriented - prefer clear, concrete language
- Concise and scannable - every sentence should earn its place
Use British English: learnt, favourite, colour, analyse, behaviour, organised, realise.
Sentence case, not Title Case:
- ✓ "Everyone should use Claude Code"
- ✗ "Everyone Should Use Claude Code"
Full sentences get full stops. Fragments can omit them, but be consistent within a single list.
Footnotes go after punctuation: sentence.[^1] not sentence[^1].
When following quoted text, the footnote goes after the period: "quoted text".[^1]
- Em-dashes (—): For parenthetical asides, no spaces: "This tool—which I use daily—is great."
- En-dashes (–): For numeric ranges: "1–5 years", "pages 10–15"
- Hyphens (-): Only for compound words: "AI-assisted", "real-time"
Straight double quotes: "text" (not curly quotes, not single quotes)
- Backticks for code, commands, file names:
`yarn build` - Normal capitalisation for product names: Claude, ChatGPT, Zapier
Check for consistent formatting within sections:
- If one list item uses bold labels, all should
- If one item capitalises "New", parallel items should too (e.g., "Trigger: New support request" not "Trigger: new support request")
- Verb forms should be consistent across parallel items (e.g., all present tense: "takes", "looks", "drafts" or all imperative: "Take", "Look", "Draft")
The author's style is informal, direct, and extremely concise. These are GOOD examples to match:
✓ "Airtable are weirdly bad at quickly illustrating the feature. So here's a 1-minute demo:" ✓ "At the time of writing, none of the major LLMs can properly read Google Docs comments. 🤦 😭" ✓ "It may take longer than you think to get things working reliably." ✓ "GPT-5 Pro is not an option, sadly." ✓ "Field agents let you quickly send lots of prompts to LLMs, and get the results back in a spreadsheet."
Do NOT suggest changes that would make the writing more formal, academic, or verbose.
Preserve:
- Occasional emojis where they add tone
- Casual asides like "sadly", "happily"
- Short, punchy sentences
- Direct critiques of tools/products
- Conversational transitions like "So here's..."
Provide style and clarity improvement suggestions.
Number each item. Include line reference, quote, issue, and rewrite.
If no style improvements needed, state: "No style suggestions."
Important: Only flag meaningful improvements. Don't nitpick. Prioritize changes that significantly improve clarity and impact.
1. Line 11: Unnecessary hedging
"I think this is probably the best approach for most users."
Remove hedging words for more direct statement.
→ "This is the best approach for most users."
2. Line 42: Verbose
"In order to get started with using this tool, you'll need to first install it."
Remove filler words.
→ "To use this tool, install it first."
3. Line 58: Passive voice
"The feature can be enabled by clicking the settings button."
Use active voice for clearer action.
→ "Click the settings button to enable the feature."
4. Line 12: Present continuous tense
"At this point, I'm using LLMs enough that it's worth having them visible."
Use simple present tense for clearer, more direct statement. Remove filler phrase "at this point."
→ "I now use LLMs enough that it's worth having them visible."
5. Line 18: Unnecessary detail
"So when I'm at my desk, I have a screen that's nearly always just for them."
The phrase "when I'm at my desk" doesn't add meaningful information to the point.
→ "So I have a screen that's nearly always just for them."
6. Line 25: Wordy phrase with awkward parenthetical
"Just make sure to request it by saying "Use your front-end design skill", since (currently) it doesn't always activate when it should."
"make sure to request it by saying" is wordy—simplify to "say". The parenthetical "(currently)" interrupts flow awkwardly; "since" can become "as".
→ "Just make sure to say "use your front-end design skill", as it doesn't always activate when it should."