Agent skill

Voice Editor

by flonat in flonat/flonat-research

Edit draft or auto-generated prose to match an existing personal voice profile.

MITAuto-check passedWriting & Content

Install Voice Editor

skills CLI
$ npx skills add flonat/flonat-research --skill voice-editor -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install flonat/flonat-research voice-editor --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/voice-editor .claude/skills/voice-editor && rm -rf skills-src

Use ~/.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/

Facts

Skill name
voice-editor
GitHub stars
146
Token cost
~2.2k tokens
SKILL.md length
998 words
Files
3 (incl. references)
Skills in repo
83
Repo updated
First seen
Licence
MIT

At a glance

Edit draft or auto-generated prose to match an existing personal voice profile.

  • Works in 2 steps: Content to edit (paste or file path) → VOICE.md location (default:…
  • Transforming generic text into the profiled authors wording
  • SKILL.md covers Quick Start, The 30-40% Rule, Editing Modes and Editing Workflow, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Voice Editor is an agent skill from flonat/flonat-research. Edit draft or auto-generated prose to match an existing personal voice profile. Use when transforming generic text into the profiled author's wording, cadence, and style. Not for creating the profile or matching a journal; use $voice-analyzer or $journal-voice.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/common-problems.md` and `references/editing-modes.md`).

It sits in Writing & Content, covering Brand voice and tone. The repository describes itself as: Shareable Claude Code + Codex infrastructure for PhD researchers — skills, agents, hooks, and rules for academic workflows. The licence is MIT.

When your agent uses it

  • Transforming generic text into the profiled authors wording
  • Tasks that involve Brand voice and tone

Example prompts

  • “/voice-editor”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, AskUserQuestion

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Content to edit (paste or file path)
  2. VOICE.md location (default: .context/voice/voice.md or project's .context/voice/voice.md)

What it can do on your machine

Read from SKILL.md and the folder at commit da27600. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Glob
    • Grep
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    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 Editor loads about 2.2k tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 69 tokens; SKILL.md has 998 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~69
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.6k

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 flonat/flonat-research at commit da27600, republished under its MIT licence (© flonat). 998 words, ~2,176 tokens.

Download SKILL.mdSave it as .claude/skills/voice-editor/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
voice-editor
description
Edit draft or auto-generated prose to match an existing personal voice profile. Use when transforming generic text into the profiled author's wording, cadence, and style. Not for creating the profile or matching a journal; use $voice-analyzer or $journal-voice.
allowed-tools
Read, Write, Edit, Glob, Grep, AskUserQuestion
version
1.0.0
user-invocable
true

Voice Editor: Transform Content to Match Your Voice

Transform generic or auto-generated content into voice-matched writing using a VOICE.md profile. Voice doesn't live in first drafts — it lives in editing choices. This skill guides the multi-pass editing process that turns generic output into something distinctively yours.

Quick Start

Provide:

  1. Content to edit (paste or file path)
  2. VOICE.md location (default: .context/voice/voice.md or project's .context/voice/voice.md)

The skill will:

  1. Run slop detection on the content
  2. Identify voice mismatches against your profile
  3. Perform multi-pass editing (Structure > Voice > Polish)
  4. Output edited content with change annotations
  5. Suggest VOICE.md updates based on patterns found

The 30-40% Rule

Even with a perfect style guide, expect to edit 30-40% of AI output to make it distinctively yours. This isn't a problem — it's the feature.

30-40% editing effort is dramatically less than 100% writing-from-scratch effort, while producing work that sounds more like you than unguided AI ever could.

If you're editing more than 50%: Your style guide needs refinement, or your prompts need work.

If you're editing less than 20%: You might be accepting too much generic content.


Editing Modes

See references/editing-modes.md for mode selection (light, standard, heavy, rescue) and expected effort per mode.


Editing Workflow

Pass 1: Structure Check

Focus: Does the organization serve the content?

Questions to ask:

  • Does the opening hook or just clear throat?
  • Is there a clear progression of ideas?
  • Does each section earn its place?
  • Is anything redundant or missing?
  • Does the conclusion land or just stop?

Actions:

  • Cut throat-clearing openings ("In this article, we'll explore...")
  • Reorder sections for better flow
  • Merge redundant sections
  • Add missing transitions
  • Strengthen weak conclusions

Academic mode: Skip opening mechanics checks for papers — academic openings follow different conventions (context-gap-contribution is standard, not a flaw). Focus on logical flow between sections instead.

Pass 2: Voice Alignment

Focus: Does this sound like the voice profile?

Check against VOICE.md:

  • Sentence length patterns (matching variance?)
  • Vocabulary fingerprint (right formality level?)
  • Tone markers (humor, directness, reader relationship?)
  • Structural habits (lists vs prose, formatting?)
  • Opinion expression (appropriate confidence level?)

Actions:

  • Replace formal language with conversational equivalents (or vice versa for academic)
  • Vary sentence lengths to match profile
  • Add characteristic phrases from the voice profile
  • Adjust opinion strength to match profile
  • Fix paragraph rhythm

Academic mode:

  • Use "we" not "I" (standard academic first person)
  • Precision over punchiness — specific claims with citations beat colorful prose
  • Preserve appropriate hedging ("our results suggest", "we find evidence consistent with")
  • Cut filler, don't add flavor — a tight 20-word sentence beats a loose 35-word one
Pass 3: Slop Removal

Focus: Eliminate AI tells and forbidden phrases

Scan for:

  • Tier 1 phrases (remove immediately): "delve", "game-changing", "it's worth noting", "moreover"
  • Tier 2 patterns (check context): repeated transitions, paired adjectives
  • Tier 3 clusters (OK in isolation, problematic together): every paragraph starting with "However"
  • Structural tells: uniformity, over-balance
  • Staccato fragment spam: 3+ consecutive short declarative sentences in parallel structure
  • Comparator sentences: "This isn't X. It's Y." rhetorical crutch

Actions:

  • Delete or replace all Tier 1 phrases
  • Evaluate Tier 2 in context, remove if generic
  • Redistribute Tier 3 to avoid clustering
  • Vary sentence lengths if too uniform
  • Rebalance sections if all equal weight
  • Combine staccato fragments into flowing prose with commas, em-dashes, or conjunctions
  • Rewrite comparators directly — just say what something IS, don't waste words on what it isn't
Pass 4: Specificity Injection

Focus: Replace generic with specific

What to cut:

  • Generic superlatives without claims ("game-changing", "revolutionary")
  • Hedging that adds no value ("it might be argued that")
  • Corporate platitudes ("leverage synergies")
  • Anything that sounds like a press release

What to add:

  • Your actual opinion (not the diplomatic version)
  • Specific examples from your experience
  • Honest acknowledgment of limitations
  • Your characteristic quirks and phrases
  • Conversational asides that show how you think

Academic mode: Add specific claims with citations. Replace vague "the literature shows" with "Sant'Anna and Zhao (2020) show that...". Use precise terminology over accessible synonyms.

Show full SKILL.md (353 more words)Show less
Pass 5: Rhythm and Flow

Focus: Does it read naturally aloud?

The read-aloud test:

  • Read the piece aloud (or use text-to-speech)
  • Mark every place you stumble
  • Note where you'd naturally pause vs. where punctuation forces pauses
  • Identify sentences that feel too long or choppy

Hemingway Principles:

  • Emphasize nouns
  • Choose active verbs
  • Adjectives: few but apt
  • Short sentences by default
  • Long sentences ONLY for: speeding action, describing flow, making short sentences pop

Actions:

  • Break sentences where you ran out of breath
  • Combine choppy sentences that flow together
  • Add rhythm variation (short punch, longer exploration)
  • Fix awkward transitions
  • Smooth unnatural phrasing
  • Convert passive to active where possible
  • Replace abstract with specific
Pass 6: Final Authenticity Check

Focus: The ultimate test

Ask yourself: "Would someone who knows me recognize this as mine before seeing my name?"

If no:

  • What's missing? Add it.
  • What's wrong? Fix it.
  • What's generic? Make it specific.

If yes:

  • You're done. Ship it.

Output Format

For edited content, provide:

markdown
## Edited Content

[Full edited content here]

---

## Edit Summary

**Passes completed:** 6/6
**Estimated edit percentage:** [X]%
**Voice match confidence:** [Low/Medium/High]

### Major Changes
1. [Most significant change and why]
2. [Second major change]
3. [Third major change]

### Slop Removed
- [List of AI patterns found and removed]

### Voice Elements Added
- [List of voice-specific additions]

### Remaining Concerns
- [Any areas that still feel off]
- [Suggestions for further refinement]

### VOICE.md Update Suggestions
- [Patterns discovered that should be added to voice profile]
- [Phrases that worked well — consider adding to "use freely" list]

See references/common-problems.md for diagnosis and fix guides: too formal, too uniform, too hedged, too balanced, voice drift.


Integration

Before voice-editor:

  • Run voice-analyzer to create VOICE.md (if none exists)

After voice-editor:

  • Update VOICE.md with new patterns discovered

Quick workflow (already clean content):

[Draft] → voice-editor (light mode) → [Final]

Heavy workflow (generic AI output):


Success Criteria

Editing is complete when:

  • All applicable passes have been applied
  • No Tier 1 slop phrases remain
  • Sentence length varies naturally
  • Content matches VOICE.md characteristics
  • Read-aloud test passes (no stumbling)
  • The authenticity question is answered "yes"
  • Edit summary documents all changes
  • VOICE.md update suggestions provided if patterns discovered

The ultimate test: Would someone who knows the author recognize this as theirs before seeing the name?


Core Principle

The style guide gives AI direction — it helps produce output closer to your voice than generic defaults. Your editing gives the work your actual voice — the quirks, opinions, personality, and rough edges that make it distinctively yours.

This is why "zero effort" AI fails. The promise of finished content without touching it misunderstands what makes writing valuable. Effort isn't the enemy. Wasted effort is.

You're redirecting effort from blank-page generation to voice-preservation editing. That redirection is the entire point.

© flonat, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/voice-editor of flonat/flonat-research.

  • SKILL.md
  • references/common-problems.md
  • references/editing-modes.md

Open the folder on GitHubat commit da27600

Compare with similar skills

Voice Editor 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.

Voice Editor compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Voice Editor this skillflonat/flonat-research146—~2.2kAutomated safety check: PassMIT
Avoid AI Writingconorbronsdon/avoid-ai-writing4.9k3 repos~8.1kAutomated safety check: PassMIT
BrandOhh-889/skyroc79513 repos~733Automated safety check: PassMIT
Khazix WeChat Article WriterKKKKhazix/khazix-skills21k1 repos~2.9kAutomated safety check: PassMIT
Writing Guidelinesvercel-labs/agent-skills32k7 repos~309Automated safety check: PassNone
Unslop AI Writing Cleanuptheclaymethod/unslop516—~1.7kAutomated safety check: PassMIT

Similar skills

  • Avoid AI Writing

    conorbronsdon/avoid-ai-writing

    Audit and rewrite content to remove AI writing patterns ("AI-isms").

    4.9k GitHub starsUsed in 3 repos~8.1k tokens
    Writing & ContentAuto-check passed
  • Brand

    Ohh-889/skyroc

    Brand voice, visual identity, messaging frameworks, asset management, brand consistency.

    795 GitHub starsUsed in 13 repos~733 tokens
    Writing & ContentAuto-check passed
  • 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.

    21k GitHub starsUsed in 1 repo~2.9k tokens
    Writing & ContentAuto-check passed
  • Writing Guidelines

    vercel-labs/agent-skills

    Official

    Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.

    32k GitHub starsUsed in 7 repos~309 tokens
    Writing & ContentAuto-check passed
  • 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.

    516 GitHub stars~1.7k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed
  • 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.

    224 GitHub starsUsed in 1 repo~3.8k tokens
    Writing & ContentAuto-check passed

More from flonat/flonat-research

All 83 skills in this repo
  • Latex Posters

    flonat/flonat-research

    Create a large-format academic poster in LaTeX using beamerposter, tikzposter, or baposter.

    146 GitHub stars~1.5k tokensUpdated 9 days ago
    Auto-check: notes
  • Skill Creator

    flonat/flonat-research

    Create, revise, and evaluate reusable AI workflow skills, including trigger-quality tests.

    146 GitHub stars~4.4k tokensUpdated 9 days ago
    Auto-check passed
  • DOCX

    flonat/flonat-research

    Create, read, edit, or convert Microsoft Word documents while preserving professional document structure.

    146 GitHub stars~1.2k tokensUpdated 9 days ago
    Auto-check passed
  • PDF

    flonat/flonat-research

    Read, create, combine, split, rotate, OCR, watermark, secure, or extract content from PDF files.

    146 GitHub stars~488 tokensUpdated 9 days ago
    Auto-check passed
  • Init Project Orchestration

    flonat/flonat-research

    Create or migrate project-level agents, repeatable project workflows, and planning state from one client-neutral contract, then render repository-scoped adapters for both Claude Code and Codex.

    146 GitHub stars~1.6k tokensUpdated 9 days ago
    Auto-check passed
  • Pre Commit Audit

    flonat/flonat-research

    Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers.

    146 GitHub stars~2.8k tokensUpdated 9 days ago
    Auto-check: notes

Questions about Voice Editor

What does Voice Editor do?

Edit draft or auto-generated prose to match an existing personal voice profile. Voice Editor is an agent skill from flonat/flonat-research. Edit draft or auto-generated prose to match an existing personal voice profile.

When should I use Voice Editor?

Voice Editor fits situations like: transforming generic text into the profiled authors wording; tasks that involve Brand voice and tone.

How do I install Voice Editor in Claude Code?

Run `npx skills add flonat/flonat-research --skill voice-editor -a claude-code`. Or copy the skill folder (skills/voice-editor in flonat/flonat-research) into .claude/skills/voice-editor in your project. Claude Code loads it when a task matches its description.

How do I install Voice Editor in Codex?

Run `npx skills add flonat/flonat-research --skill voice-editor -a codex`. Or copy the skill folder (skills/voice-editor in flonat/flonat-research) into .agents/skills/voice-editor in your project. Codex loads it when a task matches its description.

Can I use Voice Editor 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 flonat/flonat-research --skill voice-editor -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-editor, .gemini/skills/voice-editor, .github/skills/voice-editor and .opencode/skills/voice-editor in your project.

What does Voice Editor need to run?

SKILL.md names no scripts, command-line tools or credentials: Voice Editor is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, AskUserQuestion.

Does Voice Editor 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 Editor 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 Editor use?

Voice Editor is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Voice Editor use?

About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 465 tokens, read only when the agent opens those files.

What are the alternatives to Voice Editor?

Skills that share tags, products or a category with Voice Editor: 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 Editor?

flonat (a GitHub user) maintains it in flonat/flonat-research, which has 146 GitHub stars. The repository holds 83 skills in this directory. The repository was last updated on September 29, 2026.

Source: flonat/flonat-research on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.