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.
74%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills_all/blog-post-writer/SKILL.mdTransform unstructured brain dumps into polished blog posts that sound like Nick Nisi.
Accept whatever the user provides:
Don't require organization. The mess is the input.
Load references/voice-tone.md to understand Nick's writing style.
Key characteristics:
Read references/story-circle.md to understand the narrative framework.
Determine if the content fits a story structure:
Not every post needs the full Story Circle, but look for narrative opportunities.
Structure the material into sections:
Common structures:
Choose the structure that fits the content.
Apply voice characteristics:
Opening:
Body:
Technical content:
Tone modulation:
Ending:
Check the post:
Show the post to the user for feedback and iterate.
"AI is going to replace developers."
I must have heard that phrase a hundred times in the last year.I've been thinking a lot about how we use AI in our daily work.Then something clicked.
I watched it use rg to search through codebases, just like I would.I won't lie – joining Meta was intimidating.I watched it use `rg` to search through codebases, just like I would.
It ran `npm test` to verify its changes weren't breaking anything.You're not being replaced; you're being amplified.references/voice-tone.md - Complete voice and tone guide. Read this first to capture Nick's style.references/story-circle.md - Story Circle narrative framework. Check if content fits a story structure.User provides brain dump:
thoughts on using cursor vs claude code
- cursor is in IDE, feels familiar
- but claude code is in terminal, my natural environment
- tried cursor first, felt weird leaving vim
- claude code met me where I was
- not about which is better, about workflow fit
- some devs love IDE integration
- I need terminal access
- conclusion: use what fits YOUR workflowProcess:
Microck/ordinary-claude-skills
1056d29
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.