Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
Extract and document a writer's distinctive voice patterns for consistent reproduction.
Install Voice Analysis
$ npx skills add jwynia/agent-skills --skill voice-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jwynia/agent-skills voice-analysis --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/general/writing/analysis/voice-analysis .claude/skills/voice-analysis && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "voice-analysis" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/general/writing/analysis/voice-analysis into .claude/skills/voice-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "voice-analysis", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jwynia/agent-skills/tree/main/skills/general/writing/analysis/voice-analysisType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jwynia/agent-skills --skill voice-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jwynia/agent-skills voice-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/general/writing/analysis/voice-analysis .agents/skills/voice-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "voice-analysis" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/general/writing/analysis/voice-analysis into .agents/skills/voice-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "voice-analysis", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jwynia/agent-skills --skill voice-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jwynia/agent-skills voice-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/general/writing/analysis/voice-analysis .cursor/skills/voice-analysis && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "voice-analysis" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/general/writing/analysis/voice-analysis into .cursor/skills/voice-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "voice-analysis", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jwynia/agent-skills.git --path skills/general/writing/analysis/voice-analysis--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jwynia/agent-skills --skill voice-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jwynia/agent-skills voice-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/general/writing/analysis/voice-analysis .gemini/skills/voice-analysis && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "voice-analysis" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/general/writing/analysis/voice-analysis into .gemini/skills/voice-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "voice-analysis", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jwynia/agent-skills voice-analysisInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jwynia/agent-skills --skill voice-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/general/writing/analysis/voice-analysis .github/skills/voice-analysis && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "voice-analysis" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/general/writing/analysis/voice-analysis into .github/skills/voice-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "voice-analysis", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jwynia/agent-skills --skill voice-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jwynia/agent-skills voice-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/general/writing/analysis/voice-analysis .opencode/skills/voice-analysis && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "voice-analysis" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/general/writing/analysis/voice-analysis into .opencode/skills/voice-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "voice-analysis", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
voice-analysis- GitHub stars
- 170
- Token cost
- ~2.6k tokens
- SKILL.md length
- 1,155 words
- Files
- 1
- Skills in repo
- 111
- Repo updated
- First seen
- Licence
- MIT
At a glance
Extract and document a writer's distinctive voice patterns for consistent reproduction.
- Works in 8 steps: Sample Collection → Linguistic Analysis → Lexical Fingerprinting → …
- You need to capture writing voice
- SKILL.md covers Purpose, Core Principle, Phase 1: Sample Collection and Phase 2: Linguistic Analysis, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Voice Analysis is an agent skill from jwynia/agent-skills. Extract and document a writer's distinctive voice patterns for consistent reproduction. Use when you need to capture writing voice, analyze writing style, create a voice guide, or write in someone's established style. Keywords: voice, tone, style, writing analysis, fingerprint.
Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Brand voice and tone. The licence is MIT.
When your agent uses it
- You need to capture writing voice
- Analyze writing style
- Create a voice guide
- Write in someones established style
Example prompts
- “/voice-analysis”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e02ec7e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Voice Analysis loads about 2.6k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 1,155 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jwynia/agent-skills at commit e02ec7e, republished under its MIT licence (© jwynia). 1,155 words, ~2,633 tokens.
Download SKILL.mdSave it as
.claude/skills/voice-analysis/SKILL.md (or your agent's skills folder).- name
- voice-analysis
- description
- Extract and document a writer's distinctive voice patterns for consistent reproduction. Use when you need to capture writing voice, analyze writing style, create a voice guide, or write in someone's established style. Keywords: voice, tone, style, writing analysis, fingerprint.
- license
- MIT
- metadata.author
- jwynia
- metadata.version
- 1.0
- metadata.type
- utility
- metadata.mode
- evaluative
- metadata.domain
- fiction
Voice & Tone Analysis
Purpose
Extract and document a writer's distinctive voice patterns for consistent reproduction. Creates a "voice guide" that enables authentic writing that sounds like the source, not a generic approximation.
Core Principle
Capture spirit, not just mechanics. The goal is writing that makes the source say "yes, that's me" not "I guess that's accurate."
Phase 1: Sample Collection
Gather 5-10 Examples from Each Category
Peak Voice - Writing they identify as "most them"
Off-Voice - Writing that doesn't represent them well
Different Contexts:
- Technical/instructional content
- Persuasive/argumentative pieces
- Narrative/storytelling
- Casual communication (emails, messages)
- Formal communication
- Emotional/vulnerable content
Self-Report Prompts
Rewrite Exercise: Ask: "Rewrite this neutral paragraph in your voice:"
"The new policy will be implemented next month. It includes several changes to current procedures. Employees should review documentation and submit questions by the deadline."
Rule Breaking: "What writing 'rules' do you consistently ignore? Why?"
Pet Peeves: "What writing choices immediately signal something wasn't written by you?"
Evolution: "How has your writing changed in 5 years? What stayed constant?"
Phase 2: Linguistic Analysis
Sentence Level
| Pattern | What to Track |
|---|---|
| Average length | Words per sentence |
| Range | Shortest to longest |
| Fragments | Usage frequency, contexts |
| Run-ons | Tendency, intentionality |
| Opening patterns | How sentences typically start |
| Closing patterns | How sentences typically end |
Paragraph Architecture
| Element | What to Track |
|---|---|
| Average length | Sentences per paragraph |
| Topic sentences | Beginning, middle, end, absent |
| Transitions | Explicit words, implicit flow, abrupt |
| Information order | Build-up, front-load, circular |
Punctuation Signature
| Mark | Track Usage Pattern |
|---|---|
| Em dash | Interruption, emphasis, list, asides |
| Parentheses | Frequency, content type |
| Semicolon | Presence, absence, alternative |
| Ellipsis | Trailing, pause, omission |
| Exclamation | Frequency, contexts |
| Rhetorical questions | Frequency, function |
Phase 3: Lexical Fingerprinting
Word Choice Matrix
| Category | Preferred | Avoided | Signature Examples |
|---|---|---|---|
| Technical terms | |||
| Colloquialisms | |||
| Intensifiers | very, extremely, quite... | ||
| Hedging | perhaps, might, seems... | ||
| Abstract/concrete |
Register Analysis
- Consistent register (formal/informal throughout)
- Deliberate register mixing (formal content, casual asides)
- Context-dependent shifting (formal for X, casual for Y)
Recurring Constructions
List phrases/patterns appearing 3+ times:
Phase 4: Conceptual DNA
Metaphor Mapping
| Source Domain | Target Domain | Example | Frequency |
|---|---|---|---|
| (war, journey, building...) | (ideas, processes...) |
Reference Pool
- Cultural touchstones: (movies, books, memes, history...)
- Time period: (contemporary, 90s, classic...)
- Accessibility level: (mainstream, niche, insider)
- Domains drawn from: (sports, cooking, science...)
Reasoning Patterns
Rate 1-5 for prevalence:
- Analogical reasoning (like X, therefore Y)
- First principles (from basics up)
- Empirical evidence (data, studies)
- Personal anecdote (I experienced...)
- Hypotheticals (imagine if...)
- Socratic questioning (but what if...?)
Phase 5: Emotional Texture
Enthusiasm Spectrum
| Low | Medium | High |
|---|---|---|
| (understated) | (balanced) | (expressive) |
Criticism Styles
| Style | When Used | Markers |
|---|---|---|
| Direct | "This is wrong because..." | |
| Diplomatic | "One consideration might be..." | |
| Humorous | "Well, that's one way to..." | |
| Analytical | "The issue breaks down to..." |
Vulnerability Patterns
- Admission phrases: "I'll admit...", "honestly..."
- Uncertainty markers: "I think...", "not sure but..."
- Personal revelation style: Direct? Buried in humor? Rare?
Phase 6: Reader Dynamics
Positioning
The writer positions as:
- Expert/teacher (I know, let me explain)
- Peer/collaborator (we're figuring this out together)
- Student/learner (I'm working through this)
- Challenger/provocateur (conventional wisdom is wrong)
- Guide/facilitator (here's how to navigate)
Assumed Context
- Shared knowledge level: Assumes expertise? Explains basics?
- Cultural assumptions: In-group references? Universal?
- Relationship warmth: Distant professional? Familiar?
Interactive Patterns
- Questions per 1000 words: ___
- Direct address frequency ("you"): ___
- Imperative usage (commands): ___
- Inclusive language ("we/us"): ___
Phase 7: Voice Guide Synthesis
Core Voice Statement
In 2-3 sentences, capture the essence:
The Rules That Matter Most
Always:
Never:
Usually, unless:
Sentence Construction Guide
- Preferred length:
- Variety pattern:
- Opening moves:
- Power positions: (where key info lands)
Word Selection Principles
- Go-to words for [concept]:
- Banned words/phrases:
- Register rules:
Structural Signatures
- Paragraph rhythm:
- Transition style:
- Information architecture:
Emotional Register
- Default tone:
- Excitement expression:
- Criticism approach:
- Vulnerability threshold:
The Litmus Test
A piece captures this voice when: 1. 2. 3.
Red Flags
Definitely NOT this voice when: 1. 2. 3.
Phase 8: Validation
Before finalizing the voice guide:
- Can identify the author in a blind test?
- Guided writing feels authentic, not performative?
- Patterns are descriptive, not prescriptive?
- Captures spirit, not just mechanics?
- Source would say "yes, that's me"?
Quick Reference Template
In Every Piece
The Heart of the Voice
[Single paragraph essence]
Emergency Voice Recovery
When writing has gone generic, add: 1. 2. 3.
Usage Notes
For AI Writing
Once the voice guide is complete, include relevant sections in the prompt to guide generation toward authentic voice reproduction.
Show full SKILL.md (452 more words)Show less
For Self-Analysis
Writers can use this framework to understand their own voice, identify what makes their writing distinctive, and consciously apply those patterns.
For Editing
Use the voice guide as a checklist when editing to ensure consistency and authenticity.
Anti-Patterns
1. Mechanics Over Spirit
Pattern: Cataloging every linguistic feature without understanding what makes the voice feel distinctive. Why it fails: A perfect inventory of word frequencies and sentence lengths can produce writing that's technically accurate but feels like a parody. Voice is gestalt, not components. Fix: Start from "what makes this voice feel like this?" Work backward to mechanics. The inventory serves understanding; understanding doesn't emerge from inventory alone.
2. Single-Context Capture
Pattern: Analyzing voice from one type of writing, then applying it to all contexts. Why it fails: Writers shift voice across contexts. Technical writing voice differs from casual email voice. Capturing one context and forcing it everywhere creates uncanny artifacts. Fix: Sample across contexts. Map how voice shifts. Include context-switching rules in the voice guide. Understand which elements are constant vs. context-dependent.
3. Frequency as Rule
Pattern: If they use em-dashes 8% of the time, the voice guide prescribes 8% em-dash usage. Why it fails: Frequency is a statistical average, not a style rule. Forced frequency creates awkward placement. Natural writers don't count punctuation. Fix: Understand when they use em-dashes, not how often. "Uses em-dashes for dramatic interjections, rarely for lists" is actionable. "8% em-dashes" is not.
4. Imitation Artifacts
Pattern: Voice-guided writing that feels like someone doing an impression—technically accurate but overperformed. Why it fails: Distinctive features become tics when isolated. Real voice balances distinctive and neutral. Guides that catalog only distinctive features produce caricature. Fix: Include neutral baseline alongside distinctive features. Most sentences should sound natural, with distinctive features emerging at appropriate moments, not constantly.
5. Frozen Voice
Pattern: Treating the voice guide as permanent, not updating as the writer evolves. Why it fails: Writers change. A voice guide from 2020 may not fit 2025 writing. Using outdated guides produces writing that feels like an old version of the person. Fix: Note the capture date. Plan periodic updates. Include the writer's own reflections on how their voice has evolved. Treat the guide as living documentation.
Integration
Inbound (feeds into this skill)
| Skill | What it provides |
|---|---|
| (writing samples) | Raw material for analysis |
| prose-style | Sentence-level craft framework for analysis |
Outbound (this skill enables)
| Skill | What this provides |
|---|---|
| prose-style | Voice-specific sentence construction guidance |
| dialogue | Voice patterns for character speech |
| (AI generation) | Voice guides for consistent AI-assisted writing |
Complementary
| Skill | Relationship |
|---|---|
| prose-style | Voice-analysis captures what; prose-style provides how. Use voice-analysis first to understand the target, then prose-style to achieve it |
| dialogue | Voice-analysis for authorial voice; dialogue skill for character voices within fiction |
© jwynia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/general/writing/analysis/voice-analysis of jwynia/agent-skills.
Open the folder on GitHubat commit e02ec7e
Compare with similar skills
Voice Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Voice Analysis this skilljwynia/agent-skills | 170 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| BrandOhh-889/skyroc | 795 | 13 repos | ~733 | Automated safety check: Pass | MIT | |
| Khazix WeChat Article WriterKKKKhazix/khazix-skills | 21k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Writing Guidelinesvercel-labs/agent-skills | 32k | 7 repos | ~309 | Automated safety check: Pass | None | |
| Unslop AI Writing Cleanuptheclaymethod/unslop | 518 | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Brand
Ohh-889/skyroc
Brand voice, visual identity, messaging frameworks, asset management, brand consistency.
Khazix WeChat Article Writer
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
- Official
Writing Guidelines
vercel-labs/agent-skills
Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.
Unslop AI Writing Cleanup
theclaymethod/unslop
Removes AI writing tells from prose through an audit-first flow, routing to a two-pass rewrite, a report-only cleanup, voice teaching or mimicry depending on the sub-command used.
UX Writing
content-designer/ux-writing-skill
Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.
More from jwynia/agent-skills
All 111 skills in this repoDevcontainer
jwynia/agent-skills
Diagnose devcontainer configuration problems and guide development environment setup.
Frontend Design
jwynia/agent-skills
Create distinctive, production-grade frontend interfaces with high design quality.
Gitea Workflow
jwynia/agent-skills
Orchestrate agile development workflows for Gitea repositories using the tea CLI.
Godot Asset Generator
jwynia/agent-skills
Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot.
Mastra Hono
jwynia/agent-skills
Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.
PPTX Generator
jwynia/agent-skills
Create and manipulate PowerPoint PPTX files programmatically.
Related
Categories
Questions about Voice Analysis
What does Voice Analysis do?
Extract and document a writer's distinctive voice patterns for consistent reproduction. Voice Analysis is an agent skill from jwynia/agent-skills. Extract and document a writer's distinctive voice patterns for consistent reproduction.
When should I use Voice Analysis?
Voice Analysis fits situations like: you need to capture writing voice; analyze writing style; create a voice guide; write in someones established style.
How do I install Voice Analysis in Claude Code?
Run `npx skills add jwynia/agent-skills --skill voice-analysis -a claude-code`. Or copy the skill folder (skills/general/writing/analysis/voice-analysis in jwynia/agent-skills) into .claude/skills/voice-analysis in your project. Claude Code loads it when a task matches its description.
How do I install Voice Analysis in Codex?
Run `npx skills add jwynia/agent-skills --skill voice-analysis -a codex`. Or copy the skill folder (skills/general/writing/analysis/voice-analysis in jwynia/agent-skills) into .agents/skills/voice-analysis in your project. Codex loads it when a task matches its description.
Can I use Voice Analysis in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jwynia/agent-skills --skill voice-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/voice-analysis, .gemini/skills/voice-analysis, .github/skills/voice-analysis and .opencode/skills/voice-analysis in your project.
What does Voice Analysis need to run?
SKILL.md names no scripts, command-line tools or credentials: Voice Analysis is instructions for the agent only.
Does Voice Analysis access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Voice Analysis safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Voice Analysis use?
Voice Analysis is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Voice Analysis use?
About 2.6k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Voice Analysis?
Skills that share tags, products or a category with Voice Analysis: Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Brand (Ohh-889/skyroc, 795 stars), Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars) and Writing Guidelines (vercel-labs/agent-skills, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Voice Analysis?
jwynia (a GitHub user) maintains it in jwynia/agent-skills, which has 170 GitHub stars. The repository holds 111 skills in this directory. The repository was last updated on February 24, 2026.
Source: jwynia/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.