voice-analyzer
Voice Analyzer
Transform writing samples into a codified voice style that can be replicated consistently.
Purpose
This skill analyzes 3-5 samples of writing to extract the patterns, techniques, and characteristics that define a distinctive voice. The output is a complete voice skill that can be used alongside anti-ai-writing to produce content in that voice.
Core Philosophy: Every distinctive writer has patterns - conscious or unconscious. By identifying and codifying these patterns, we can replicate voice authentically without losing what makes it human.
When to Use This Skill
- Establishing your own writing voice for consistent content
- Codifying a brand voice for team use
- Creating voice guides for ghostwriting clients
- Analyzing competitors or inspirations to understand their approach
- Building a library of voice styles for different contexts
Requires: 3-5 writing samples of 500+ words each (more samples = better analysis)
More from michael-f-bryan/skills
long-running-agent-harness
Plans and structures large-scale work for AI agents across many sessions. Human and AI iterate to produce a design doc; run an Initializer sub-agent once to create feature list, runbook, and backlog in _working/; then repeatedly run a Coding sub-agent until all features pass. At milestones (e.g. end of a work-unit group), pause for human check-in, re-run Initializer, then continue. Prompts are passed to sub-agents when spawning (no copying into .cursor/rules). Use when planning multi-session agent work, long-horizon coding from a design, or handoff between coding sessions.
31working-docs
Use when handling multi-step tasks, investigations, or long sessions where working notes, interim findings, and scratch planning are needed to keep context and handoffs clear.
23doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
23test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
19commit-messages
When suggesting or writing commit messages for this repo, follow these rules.
17code-like-michael
Write, refactor, and review code in Michael's style; explicit contracts, thin entrypoints, practical boundaries, anti-ceremony abstractions, deterministic tooling, and architecture that scales from function internals to repository shape.
16