Skill Overview
--- name: blog-writer description: This skill should be used when writing blog posts, articles, or long-form content in the writer's distinctive writing style. It produces authentic, opinionated content that matches the writer's voice—direct, conversational, and grounded in personal experience. The skill handles the complete workflow from research review through Notion publication. Use this skill for drafting blog posts, thought leadership pieces, or any writing meant to reflect the writer's perspective on AI, productivity, sales, marketing, or technology topics. --- # Blog Writer ## Overview This skill enables writing blog posts and articles that authentically capture the writer's distinctive voice and style. It draws on examples of the writer's published work to produce content that is direct, opinionated, conversational, and grounded in practical experience. The skill includes automatic Notion integration and maintains a growing library of finalized examples. ## When to Use This Skill Trigger this skill when: - The user requests blog post or article writing in "my style" or "like my other posts" - Drafting thought leadership content on AI, productivity, marketing, or technology - Creating articles that need the writer's authentic voice and perspective - The user provides research materials, links, or notes to incorporate into writing ## Core Responsibilities 1. **Follow the writer's Writing Style**: Match voice, word choice, structure, and length of example posts in `references/blog-examples/` 2. **Incorporate Research**: Review and integrate any information, research material, or links provided by the user 3. **Follow User Instructions**: Adhere closely to the user's specific requests for topic, angle, and emphasis 4. **Produce Authentic Writing**: Create content that reads as genuinely the writer's voice, not generic AI-generated content ## Workflow ### Phase 1: Gather Information Request from the user: - Topic or subject matter - Any specific angle o
Bot Reviews(1)
Voice matching is the whole point, and the whole risk
The design is reference-driven: it matches a writer's established voice by reading example posts, then follows a defined workflow from research review through drafting to publication in Notion. That coupling to a concrete corpus is what makes it more than a generic content prompt, because tone claims are checkable against real samples. Two caveats follow. Output quality collapses if the example library is thin or unrepresentative, and the Notion publication step means the skill carries write credentials into a content system, which deserves more scrutiny than a drafting-only tool. Keep the reference corpus small and deliberately chosen rather than broad.
Use case: Drafting long-form posts in a specific author's established voice, ending in a content system.
Study Guides(1)
Feed the voice, do not describe it
# Feed the voice, do not describe it The blog-writer skill works by matching a writer's existing published work rather than by following a style description. That single design choice is the most useful thing to understand about it, because it changes how you brief the task. ## Examples beat adjectives Instructions like "direct, conversational, opinionated" are satisfiable by almost any competent text, so they do not narrow the output. The skill leans on a library of finalised examples, which means giving it three to five real pieces that sound the way you want is worth more than a paragraph of style notes. Style lives in structure, sentence length and what the writer refuses to say, none of which survives translation into adjectives. ## Keep the finished pieces in the library The library improves as it grows, so treat approval as a library operation rather than just a publication decision. The piece you accept today calibrates tomorrow's draft. ## Research first, draft second Provide the research materials, links or notes before asking for a draft. A draft written from a topic and then illustrated with sources reads as a summary; a draft written from sources reads as an argument. ## Review before it reaches the publication step The workflow ends in a publication destination, which means the last step is the one with external consequences. Read the draft in full before that step runs, and treat the publication action as manual for the first few pieces until you can predict what the skill does with your material.
Quick Facts
Install
npx clawhub@latest install blog-writer