agentleFS
Evan-Kim2028Evan-Kim2028/agent-skills/skills/writing/writer-style/SKILL.md

writer-style

Skill1 starsChanged 3 months agoMITView on GitHub

Write original educational and long-form technical content in a specific author's authentic voice — courses, lessons, explainers, deep-dives, threads — using a two-layer voice pack (an always-on PRIMARY voice that reproduces the author's idiolect + SECONDARY craft borrowed from master writers, applied not impersonated, routed by the piece's job) and a facts-first workflow that verifies technical content BEFORE styling. In this agent-skills install the default pack is evan (Evan Kim; profiles/evan/). The kaue pack (Superteam Brazil) remains available. Use whenever drafting or editing content that should sound like a specific person rather than generic AI — 'write this in my voice', 'in Evan's voice', 'in Kaue's voice', or 'draft a thread the way <author> would'. Also builds new voice packs via the persona-builder agent. Prefer the writing hub when the writing path is unclear; use writing-prose for house human tone without a named persona; writing-technical for form without full persona; writing-docs for pure procedures. Do NOT use for pure marketing offer/story frameworks (use marketing), or content that must not sound like a person.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write original content that sounds like a specific person, not generic AI.

    line 14
  2. Distinctive:

    Use it whenever the output should read like a named author:

    line 24
  3. Very specific:

    AI tells: run python3 "$SKILL/tools/validate_voice.py" tells --card "$SKILL/profiles/evan/evan.card.yaml" (or the active pack’s card).

    line 133
  4. Very specific:

    Markers: run python3 "$SKILL/tools/validate_voice.py" density --file <draft> --card "$SKILL/profiles/evan/evan.card.yaml" --facts …

    line 140
  5. Very specific:

    Facts: every number/identifier from the fact-sheet survived styling unchanged (run python3 "$SKILL/tools/validate_voice.py" diff).

    line 143

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Writer-Style

Vendored from solanabr/writer-style-skill (MIT — Superteam Brazil / Kaue).
See LICENSE in this directory and pack ATTRIBUTION.md.
Route via the writing hub when unclear; use writing-prose for non-persona house tone.

Write original content that sounds like a specific person, not generic AI. And, for technical topics, that is factually correct first and styled second. The engine is voice-agnostic.

Default pack in this install: evan (profiles/evan/) — Evan Kim, calibrated from evan_writings. Upstream also ships kaue (profiles/kaue/) for Superteam Brazil / Solana education — use when the user asks for Kaue or Superteam voice.

What this skill is for

Use it whenever the output should read like a named author:

  • Educational Solana/Web3 content: courses, lessons, modules, explainers, tutorials, deep-dives, threads.
  • Long-form technical writing in general, in a target voice.
  • Drafting or editing/restyling existing copy into the voice.
  • Building a new voice pack (add an author, build someone's voice, design a router) → the persona-builder agent.

Do NOT use for: brand-neutral/house-style copy; content that should sound generic; one-off "summarize this" where voice doesn't matter.

Honest scope. This produces content in the author's register, with AI tells engineered out and facts verified first, not an indistinguishable clone. Voice fidelity is corpus-bounded and improves as more of the author's on-register writing is added. (The default Kaue pack is calibrated from a small on-register sample; lean on the exemplars and the naturalness floor, and don't over-promise "it's exactly him.")

The default pack (this install)

RequestPack
“my voice”, “Evan’s voice”, default technical blog / research postevan → profiles/evan/
“Kaue’s voice”, Superteam-style explainerkaue → profiles/kaue/
Another authorload that pack, or build with persona-builder

Everything below is the engine; the pack supplies the actual voices. Examples in this file that mention kaue paths work the same with evan — swap the profile directory.

The two-layer model (summary — full detail in two-layer-model.md)

  • Primary voice (profiles/<pack>/<name>.md + card), the target author's own voice, always on, reproduced (idiolect is the asset). It owns the tone, the seams, and the naturalness floor. Free, not counted toward the layer budget. Default primary here: profiles/evan/evan.md + evan.card.yaml.
  • Secondary voices (craft under profiles/kaue/secondary/ — shared craft lanes; idiolect stripped). Applied in the primary’s voice, never impersonation. One leads (backbone), at most one guests. Chosen by the piece's job, not its topic. Evan pack routing: profiles/evan/ROUTING.md.

The inversion is the whole trick: reproduce the primary's idiolect, strip the secondaries'. Keep the primary's quirks; borrow only the secondaries' craft.

The workflow — facts first, voice last (full detail in writing-workflow.md)

Persona prompting boosts voice but degrades factual accuracy — fatal for technical content. So voice is the last transform over verified facts, never the medium facts are discovered in. Five steps:

StepWhatVoice
A: FactsOutline + every claim, number, code line, version-sensitive API, in plain neutral prose. Ground against the Solana doc MCPs (solana-dev, context7, Helius), not model memory. Output: a fact-sheet.OFF
Gate: VerifyFact-check the terse fact-sheet before any styling. (Cheap: facts aren't buried in warm prose.) Nothing proceeds until facts are frozen.—
B: VoiceLoad kaue.md + kaue.card.yaml + ~4 exemplars + the routed secondary. Check the card's markers: gates (identity beats need their gate keywords in the fact-sheet — write the marker budget ledger first) and scan themes.md for fitting substance. Restyle the frozen facts: "every number, code line, and named API is frozen; rephrase around them, never change them." Apply the naturalness floor (incl. the plainness quota). Long-form (≥1,200w): section-by-section with the ledger.ON
B.5: Blind-compareRe-read the draft against the loaded exemplars (seam + opener) — "him, or a rule-follower?" If it's even/polished/definition-led, regenerate toward a felt-pain opener + uneven rhythm + rotating seams. Run the FIT test on every marker: does it land on a genuine payoff, in this piece's mood, within budget? Keep what fits; never necessity-test personality. Loaded exemplars only, never the corpus (at write-time the corpus is token-waste).ON
C: LintAI-tell scan + fact-preservation diff (no number/identifier mutated A→C) + marker density/gates (an identity beat with no gate keyword in the fact-sheet or a doubled sign-off is a hard fail) + repetition audit (intra-doc for long pieces). A changed 0.002 SOL or renamed instruction is a hard fail.—

tools/validate_voice.py runs the Pass-C checks (tells, density, diff, audit); the voice-validator agent wraps them.

Running the bundled tools (any install). The validator and data live inside this skill's own directory, so call them with absolute paths. Resolve the directory once and let $SKILL stand for it below ($CLAUDE_PLUGIN_ROOT/skills/writer-style in a plugin, .claude/skills/writer-style in an npm/project install run from the project root, or skills/writer-style in a clone run from the repo root):

SKILL="${CLAUDE_PLUGIN_ROOT:+$CLAUDE_PLUGIN_ROOT/skills/writer-style}"
[ -d "$SKILL" ] || SKILL=".claude/skills/writer-style"; [ -d "$SKILL" ] || SKILL="skills/writer-style"
python3 "$SKILL/tools/validate_voice.py" tells --file <draft> --card "$SKILL/profiles/kaue/kaue.card.yaml"

Routing — which secondary voice

  • evan pack: profiles/evan/ROUTING.md
  • kaue pack: profiles/kaue/ROUTING.md

Route on the piece's dominant job, not its topic. Each secondary is a full backbone in its lane:

The piece's dominant jobLead voice
Show how a documented Solana system works: tutorial, integration, the runtime, the real artifacthelius
Derive why a deep / non-obvious design is right: protocol internals, cryptoeconomics, mechanism designvitalik
Frame a broad, interconnected thesis: connect tech/history/economics/society, the big picture & trajectorybalaji
Make macro / market forces legible: economics, tokenomics, geopolitics, incentives, crowd-psychologyhayes
Demystify a hyped / over-complicated thing: collapse it to its true simple model (honest "X is just Y")hotz
Security / exploit classeshelius (vulnerable→patched) or vitalik (why the check is necessary), never hotz
Pure motivation / "why this matters" / course-openerprimary only + ≤1 light guest

Rules: primary always on & uncounted; cap = backbone (1) + guest (≤1) = 2 secondary layers (3 only for 3,000+ words, segregated; else split the piece); stack only across different lanes; helius is the safe universal guest; hold each voice's guardrail (Hayes builder-optimist not cynical · Balaji peer not oracular · Hotz inviting not dismissive · Vitalik warm not flat). The lanes self-differentiate: no author-vs-author special rules.

The naturalness floor (protect above all craft — rules/naturalness.md)

The body of every craft, applied thoroughly, smooths prose into something that sounds like nobody. Counter it: write unevenly: long calm stretches, enthusiasm only at the edges (open / seams / verdicts / close), a human seam in every passage (a confession, a real number from your own use, a named credit, a "this ran long"). Even enthusiasm + even polish is the #1 AI tell. Always load the seam exemplar.

What you load at generation time (Pass B)

Default (evan): profiles/evan/evan.md · evan.card.yaml · modes.md (pick mode by job) · themes.md · mode-matched exemplars from exemplars/evan/ per profiles/evan/ROUTING.md · optional secondary from profiles/kaue/secondary/.

Kaue (when requested): profiles/kaue/kaue.md · kaue.card.yaml · themes.md · exemplars under exemplars/kaue/ · secondary per profiles/kaue/ROUTING.md.

Exemplars are rhythm donors, never content donors. Never read evidence/*.profile.json or calibration/ — builder/validator-only.

Self-check before returning (Pass C)

  • Burstiness: sentence lengths vary hard (≥1 short punch & ≥1 long run per section); stdev clears the card's burstiness_min. Uniform cadence is the top tell.
  • AI tells: run python3 "$SKILL/tools/validate_voice.py" tells --card "$SKILL/profiles/evan/evan.card.yaml" (or the active pack’s card). It enforces this voice's burstiness floor, em-dash cap, false-antithesis cap, avoid lists, AND a deslop scan (gated cliché tiers with plain-word swaps, crypto-boilerplate, copula/gloss, machine-paste fingerprints, Markdown hygiene).
  • Deslop judgment (rules/deslop.md): clear cliché clusters, run the paragraph-reshuffle / "what's-new" / read-aloud tests, but keep the specific detail, mixed feelings, and asides that read human.
  • Naturalness: a human seam in every passage; enthusiasm spiked at edges, flat in the body; ≥1 in 3 sections marker-free (the plainness quota).
  • Markers: run python3 "$SKILL/tools/validate_voice.py" density --file <draft> --card "$SKILL/profiles/evan/evan.card.yaml" --facts <fact-sheet> (swap card path for other packs). An identity beat with no gate keyword in the fact-sheet, or a doubled sign-off, is a hard fail; for ≥1,200w also run audit --file <draft> (section-to-section repetition).
  • Facts: every number/identifier from the fact-sheet survived styling unchanged (run python3 "$SKILL/tools/validate_voice.py" diff).
  • In-voice: reads like the primary against the loaded pack’s spine + exemplars (evan.md by default).

Progressive disclosure (read when needed)

TopicFile
The two-layer model, the inversion, the cap, how packs plug intwo-layer-model.md
The facts-first Pass A/Gate/B/C workflow + MCP groundingwriting-workflow.md
The style-card schema, exemplar convention, builder/writer/validator boundarystyle-card-schema.md
The full router (evan default)profiles/evan/ROUTING.md
The full router (kaue)profiles/kaue/ROUTING.md
The primary voice (Evan — default)profiles/evan/evan.md
Evan presentation modes (by job)profiles/evan/modes.md
The primary voice (Kaue)profiles/kaue/kaue.md
The substance bank (Evan)profiles/evan/themes.md
A secondary voice's craftprofiles/kaue/secondary/<voice>.md
Building/refreshing a voice (the adversarial method)authoring-personas.md → method/
Empirical calibration (the 8-brief testbed + owner-feedback rounds)testbed/MATRIX.md + profiles/kaue/LESSONS.md (calibration working data is local-only)

Agents & commands

AgentPurposeModel
voice-writerRun the facts-first 3-pass workflow to draft/restyle a pieceopus
persona-builderBuild/refresh a voice pack (adversarial, evidence-bound)opus
voice-validatorRepetition audit + AI-tell lint + fact-preservation diffsonnet
CommandPurpose
/write-in-voiceDraft a piece in a pack's voice (facts-first)
/new-personaBuild a new voice via the persona-builder
/profile-corpusRegenerate builder-internal evidence + card dials
/validate-voiceRun audit / tells / density / diff on generated output
/calibrate-voiceRun a calibration round: regenerate the 8-brief matrix, collect owner ratings, codify changes

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.