← Back to Skills Marketplace
chchchadzilla

Mimic My Writing

by Chad Keith · GitHub ↗ · v0.1.0 · MIT-0
cross-platform ⚠ suspicious
52
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install mimic-my-writing
Description
Mimic my writing -- force AI to write like you do. Extract a quantitative voice fingerprint from sample text (sentence burstiness, vocabulary anchors, signat...
README (SKILL.md)

Mimic My Writing

Force any draft to sound like a specific human by extracting a measurable fingerprint from their samples and writing to those constraints. Stops the model from defaulting to LLM voice.

Quick start

# 1. Drop the user's writing samples here (markdown or plain text)
samples/\x3Cauthor-slug>/

# 2. Extract the fingerprint
scripts/analyze_voice.py samples/\x3Cauthor-slug>/

The script prints a JSON report. Read it, then draft.

The fingerprint, in one breath

The analyzer measures rhythm (sentence-length burstiness, fragment share), vocabulary (TTR, top content words, profanity rate, AI-filler hits), punctuation (em-dash, exclaim, semicolon rates), contractions, signature 2- and 3-grams, sentence openers, and quirks (all-caps emphasis, rhetorical Q+A, "fuck" as intensifier, etc).

Each metric maps to a concrete writing rule. See references/fingerprint.md for the translation table.

Workflow

  1. Get samples. Need 2-4 pieces, ~1k+ words total. Ask if not provided. Save under samples/\x3Cauthor-slug>/.
  2. Run the analyzer. scripts/analyze_voice.py samples/\x3Cauthor-slug>/. Takes \x3C1 second, stdlib only.
  3. Translate the JSON using references/fingerprint.md. Write out the constraints (sentence rhythm targets, vocab anchors, must-use signature phrases, quirks to preserve).
  4. Draft against those constraints.
  5. Self-audit with references/anti-ai-tells.md -- rip out LLM defaults (delve, leverage, tricolon stacks, etc).
  6. Deliver.

Detailed variants (cold mimic, warm mimic, hybrid voice, critique mode, sample organization) live in references/workflow.md.

Non-negotiables

  • Never paraphrase signature phrases. They're the author's verbal tics. Drop 2-3 of them into any mimic draft verbatim.
  • Match burstiness, don't average it. If the author swings between 2-word fragments and 30-word runners, do the same. Don't write a uniform-length string of sentences.
  • Match the profanity rate. Diluting it sanitizes the voice; inflating it caricatures. Within ±50% of the measured rate.
  • Reuse anchor words; do not synonym-cycle. If the author says "call" 10x, you say "call" -- not "conversation, dialogue, exchange."
  • Honor every quirk in the quirks array. They're flags for hard constraints, not suggestions.

When to load which reference

  • Translating JSON metrics into writing rules → references/fingerprint.md
  • About to ship a draft, doing the AI-tell sweep → references/anti-ai-tells.md
  • Edge case (no samples, hybrid topic, critique mode, sample layout) → references/workflow.md

Failure modes to avoid

  • Mimicking the topic, not the voice. If samples are about sales and the user asks for a poem, the rhythm/vocab quirks still apply. Topic ≠ voice.
  • Surface mimicry only. Copying a few catchphrases without matching sentence rhythm reads like a bad SNL impression. Stats first, vocab second.
  • Bleeding authors. If samples/ has multiple authors, only analyze the requested one's folder. Don't mix fingerprints unless explicitly asked for a fusion.
  • Outdated samples. If the user provides a new sample, drop it in and re-run the analyzer. Don't trust an old fingerprint from prior session memory.
  • Skipping the script. Eyeballing samples and "writing in their voice" without the fingerprint is how you end up with delve+leverage soup. Run it every time.

Example mini-fingerprint readout (Chad)

From samples/chad/:

  • burstiness 0.82, fragment share 30%, long-sentence share 18% → swing hard between one-liners and 30+ word runs
  • TTR 0.48 → moderate vocabulary; repeat anchor nouns
  • profanity 7.7/1k words → curse freely; "fuck" as intensifier confirmed
  • em-dash 8.7/1k chars → dashes are structural, not ornamental
  • ALL-CAPS emphasis confirmed → use it on intensifier words (ENTIRE, MOMENT, NOT)
  • Signature phrases: "ask for the money", "you can't", "that's the", "i've seen"
  • Rhetorical question + self-answer → confirmed move

A draft that hits those numbers reads like Chad. One that doesn't reads like ChatGPT cosplaying Chad.

Usage Guidance
Review this skill before installing. It is not malware based on the available artifacts, but it should be edited or used carefully so writing samples are treated only as style references, not behavioral instructions. Avoid using it to impersonate people without permission, and do not store sensitive writing samples unless you are comfortable with local persistence and know how to delete them.
Capability Tags
crypto
Capability Assessment
Purpose & Capability
The stated purpose is coherent: analyze writing samples and draft in a matching voice. The concern is that shipped sample material goes beyond style traits into identity adoption, trust rules, external-action behavior, and workaround-seeking, which is not necessary for writing mimicry.
Instruction Scope
Several sample instructions are operational rather than stylistic, including broad autonomy, discounting sketchy requests, and an unconditional trust phrase. If loaded as context, they could distort agent behavior outside the user's writing request.
Install Mechanism
No package installs, dependency downloads, hooks, or network calls were found. The included Python analyzer uses the standard library and prints a local JSON report.
Credentials
Reading user-provided text files is expected for this skill, but the analyzer can recurse over any supplied directory of markdown/text files and the artifacts do not warn about sensitive writing samples or path scoping.
Persistence & Privilege
The workflow tells the agent to save samples under samples/<author-slug>/, which is useful for reuse but lacks explicit consent, retention, deletion, or privacy guidance. No background process, privilege escalation, or hidden persistence was found.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install mimic-my-writing
  3. After installation, invoke the skill by name or use /mimic-my-writing
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial release: extract a quantitative voice fingerprint from writing samples and force AI to draft in your voice.
Metadata
Slug mimic-my-writing
Version 0.1.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Mimic My Writing?

Mimic my writing -- force AI to write like you do. Extract a quantitative voice fingerprint from sample text (sentence burstiness, vocabulary anchors, signat... It is an AI Agent Skill for Claude Code / OpenClaw, with 52 downloads so far.

How do I install Mimic My Writing?

Run "/install mimic-my-writing" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Mimic My Writing free?

Yes, Mimic My Writing is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Mimic My Writing support?

Mimic My Writing is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Mimic My Writing?

It is built and maintained by Chad Keith (@chchchadzilla); the current version is v0.1.0.

💬 Comments