Transform brain dumps into polished blog posts in Nick Nisi's voice. Use when the user wants to write a blog post with scattered ideas, talking points, and conclusions that need organization into a cohesive narrative with Nick's conversational, authentic, and thoughtful tone.
View on GitHubplugins/content/skills/blog-post-writer/SKILL.md
February 5, 2026
Select agents to install to:
npx add-skill https://github.com/nicknisi/claude-plugins/blob/main/plugins/content/skills/blog-post-writer/SKILL.md -a claude-code --skill blog-post-writerInstallation paths:
.claude/skills/blog-post-writer/# Nick Nisi Blog Writer Transform unstructured brain dumps into polished blog posts that sound like Nick Nisi. ## Process ### 1. Receive the Brain Dump Accept whatever the user provides: - Scattered thoughts and ideas - Technical points to cover - Code examples or commands - Conclusions or takeaways - Links to reference - Random observations Don't require organization. The mess is the input. ### 2. Read Voice and Tone Load `references/voice-tone.md` to understand Nick's writing style. Key characteristics: - Conversational yet substantive - Vulnerable and authentic - Journey-based narrative - Mix of short and long sentences - Specific examples and real details - Self-aware humor ### 3. Check for Story Potential Read `references/story-circle.md` to understand the narrative framework. Determine if the content fits a story structure: - Is there a journey from one understanding to another? - Can you identify a problem and resolution? - Does it follow: comfort → disruption → return changed? Not every post needs the full Story Circle, but look for narrative opportunities. ### 4. Organize Content Structure the material into sections: **Common structures:** - Problem/experience → Journey → Results → Lessons - Setup → Challenge → Discovery → Application - Philosophy → How-to → Reflection - Current state → Past → Learning → Future Choose the structure that fits the content. ### 5. Write in Nick's Voice Apply voice characteristics: **Opening:** - Hook with current position or recent event - Set up tension or question - Be direct and honest **Body:** - Vary paragraph length - Use short paragraphs for emphasis - Include specific details (tool names, commands, numbers) - Show vulnerability where appropriate - Use inline code formatting naturally - Break up text with headers **Technical content:** - Assume reader knowledge but explain when needed - Show actual commands and examples - Be honest about limitations - Use casual tool references **Tone modula