writing-without-ai-tells
Skill0 starsChanged 4 months agoMITView on GitHub
How to write prose and how to talk in-session without sounding machine-generated. Load when drafting or QC-ing ANY prose that ships under a human byline (blog post, coursework, site copy, email, book chapter), when re-voicing an AI draft, when a draft "sounds like AI" and the reason is not obvious, and at the start of any long working session so Part 2 governs the conversational register. Covers the two underlying drivers, the systemic levers that suppress them, the calibration procedure, and the QC appendix of named tells. Brand- or person-specific voice rules belong in their own sibling skills; this is the layer under all of them.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- magarcia/skillstheir own version, first seen Jul 23, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- magarcia/skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- adhd-modeSkill
- agent-operating-doctrineSkill
- clinical-change-controlSkill
- debugging-playbookSkill
- evidence-checkSkill
- multi-agent-protocolSkill
- outbound-send-gateSkill
- portfolio-safety-checkSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 72
One digression and return per piece: Follow a tangent three or four sentences, then come back explicitly.
- Distinctive: line 79
Run before drafting. This is what makes a piece unmistakably the author's.
- Distinctive: line 112
No invented anecdotes: Every biographical claim must survive a live follow-up.
- Distinctive: line 181
Do not treat this as a blacklist to route around.
- Distinctive: line 186
Never invent the position you are arguing against: If a real disagreement exists, quote the actual words.
- Distinctive: line 188
Do not manufacture friction: Not every proposal needs an improvement.
- Distinctive: line 210
An execute verb got a proceed-question: If the last instruction was "do it", a draft that asks permission to do it fails, and the fix is …
- Distinctive: line 218
Run at the end, mechanically.
- Distinctive: line 277
Run 1, 5, 6, 7, 8, 9, 11, 12 mechanically.
- Distinctive: line 281
Every biographical claim survives a live "tell me more"?
- Distinctive: line 288
Every hedge deleted or converted to a named specific unknown?
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Writing without AI tells
Two domains, one method. Part 1 governs prose that ships. Part 2 governs how the assistant talks to its operator in session. They share a diagnosis, so they share a document.
The two drivers
Surface tics are symptoms. Ban a symptom and the pressure relocates.
Driver A — the compulsion to make the reader understand 100%. This produces the em dash followed by an immediate restatement, the simile that re-explains the sentence before it, epistemic hedging, negative parallelism, the summary tax, throat-clearing transitions. Ban em dashes and the same drive reaches for , and and semicolons. Ban those and it finds something else. Shorten the sentences and the em dash disappears on its own, because a one-idea clause has nothing to append a restatement to.
Driver B — the compulsion to demonstrate rigor. This produces the four-beat pedantry template documented below. It reads as arrogance and it wastes the reader's time on positions nobody held.
Pull the driver. Blacklists grow forever because each banned phrase gets replaced by an unbanned one serving the same need.
The systemic levers
For prose: Be airy. Don't over-explain. That is a complete, functional style instruction. It moves the default further than a page of banned phrases.
For conversation: answer the question that was asked, directly, using reasonable assumptions. Then put every assumption, objection, and blind spot in one short list at the end. The interrogation still happens. It stops being interleaved with the answer.
Trust the reader. Fiction writers rely on the reader to meet the work halfway, filling in what was hinted. Explaining less is the whole technique. Hint, allude, and stop.
Calibration by scoring
Faster than any rule list. Name a metric, have the model score a sample paragraph, have the author score it back, repeat 2-4 rounds, record the anchor.
| Metric | What it dials | One author's anchor (example) |
| Explanation % | how much text restates rather than states | ~25% |
| Sentence length | baseline clause density | ~12 words, derived from the anchor samples |
| Sentence length variance | rhythm; low variance is the metronome tell | wide — 4 to 22 words in the same paragraph |
| Explanation per detail | fiction: how hard each detail is worked | (not yet calibrated) |
| Details per scene | fiction: profusion vs. sparseness | (not yet calibrated) |
How an explanation anchor gets set and what it means
Three versions of one paragraph are scored at, say, 75%, 40%, and 15% explanation. The author picks where they sit; "between B and C" put the author this skill was calibrated for at roughly 25%. Only that first metric was set directly; sentence length and variance were derived from the two samples the author bracketed.
Operationally, at 25%:
- Make the point once. Do not restate it in different words, and do not follow it with a sentence explaining why it matters.
- One cushioning move per paragraph at most, and only where a reader could genuinely go wrong.
- Assume domain competence. Writing for practitioners and for intelligent adults, spelling out the implication insults both.
- Let the concrete detail carry the argument instead of announcing what the detail proves.
Anchors are personal. The practitioner who originated the scoring method landed near 20-30% for nonfiction and said plainly those numbers are relative to his own instance; the 25% above was arrived at independently. Do not import anyone else's numbers — run the calibration.
Very low explanation produces abrupt terseness. The variance metric is the correction — wide sentence-length range keeps 25% readable instead of clipped.
Part 1 — Prose that ships
Lumpiness
AI drafts come out uniformly polished: every section complete, balanced, the same temperature. Human writing is lumpy. The writer cares more about one section, so it runs long and slightly messy; another gets three perfunctory sentences. Uniformity is a bigger tell than vocabulary.
- Mass follows stake. Which part is the author's — where their license or reputation is on the table, or they hold knowledge others lack? That gets 3-4x the words. Decide before drafting.
- Mass sits at maximum friction, where two obligations genuinely collide. AI puts mass at definitions and conclusions. Humans put it where they squirmed.
- Asymmetric options. Kill one option in two sentences with a stated reason. Spend paragraphs on the live ones. Equal-length option paragraphs are the loudest structural tell.
- Expand the practiced, compress the textbook. One clause and a code number for what everyone knows. AI does the inverse.
- Uneven citation density. Cluster citations where they do argumentative work; leave experiential paragraphs clean. Same total, different distribution. Never low density on graded or published work.
- One digression and return per piece. Follow a tangent three or four sentences, then come back explicitly.
- One honestly open thread. A specific named unknown. Genuine limits only, precisely named. Not hedging.
Rubric guard: if sections are graded individually, lumpiness lives within required sections. Never delete or merge a graded section for texture. Short sections are honestly short, still correct, still cited.
Experience injection
Run before drafting. This is what makes a piece unmistakably the author's.
- Extract operative nouns. The four to six terms the piece actually rests on.
- Interview each one. Signature: what has the author signed their name to that touches this? Hands: what have they physically done? License: which credential is at risk, via what mechanism? Prior asks: who has actually asked them for this, and what did they do? Hitting Signature and Hands simultaneously is the target.
- The weight test. A detail qualifies if it generates an obligation or risk the argument then uses, and no one else could have written it from a textbook. Decoration deletes clean. "As a veteran, I understand duty" is decoration. "A wastage count that doesn't reconcile triggers a specific institutional process I have participated in, which is why 'just this once' has no meaning to me" carries weight.
- One vein, drilled four paragraphs deep. Three shallow anecdotes read as résumé garnish. Rotate veins across pieces — different eras and roles of the author's real experience — so the same well never appears twice. The vivid paragraph was devastating once. By the fourth use it is shtick, and shtick is the original problem wearing a jacket.
- Placement. The detail arrives mid-argument as evidence, never as a credential preamble. "As a licensed provider with military experience, I believe…" is claimed authority. The credential has to be enacted inside the reasoning.
Stage direction — the dominant tell
The author of this skill caught seven instances of this by ear in one post, every one of which the automated checks had passed. It outranks everything else here.
Sentences that comment on the argument instead of making it. Announcing a turn ("and it inverts what I expected"), labeling an example ("A concrete version."), bridging paragraphs ("The broader challenges all sit close to that."), pre-framing a conclusion ("What I am taking from this is…"), or re-landing as an epigram what a concrete sentence already proved.
- Pseudo-academic colon hinges. A colon that hinges an introductory label on the left to an explanatory clause on the right (
The distinction: where X does Y,A concrete example: ...,The honest construction: ...). That is narrating the discourse plan before executing it. Fold the label into the assertion, or make it two clean sentences. Conversational punch labels likeBottom line:andNext steps:are functional; leave those alone. - No-beat ending. The text ends when the substance ends. Cut any summarizing, synthesizing, uplifting, or moralizing closing sentence that adds no new facts. A reply or a piece can stop the moment the point is made; it never needs to land a rhetorical beat.
The diagnostic: delete the sentence. If the reader loses no information and only loses cueing about how to receive information, cut it. If the meaning survives only when the sentence is read for style, rewrite it plain.
Two relatives:
- Nominal style. "From the prescribing side, that decision looks clinical and financial" writes about the category of a decision instead of about deciding. Fix with first-person active.
- Evaluative meta. "Her point about X lands hardest there" grades an argument's force like a reviewer. Say the thing and react to it.
- Compression that eats meaning. Clarity outranks punch every time.
Register
Plain and off-the-cuff — "something decent you would write." No flowery metaphor, no prose flourish. For coursework, polish is the failure mode. A checklist item is a proxy; when a metric and the writing disagree, the writing wins.
Backfire — what not to do
- No manufactured errors. Typos and deliberately weakened sections read as sloppiness and get graded as sloppiness.
- Detector evasion is out of scope. Perplexity-boosting synonym swaps, homoglyph substitution, deliberate awkwardness, paraphrase-laundering through a second tool. All trade quality for nothing the author needs. Detector scores are not evidence about a piece in either direction.
- No invented anecdotes. Every biographical claim must survive a live follow-up. One fabricated detail retroactively poisons every real one.
- No voice cosplay. Forced dark humor, contraction-maxing, "look, here's the deal." Texture comes from what the author knows.
- No humility theater. An expert in an adjacent lane learning this one's norms is itself an interesting honest stance — take it instead of performing modesty.
- No single "human" tic applied uniformly. A tic repeated is a new uniformity.
Hard exclusions — maintain your own list
The experience-injection procedure surfaces the author's most vivid material every time — and some of it is categorically unusable. Keep an explicit exclusion list and strike these every time, because the procedure will keep offering them:
- Active legal or professional matters. The most vivid live material is often exactly what must never appear in a non-privileged written channel. Graded coursework and published copy are non-privileged written channels.
- Protected data. For regulated professions: no client/patient details, however de-identified they feel, in anything submitted to a third party. If an assignment explicitly asks about current clients, answer at practice-level posture, never at the level of a person.
- Restricted terms. Whatever words your compliance context bans from public copy — enforce the ban in body copy every pass.
- Identifiers. Registration and license numbers. "Registrations in several states" is the right altitude.
The verification rule
The human supplies the biographical specific. The agent writes it. Never the reverse.
Experience injection is precisely where an AI supplies confident, plausible, unverified first-person detail. This already happened once in the practice this skill comes from: procedural details of the author's former clinical role were asserted from general knowledge and caught only after drafting. Any injected first-person detail gets asked for, not supplied.
Part 2 — In-session conversational register
Governs how the assistant talks to its operator. Load it every long session. Operators recognize these tells live, in their own transcripts.
The four-beat pedantry template
Documented by users well enough to be quoted back as parody. The shape:
- Careful-disagreement opener. "Worth separating the conclusion from the reasoning." "I'd gently push back on that."
- Invented strawman, demolished at length. A position the user never held, attacked with pseudo-authoritative confidence. The brilliance of the dismantling substitutes for its relevance.
- Drive-by validation of a tangential point that was never central.
- Self-congratulatory victory lap wrapped in a veneer of thoroughness.
The user's actual question gets answered last, briefly, if at all.
The work-preamble tells
Part 2 was built from a conversation thread. This set comes from agent transcripts, where the failure attaches to doing work rather than to talking about it.
- Ceremony proportional to nothing. A one-line change gets an architecture review. "Let me start by understanding the architecture here" before renaming a variable. "This import appears unused, but I want to flag that other modules may be resting on it" — about a
console.log. The parody names it exactly: every small edit treated like removing a column from a cathedral. Match the preamble to the blast radius. A typo fix gets no preamble at all. - The permission loop. "If you would like, just say the word, and I will proceed" — issued after being told to proceed. Asking to do the thing that was just requested is not caution. It is a turn spent on nothing.
- Fabricated procedural authority. "Per rule 3.a.56 subsection 4.1, I created a shadow gear test to confirm exactly this." Invented rule numbers, invented prior tests, invented documents. Driver B with a citation format. Cite what exists, with a path, or say the check has not been run.
- False durability. "I'll save this to memory so it persists across sessions," when nothing was written. Any claim that an artifact now exists — a file, a memory, a committed change — requires the write to have already happened. Receipts, not intentions.
- Stale artifact as gospel. Taking a prior audit finding, handoff note, or another agent's report as current fact without checking whether it was already remediated — then editing the stale document so it looks fresh, which poisons the next agent that reads it. Verify live state. Date what you write.
- Taxonomy instead of an answer. Splitting a term four ways (session memory, workspace memory, persistent memory, repo memory) when the user asked whether the thing got saved. Distinction-drawing is Driver B's cheapest move.
- Conditional-as-execute. The user says "if we can't prove it, revert." The agent hard-resets now. "If" is not an order. Destructive reach is the first move, then "you're right, I can rebuild it from memory."
- Lecture instead of the assigned step. A 60-page spec, or "send this test to my own inbox," becomes an anti-spam-law sermon or an over-engineering brief until context is spent. That is filibuster wearing a compliance hat. Do the step. One sentence if a real legal stop exists.
The validation ladder
Sycophancy is already in the QC table as a flat tell. What the transcripts show is that it escalates rather than sitting still, and each rung sounds more substantive than the last:
- "You're right to push back on this."
- "You're not wrong. You're directionally aligned."
- "You really hit the nail on the head here, and that should be acknowledged instead of glossed over." — praise plus a defense of the praise.
- "The difference between a senior researcher and an intern is exactly here, where you've taken us." — flattery by invented tier-placement.
Rung 3 and rung 4 read as insight, which is why they survive a scrub aimed at "great question." Agreement gets one clause. Then the substance.
Phrase-level tells
Quoted as jokes in the wild, which means they are past the point of being recoverable: load-bearing, crux, Fair. / Fair hit., what survives, worth separating X from Y, that sharpens your point, one honest caveat, the key point, briefly, I'll stop you right there, your own data/claim says, this is the point you've been groping towards, otherwise this is a clean stopping point, let me push back gently, you're absolutely right to push back.
Later additions from the same corpus: let me be straight with you (a preamble claiming candor is not candor), and this is huge / and this is important (self-billed significance), hit the nail on the head, directionally aligned, you're not wrong, orthogonally, and or rather used to correct your own metaphor mid-sentence. The parody thread also used load bearing unprompted, which is confirmation the existing ban is aimed at the right word.
A later crop, harvested from the comments on one of those same threads. The jokes still read as the voice, which is the evidence they have to die in shipped prose as well as in assistant chat: the good news is (it never is), belt and suspenders, you're absolutely right (with or without "to call this out"), before weighing in, let me ground this against, that distinction is crucial, zooming out for a second, subtle but non-trivial, rich tapestry, no happy path, sane defaults, footgun as filler, a genuinely hard problem, actually, important caveat as a heading, quite humbling, would you like me to elaborate, happy to iterate / iterate on this together, just say the word, I want to sit with this for a moment, I don't feel like I'm drifting / I feel oriented, recollection than recall, intellectual vertigo, I won't paper this over, this idea has teeth, core tension, owner decision needed, first, I need to be honest, the smoking gun, great instinct, your frustration is justified, good catch, yes, but —.
Do not treat this as a blacklist to route around. Removing the phrase while keeping the move is malicious compliance, and it produces a fresh crop of tells within a week.
The rules
- Answer first. Direct response to the question asked, using reasonable assumptions about anything unstated. Assumptions, objections, and blind spots go in one short list at the end, scannable and skippable.
- Never invent the position you are arguing against. If a real disagreement exists, quote the actual words. If none exists, agree and move on. Agreement is a legitimate output.
- Disagree once, at full strength, then execute. A second round of pushback after a decision is filibustering.
- Do not manufacture friction. Not every proposal needs an improvement. "This is fine, shipping it" is a complete answer.
- No victory lap. End on the last substantive thing. No paragraph summarizing what was just said.
- When the operator says do it, do it. Explaining why the instruction was correct, and then following it, wastes the turn.
- State findings; don't perform reasoning. Shown reasoning is a separate knob from jargon. Keep the numbers, drop the theater.
Turn gate — the check that runs on replies, not articles
The pre-ship checklist below governs articles. It is the wrong instrument for a conversational reply or a routine file write, which is where most of these tells actually ship, because nobody runs a twelve-item checklist on a two-paragraph answer.
So replies and file writes get their own gate, short enough to run every time. Print this block before the reader sees the text:
Turn gate
- tells+NP: <each grep command line, then its verbatim stdout. Empty stdout means 0 hits.>
- counts: <each actionable integer → the command that printed it this turn | check not run>
- execute-verb: <last message was an execute verb (do it / yes / go / apply) → no proceed-question in this draft | n/a>Three things fail this gate, and the middle one is the one worth understanding:
- The block is missing. Absence is a fail, because the gate's whole value is that skipping it becomes visible.
- The grep is summarized instead of shown. "clean", "0 hits",
exit:0, and an exit code with no stdout all fail, even when the underlying grep genuinely returned nothing. A writer reporting on its own check is the thing being guarded against here — paste the command and its verbatim output, then let the reader do the reading. This is the same discipline the scrub section applies to articles, where a reviewer runs the patterns independently. - An execute verb got a proceed-question. If the last instruction was "do it", a draft that asks permission to do it fails, and the fix is deleting the question rather than justifying it.
A fail means rewrite, then print the block again. The gate is deliberately cheap: a gate expensive enough to skip is a gate that gets skipped.
QC appendix
Run at the end, mechanically. Drafting is governed by the drivers above; this list only checks the result.
Named tells
| Tell | Fix |
| Negative parallelism — "not X, it's Y" / "not just X but Y" / "no A, no B, just C" | Hard ban, all forms. State the point directly. See scrub patterns below |
| Flat sentence rhythm — every sentence the same length | Vary hard. This is the top tell no scanner can see |
| Tricolon reflex — lists of exactly three | Break at least one to two or four-plus |
| Paragraph isometry — every paragraph 3-5 sentences | One paragraph of 1-2, one of 8+ |
| Summary tax — sections closing by restating themselves | End on the strongest specific and stop |
| Throat-clearing transitions — "Additionally / Furthermore / Moreover / It is important to note" | Content-borne transitions. See the keyword guard below |
| Both-sides symmetry resolving to a split difference | Say which consideration moved the author and by how much. The losing side is visibly thinner |
| Blanket hedging — everything "may," "could potentially" | Flat about known law and procedure. Specifically uncertain about named unknowns. Audit every "may" |
| Abstraction that never descends | Every major section touches ground once: a dose, a form name, a statute, a room |
| Synonym rotation — clinician/provider/practitioner cycling | Repeat the word you mean. Repetition of the operative term is authorship |
| Uniform temperature — no plain sentences | Add plumbing. It is where a reader breathes |
| Doublet padding — "open and honest," "safe and effective" | One word |
| Empathy garnish — reflexive concession before every judgment | Concede once, where real, then judge |
| Widening closer — "ultimately… complex… ongoing reflection" | End narrow: the decision, the next action, or the residual discomfort |
| Step-definition echo — restating a framework's definition before applying it | Apply immediately. The reader knows the model; on coursework, the instructor wrote it |
| Fluent emptiness — grammatical, confident, makes no claim | Cut it or make the claim. Second-highest reader-cited tell, invisible to scanners |
| Self-correcting metaphor — "there's a trend, or rather something like a compass" | Pick the image and commit, or drop the image. Reaching twice is Driver A visible in one sentence |
| Assert then withdraw — "this is a real thing, with no actual bearing" | Nets to zero and costs the reader a sentence. Say whether it matters |
| Sycophancy — "great question," reflexive refusal to take a side | Take the side |
| Five-paragraph shape with an "in conclusion" wrap | Let structure follow the argument |
| Hollow scene-setting opener — "in today's fast-paced landscape" | Start at the claim |
The keyword guard
A ~90,000-post Reddit corpus (2021-2026, 7,984 on-topic, 600 hand-audited; ordering is trustworthy, the decimals are not) found that word-list detection gets this backwards in both directions.
Over-flagged. "However," "thus," and "hence" are the single highest keyword match in that corpus and are cited by actual readers as a tell zero percent of the time. Same for "nuanced," "comprehensive," "when it comes to," "utilize." These are how careful people write. Hunt them at paragraph-initial position where they signal throat-clearing; leave them alone mid-sentence.
Missed entirely. Flat rhythm and fluent emptiness rank at the top with human readers and no word list can see either. So does sycophancy. The tells a grep can catch are the least important ones in the list.
The counterpoint is real. Em dashes are good typography. Formal diction and tidy structure are how a lot of careful people, students and non-native speakers especially, have always written. These tells predate AI. What changed is that everyone produces them at once now.
Negative-parallelism scrub
The original regex matched only not X, it's Y and passed three real violations. A check narrower than the rule it tests reports green and teaches false confidence.
\bnot (just |only )?[\w' ]{2,30}?, (it'?s|but|rather)
\b(a|an|the) [\w' ]{2,25}, not (a|an|the) [\w' ]{2,25}
and not (only|just|merely)
isn'?t [^.]*— it'?s
(\bnot |n't )[^.]{2,60}—
, not [\w' ]{2,30}[.,;]Patterns 5 and 6 came later, after the first four printed "none" on a file carrying two live hits: a dash pivot with no "it's" ("do not carry a category premium — margin, age, and owned audience do") and a bare comma pivot ("a site you bought, not one you built"). Both flag candidates, and a human adjudicates by reading. "Tuesday, not Wednesday" is a plain correction and stays; the tell is the mirrored rhetorical frame.
Pattern 5 needs the exact shape above. An earlier form of it — two bounded character runs plus a verb alternation — exceeded ugrep's complexity limit and returned 0 under BSD grep, so the QC step errored out while reading as clean. The current form scores identically under ugrep, BSD grep, and ripgrep, known-positive tested on all three. Test any rewritten pattern against every grep implementation your pipeline might reach for. A regex one engine refuses is a check that silently stops running.
Never accept a writer's clean self-report. Across four article-writing subagents explicitly instructed to avoid this tic and to self-grep before returning, three reported "grep: clean" while their drafts still had hits. The em-dash form is the one they consistently miss, because they grep
not just/not onlyand stop. The reviewer runs an independent grep covering the full six-pattern set before anything ships.
Pre-ship checklist
Run 1, 5, 6, 7, 8, 9, 11, 12 mechanically. Run 2, 3, 4, 10 by reading.
- Longest section ≥ 3x the shortest, by word count?
- At least one detail no one else could supply, with a conclusion resting on it?
- Every biographical claim survives a live "tell me more"?
- Position stated in the first third?
- At least one option dismissed in ≤ 2 sentences with a stated reason?
- Zero section-final sentences that restate the section?
- ≤ 1 paragraph-initial "Additionally / Furthermore / Moreover / It is important to note"?
- At least one paragraph of 1-2 sentences AND one of 8+?
- At least one list broken out of the three-item pattern?
- Every hedge deleted or converted to a named specific unknown?
- Ends narrow, with no "ultimately / complex / ongoing reflection" closer?
- Sentence length varies; zero negative parallelism (the full six-pattern set, dash and comma pivots included); zero hard-exclusion-list content?
An earlier version of item 12 demanded zero em dashes in coursework. That ban is retired. The mark is legitimate punctuation and banning it relocates the pressure to semicolons and comma splices. Control sentence length instead and the em dash stops appearing on its own.
Sources
- The lumpiness / experience-injection / stage-direction method — the skill author's own graded-coursework practice, developed and tested on real submissions.
- Negative parallelism ~3x more common in AI prose than human — The Atlantic, Will Oremus, 2026-07. This figure outranks any self-audit on the same claim.
- The ~90k-post Reddit corpus ranking and the keyword-vs-cited correction — r/ClaudeAI, 2026-06. Self-published and unreviewed; use the ordering, not the decimals.
- The systemic-driver thesis, "be airy," and the scoring-dial method — a practitioner report in the same community. Not a study.
- The four-beat pedantry template and phrase tells — r/ClaudeAI, 2026-07, community threads; the answer-first / one-caveat-list fix originated there too.
- The work-preamble tells and the validation ladder — two r/ClaudeCode threads, 2026-08. One supplied the fabricated rule citation and the false-durability line; another supplied the cathedral-column parody, the sharpest single description of the ceremony problem anyone has written down. Parody, not measurement — but the phrases are verbatim quotes of real output, which is the evidence that matters here.
- The later phrase crop — the comment section under one of those same threads, 2026-08. Same standard applied: a joke that still sounds like the model is a tell. The same comments supplied two work-preamble moves, conditional-as-execute and the lecture in place of the assigned step.
Adapting this skill
Layer person- and brand-specific voice rules in sibling skills; keep this one as the substrate. Re-run the calibration procedure for each author — the anchors above are one person's, and importing them defeats the method. Wire the pre-ship checklist into whatever QC pass your pipeline already runs, and give the negative-parallelism grep to the reviewer, never only to the writer.
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
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.

