voiceprint

A single unified prose-authenticity tool with one entry point. You give it text. It checks how authentically the text reads, rewrites the AI tells once, and tells you what is left. It is a thin orchestrator: it does not invent a method, it composes two existing skills in a fixed order, exactly once.

Where this comes from

voiceprint is the bundled product of two standalone, pure-prompt skills that each do one job well:

• humanizer rewrites AI-sounding prose so it reads as genuinely human, and in a specific writer's voice when a sample or profile is available.
• authenticity-check is a read-only diagnostic that scores how authentically text reads as a real human author and flags the spans that read as AI-generated, AI-templated, or derivative. It never rewrites.

Both descend from the voice-preservation logic that powers Scriveno (formerly Scriven), an AI-native longform writing system whose core promise is that drafted prose should sound like the writer, not like AI. The two skills were deliberately kept separate upstream, because a single tool that scores text and then rewrites it to raise its own score is a detector-gaming loop. voiceprint composes them without recreating that loop: it runs the diagnostic, the rewrite, and the diagnostic again, once each, with a human deciding what to do about anything left over.

The one-pass rule

This is the behavior the product exists to guarantee, and it does not relax:

1. Run the authenticity-check logic once on the input. This is the before read.
2. Apply humanizer's known fixes once. This produces the after text.
3. Run the authenticity-check logic again only to report the residual.

There is no iteration toward a score threshold. The re-check informs you; it never drives further rewriting. The output is the before text, the after text, the residual flagged spans, the authenticity read, and an explicit statement that what remains requires human judgment. A silent score-optimization loop is exactly what this design forbids. voiceprint is not an AI-detector-beating tool, and it names and targets no detector.

Why this one is different

• One pass, never a loop. The re-diagnosis is a report, not a feedback signal. There is no target score and no "try again until it passes."
• Thin orchestrator. It adds no method of its own. The behavior lives entirely in the vendored skills; this repo wires them together and gets out of the way.
• Canonical upstreams, one-directional sync. humanizer and authenticity-check stay independently usable and authoritative. voiceprint vendors copies and never edits them in place.
• Faithfulness inherited. humanizer's anti-fabrication guards and authenticity-check's restraint and caveats pass through unaltered, because voiceprint runs the vendored skills as written.

What it does

Given text, voiceprint returns one structured result: the original, the before authenticity read, the humanized rewrite with humanizer's own "what changed / deliberately left alone / meaning check" report, the residual read after the single pass, and a closing statement that the remaining gap is a human's call, not another automated rewrite.

Supported tools

Tool	File it reads	Install
Claude Code	SKILL.md	cp -r this repo to ~/.claude/skills/voiceprint/, or use the repo in-project
Cursor	.cursor/rules/voiceprint.mdc	Open this repo in Cursor, or copy .cursor/rules/voiceprint.mdc + SKILL.md + vendor/ into your project
Codex	AGENTS.md	Clone this repo into (or beside) your project; Codex reads AGENTS.md
Antigravity	AGENTS.md	Same as Codex: keep AGENTS.md + SKILL.md + vendor/ in the workspace
Gemini CLI	GEMINI.md	Keep GEMINI.md + SKILL.md + vendor/ in the project Gemini runs in
Pi Coder	AGENTS.md	Point Pi Coder at this repo / its AGENTS.md
OpenCode	AGENTS.md or SKILL.md	Copy the skill into OpenCode's skills directory, or keep AGENTS.md in the project
GitHub Copilot	.github/copilot-instructions.md	Copy .github/copilot-instructions.md + SKILL.md + vendor/ into the target repository

Every adapter points the agent at the same SKILL.md and the same vendored skills under vendor/, so the one-pass behavior is identical across tools.

voiceprint ships adapters for the eight tools above, the subset both upstream skills support in common. A vendored skill's own compatibility: frontmatter reflects its upstream's support and may list more (authenticity-check also names windsurf, cline, continue, zed, and aider, which voiceprint does not adapt); that frontmatter is upstream's, synced verbatim, and is not a claim that voiceprint provides an adapter for those tools.

Usage

Ask, in plain language, for the combined intent: clean this up and verify it, make this authentic and tell me how it scored, de-slop this and show me what is still flagged, or just "voiceprint this." You do not need to say the word "voiceprint."

If you only want one half, use the standalone skill directly:

• Only a rewrite, no score: use humanizer.
• Only a score, no rewrite: use authenticity-check.

For voice-matched output, the same options humanizer supports apply: paste a sample, name a well-known author, or keep a VOICE.md / STYLE-GUIDE.md in the project. The vendored skills discover it automatically.

Composition and the sync obligation

voiceprint is a thin orchestrator over vendored copies of both skills and the shared detection criteria. The vendored copies are not the source of truth. The sync is strictly one-directional.

• Canonical upstream for detection and rewrite criteria (tell-patterns.md, do-not-flag.md, voice-matching.md) is the humanizer repo.
• Canonical upstream for scoring logic (scoring.md) is the authenticity-check repo.
• voiceprint never edits vendored content. A fix belongs upstream in the canonical repo and is then re-vendored here. Editing a copy in place makes the product drift from the skills it claims to run.
• Every vendored file carries a header stamp recording its true upstream repo, the source commit, and a "synced copy, do not edit here, edit upstream" notice. The header is the contract.

Sync procedure

The vendored tree under vendor/ is produced and stamped entirely by the sync script. It is never hand-copied.

1. Land the criteria or logic change in the canonical upstream repo and commit it there (humanizer for detection/rewrite criteria, authenticity-check for scoring logic).

2. From this repo's root, run the sync tool:

   scripts/sync-upstream

   By default it reads the sibling repos ../humanizer and ../authenticity-check. Override with arguments or the HUMANIZER_REPO and AUTHENTICITY_CHECK_REPO environment variables:

   scripts/sync-upstream /path/to/humanizer /path/to/authenticity-check

3. The script refuses to run if either upstream working tree is dirty, so the stamped commit always reproduces the vendored bytes. It copies the runtime files into vendor/, prepends the sync header (naming the true canonical upstream per file: the shared criteria always point at humanizer even inside the authenticity-check tree), and prints a summary.

4. Verify and commit the updated vendor/:

   scripts/check-vendor-headers
   git add vendor && git commit

scripts/check-vendor-headers also runs in CI (.github/workflows/vendor-sync-check.yml) and fails the build if any file under vendor/ is missing a valid sync header. Re-syncing is an obligation, not an option: when the upstream criteria change, the vendored copies must be re-pulled or the product silently disagrees with the skills it advertises. A scheduled upstream-freshness workflow (and scripts/check-upstream-freshness) flags when an upstream has advanced past the vendored copy, so this obligation does not depend on remembering.

Scope

voiceprint improves prose quality and authentic voice, then gives an honest read of what is left. It is not designed or tuned to defeat plagiarism checkers or AI-detection systems, and it names no detector. Requests framed as passing AI work off as a person's own for a graded or contractual assessment are reframed toward the quality-and-voice use the tool actually serves. This is the same boundary the vendored skills hold; voiceprint inherits it.

Layout

SKILL.md                          orchestrator: the one-pass rule, output contract, scope
AGENTS.md                         cross-tool entry point (Codex, Antigravity, OpenCode, Pi Coder)
GEMINI.md                         Gemini CLI context
.cursor/rules/voiceprint.mdc      Cursor project rule
.github/copilot-instructions.md   GitHub Copilot instructions
.github/workflows/                CI: vendor-sync gate (headers, lint, evals) + weekly upstream-freshness check
vendor/humanizer/                 synced copy of the humanizer skill (canonical: humanizer)
vendor/authenticity-check/        synced copy of the authenticity-check skill
scripts/sync-upstream             re-pulls vendored files and stamps headers
scripts/check-vendor-headers      validates every vendored file has a valid header
scripts/check-upstream-freshness  flags when a vendored skill is behind its upstream
evals/evals.json                  verification cases asserting one-pass, no-loop behavior

License

MIT. See LICENSE. The vendored skills are MIT under the same copyright; their canonical sources are the humanizer and authenticity-check repos.