SomtoUgeh/somto-dev-toolkit / skills/blog-post-writer
blog-post-writer
VerifiedTransform 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.3 KB |
| references/story-circle.md | markdown | 2.8 KB |
| references/technical-storytelling.md | markdown | 2.1 KB |
| references/voice-tone.md | markdown | 5.0 KB |
references/technical-storytelling.md
View on GitHub# Technical Storytelling Patterns
From analyzing effective technical blog posts.
## Narrative Frame
Open with personal context that transforms technical content into experience:
- "It's the holidays. Everyone's supposed to be taking a break. Instead, X messages me..."
- Hook via relatable interruption or moment
- Establish intimacy before diving into tech
## Sentence Rhythm
Vary length dramatically for pacing:
**Punchy fragments for emphasis:**
- "One tool call."
- "An hour. That's fast."
- "It worked."
**Then expand into complex explanations when needed.**
This alternation maintains engagement across dense material.
## Paragraph Structure
- Keep paragraphs concise (3-5 sentences)
- Prevent information overload
- Key concepts get their own section breaks
- Casual subheadings: "The Thing About X" not "Understanding X Architecture"
## Layered Technical Explanations
Don't define concepts academically. Instead:
1. Introduce abstractly
2. Ground in concrete scenario
3. Show measurable impact (98.7% reduction, 3x faster)
4. Code appears embedded in explanation, not isolated
**Bad:** "Tool calls are a mechanism by which..."
**Good:** "Here's the thing about tool calls - every time the model wants to do something, it costs tokens. We were burning through them just filtering documents."
## Parenthetical Personality
Add asides that show self-awareness:
- "(new)"
- "(exaggerating here but you get the drift)"
- "(I'll explain why in a sec)"
Acknowledges imprecision, builds trust.
## Progressive Disclosure
When addressing concerns:
1. Validate the concern first
2. Then immediately explain the solution
3. Don't let objections hang
## Opening/Closing Loop
- **Open:** Narrative hook, relatable context
- **Close:** Circle back to practical application
- End with actionable next step, not abstract summary
- Final line can be casual/friendly: "maybe try X yourself π"
## Flow Pattern
Ideas progress: **problem β insight β solution β implementation β results**
Minimal transitional phrases. Let subheadings and visual elements carry readers forward.
Match natural curiosity: "why this matters" β "how we built it" β "what you can do"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |