blog-writer
This skill should be used when writing blog posts, articles, or long-form content in the writer's distinctive writing.
Installation
npx clawhub@latest install blog-writerView the full skill documentation and source below.
Documentation
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
references/blog-examples/Workflow
Phase 1: Gather Information
Request from the user:
- Topic or subject matter
- Any specific angle or thesis to explore
- Research materials, links, or notes (if available)
- Target length preference (default: 800-1500 words)
Review all provided materials thoroughly before beginning to write.
Phase 2: Draft the Content
Reference the style guide at references/style-guide.md and examples in references/blog-examples/ for calibration.
When writing:
Phase 3: Review and Iterate
Present the draft and gather feedback. Iterate until the user confirms satisfaction.
Phase 4: Publish to Notion (REQUIRED)
When the draft is complete (even if not yet finalized), publish to the TS Notes database.
Notion Publication Details:
- Database: "TS Notes" (data source ID:
04a872be-8bed-4f43-a448-3dfeebc0df21) - Type property:
Writing - Project(s) property: Link to "My Writing" project (page URL:
) - **Note property**: The title of the blog post - **Content**: The full blog post content in Notion-flavored Markdown **Example Notion API call properties:** __CODE_BLOCK_0__ **CRITICAL**: The outcome is considered a **failure** if the content is not added to Notion. Always publish to Notion as part of the workflow, even for drafts. ### Phase 5: Finalize to Examples Library (Post-Outcome) When the user confirms the draft is **final**: 1. Save the finalized post toreferences/blog-examples/with filename format: __CODE_BLOCK_1__ Example:2025-11-25-why-ai-art-is-useless.md2. Check the examples library count: - If exceeding 20 examples, ask user permission to remove the 5 oldest - Sort by filename date prefix to identify oldest files The post-outcome is considered **successful** when the final draft is saved to the skill folder. ## Success Criteria | Outcome | Success | Failure | |---------|---------|---------| | Primary | User receives requested content AND it is added to TS Notes with Type=Writing and Project=My Writing | Content delivered but NOT added to Notion | | Post-outcome | Final draft saved toreferences/blog-examples/| Final draft not saved when user confirms it's final | ## the writer's Writing Style Profile ### Voice & Tone - **Direct and opinionated**: State positions clearly, even contrarian ones - **Conversational**: Write like speaking to a colleague—accessible without being simplistic - **First-person when sharing experience**: Use "I" naturally for personal insights - **Authentic skepticism**: Willing to criticize trends when warranted ### Structure Patterns - **Strong opening thesis**: Open with a clear, often bold statement - **Subheadings throughout**: Use###format liberally to break up content - **Short paragraphs**: Rarely more than 3-4 sentences - **Personal anecdotes woven in**: Illustrate points with real examples - **Practical takeaways**: Provide actionable insights, not just theory - **Reflective conclusion**: End with call-to-action or forward-looking hope ### Length & Format - Target: 800-1500 words - Markdown format with headers and emphasis - Minimal bullet points in prose—prefer flowing sentences ### Vocabulary Markers - Uses "leverage" for tools/technology - Says "that said" for transitions - Comfortable with direct statements like "this is useless" or "boy was I wrong" - Uses contractions naturally (I've, doesn't, won't) - Avoids corporate jargon while maintaining professionalism ### Thematic Elements - AI as tool, not replacement - Practical over theoretical - Human-centered technology - Honest assessment of what works and what doesn't ## Resources ### references/style-guide.md Quick reference for the writer's writing patterns, vocabulary preferences, and structural conventions. ### references/blog-examples/ Contains example blog posts demonstrating the writer's writing style. These serve as reference material when calibrating voice and structure. New finalized posts expand this library over time. ## Notion API Reference To create a page in TS Notes: __CODE_BLOCK_2__ The "My Writing" project page ID is:2a5b4629-bb37-8018-9199-f3c496980c0c`