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.
Transforms scattered thoughts into polished blog posts in Nick Nisi's conversational, vulnerable voice. Use when organizing brain dumps into narrative-driven content with authentic storytelling and technical details.
/plugin marketplace add nicknisi/claude-plugins/plugin install content@nicknisiThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/story-circle.mdreferences/voice-tone.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 workflow
Process:
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.