craft-author-voice
Captures writing style/voice into AUTHOR_VOICE.md so AI can write like the user. Use when asked to match tone, write like me, replicate voice, or capture writing style for content generation.
What this skill does
**User request**: $ARGUMENTS
# Author Voice Skill
Create a maximally information-dense AUTHOR_VOICE.md document through iterative refinement. The resulting document enables any LLM to write content that authentically matches your voice.
## Overview
This skill supports both **creating a new voice doc** and **refining an existing one**. Users often come back multiple times to adjust their doc as their voice evolves or as they notice issues in generated content.
This skill guides you through:
0. **Check Existing** - Look for existing AUTHOR_VOICE.md; let user choose to refine or start fresh
1. **Discovery** - Clarifying questions about your voice characteristics and goals
2. **Initial Draft** - Generate first AUTHOR_VOICE.md based on your inputs (good enough to start!)
3. **Refinement Cycles** - Generate sample texts, collect your ratings/feedback, update the doc ⬅️ **THE REAL MAGIC**
4. **Completion** - Final honed document ready for AI content generation
**Returning users** can skip straight to Phase 3 to run more feedback cycles on their existing doc.
### Where the Value Comes From
The discovery questions give you a solid starting point - but **the real magic happens in Phase 3**. That's where you:
- See actual generated samples in your "voice"
- Judge them ("this doesn't sound like me")
- Give specific feedback ("too formal", "wrong words")
- Watch the voice doc evolve until it truly captures YOU
Each feedback cycle sharpens the doc. Most users need 3-5 cycles to get from "this is okay" to "this is actually me."
## Workflow
### Phase 0: Check for Existing Document
Before starting discovery, check if the user already has an AUTHOR_VOICE.md:
1. **Search for existing doc**: Use Glob to search for `**/AUTHOR_VOICE.md` in the current directory and common locations
2. **If found**: Read it and ask the user what they want to do
```
header: "Existing Voice Doc Found"
question: "I found an existing AUTHOR_VOICE.md. What would you like to do?"
options:
- "Refine it - run feedback cycles to improve accuracy"
- "Start fresh - create a new voice doc from scratch"
- "Review it - just read through what's there"
```
**If "Refine it"**: Skip to Phase 3 (Refinement Cycles) - the user is coming back to improve their existing doc.
**If "Start fresh"**: Proceed to Phase 1 (Discovery) - will overwrite the existing doc.
**If "Review it"**: Read and display the doc, then ask what they want to do next.
3. **If NOT found**: Proceed directly to Phase 1 (Discovery)
### Phase 1: Discovery
Use AskUserQuestion tool with multi-choice options for EVERY question to minimize cognitive load. If AskUserQuestion is unavailable, present numbered options and ask the user to reply with the number(s).
**Question 1: Primary Content Type**
```
header: "Content Type"
question: "What's your PRIMARY content format?"
options:
- "Twitter/X posts (short-form, punchy)"
- "LinkedIn posts (professional, insights)"
- "Blog articles (long-form, detailed)"
- "Newsletter (conversational, regular)"
- "Technical documentation (precise, instructional)"
- "Mixed - I write across multiple formats"
```
**Question 2: Voice Personality**
```
header: "Voice Tone"
question: "How would you describe your voice personality?"
options:
- "Authoritative expert - confident, direct, no-nonsense"
- "Friendly mentor - approachable, encouraging, educational"
- "Provocateur - contrarian, challenges assumptions, bold"
- "Storyteller - narrative-driven, uses examples, personal"
- "Analyst - data-driven, logical, objective"
- "Conversational peer - casual, relatable, human"
multiSelect: true (pick up to 2)
```
**Question 3: Signature Elements**
```
header: "Signatures"
question: "What signature elements define your writing?"
options:
- "Strong opening hooks"
- "Numbered lists and frameworks"
- "Personal anecdotes and stories"
- "Contrarian takes and hot takes"
- "Data and research citations"
- "Metaphors and analogies"
- "Direct calls-to-action"
- "Questions to engage readers"
- "Short punchy sentences"
- "Long flowing prose"
multiSelect: true
```
**Question 4: Vocabulary Style**
```
header: "Vocabulary"
question: "What's your vocabulary style?"
options:
- "Simple and accessible - anyone can understand"
- "Technical jargon - domain-specific terms expected"
- "Casual slang - internet-native, memes okay"
- "Formal professional - polished, corporate-appropriate"
- "Academic - precise, nuanced, scholarly"
```
**Question 5: Emotional Range**
```
header: "Emotion"
question: "What emotions do you convey in your writing?"
options:
- "Enthusiasm and excitement"
- "Calm confidence"
- "Urgency and importance"
- "Humor and wit"
- "Empathy and understanding"
- "Skepticism and critical thinking"
- "Inspiration and motivation"
multiSelect: true
```
**Question 6: Target Audience**
```
header: "Audience"
question: "Who is your primary audience?"
options:
- "Developers/Engineers"
- "Founders/Entrepreneurs"
- "Product managers"
- "Executives/Leaders"
- "General tech audience"
- "Non-technical professionals"
- "Students/Learners"
```
**Question 7: Writing Goals**
```
header: "Goals"
question: "What do you want your writing to achieve?"
options:
- "Build authority and thought leadership"
- "Drive engagement and discussion"
- "Educate and inform"
- "Entertain and delight"
- "Convert/sell (subtly)"
- "Build community and connection"
multiSelect: true
```
**Question 8: Anti-patterns**
```
header: "Avoid"
question: "What should your writing NEVER do?"
options:
- "Use corporate buzzwords"
- "Sound robotic or AI-generated"
- "Be preachy or condescending"
- "Use excessive emojis"
- "Be overly promotional"
- "Use clickbait tactics"
- "Be wishy-washy or hedging"
- "Use filler phrases"
multiSelect: true
```
**Question 9: Sample Topics** (free text acceptable here)
```
header: "Topics"
question: "List 2-3 topics you frequently write about (or paste examples of your past writing)"
```
### Phase 2: Initial Document Generation
After discovery, generate the first AUTHOR_VOICE.md. This draft is intentionally a "good enough" starting point - not perfect, but solid enough to generate samples and start the feedback loop.
Use this structure:
```markdown
# AUTHOR_VOICE.md
> This document defines [Author]'s writing voice for AI content generation.
> Feed this to any LLM before requesting content to match the author's style.
## Voice Identity
[1-2 sentences capturing the core voice essence]
## Tone Parameters
- **Primary tone**: [e.g., "Confident mentor with occasional humor"]
- **Emotional range**: [comma-separated emotions from discovery]
- **Formality level**: [1-10 scale with description]
- **Warmth level**: [1-10 scale with description]
## Structural Patterns
- **Opening style**: [how posts/articles begin]
- **Paragraph length**: [short/medium/long, typical sentence count]
- **List usage**: [when and how lists are used]
- **Closing style**: [how content ends - CTA, question, statement]
## Vocabulary Rules
### USE:
- [Specific words/phrases the author uses]
- [Technical terms that are okay]
- [Signature expressions]
### AVOID:
- [Words that feel off-brand]
- [Overused phrases to skip]
- [Tone markers to avoid]
## Content Patterns
### Hooks
[How the author grabs attention - examples of opening patterns]
### Arguments
[How the author builds points - numbered, narrative, comparison]
### Evidence
[How claims are supported - data, anecdotes, logic, authority]
### Transitions
[How ideas connect - explicit markers, implicit flow]
## Signature Moves
1. [Specific technique the author uses regularly]
2. [Another signature element]
3. [Third distinguishing characteristic]
## Anti-Patterns
NEVER:
- [Specific thing to avoid]
- [Another anti-pattern]
- [Third prohibition]
## Example Transformations
### Generic version:
"[Common way to express an idea]"
### In author's voice:
"[Same idea in the author's Related in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.