better-documents: The Free Claude Skill That Tells Claude to Stop Looking Like Claude

144 stars, five commits, one file -- and the most useful paragraph in it names the exact fonts that give an AI-written document away.

better-documents -- a SKILL.md file for Claude and other skill-compatible agents. It applies five review passes to any business document the agent writes or reviews: audience, structure, formatting, wayfinding, naming.

Alternative to: nothing you can buy. This is the rare entry with no incumbent -- it replaces a default, not a product. The nearest paid market is AI deck generation: Beautiful.ai Pro at $14.50/month billed annually, Team at $40/user/month annually or $50 monthly with a two-seat minimum, and $45 for a single one-off presentation. That is a different job, and the section below says why.

Cost to run: free. It is a text file. The cost is that you need an agent to run it in, and whatever you already pay for that.

License: GPL-3.0, added 2026-07-24 -- two months after the content itself. An unusual choice for a prose artifact; GPL is written for software, and what copyleft means for a prompt file is genuinely unsettled.

Runs on: Claude, and any agent that reads SKILL.md. Drop it in your skills directory.

Requires: an agent that supports skills. Nothing else -- no install, no dependencies, no key.

Traction: 144 stars · 0 forks · 0 open issues · 0 releases · 5 commits total · one skill file, a README and a licence.

Liveness: slow -- the content has not changed since 2026-05-28, and the only commit since was adding the licence on 2026-07-24. See the note below on why that reads differently for a prompt file than for software.

Maturity: no version number. It is a finished document, not a release train.

Links: repo · the announcement · the 2024 post it is based on · Trendshift: not listed
Figures as of 2026-08-18.

What it does

It is one markdown file that changes how an AI writes your documents.

Without it, an agent asked for a proposal tends to do the same four things: bury the ask at the end, open with background instead of the conclusion, bold and underline and color everything, and produce something that looks unmistakably machine-made. better-documents is a set of instructions that stops each of those.

The file defines five passes, applied in order, each aimed at a different failure:

1. Audience and Purpose -- is the ask stated in the first third, or saved for the end? Is there jargon nobody explained?

2. Structure and Sequencing -- it calls the main failure "murder mystery structure," and flags any document whose conclusion arrives in the second half.

3. Formatting Restraint -- no two emphasis types on the same text, no underlines that aren't links, no more than two colours, white space instead of borders.

4. Wayfinding and Density -- every chart needs a title that answers "what does this show?" Every open question needs to be answerable with a choice rather than a discussion.

5. Naming and Versioning -- no _final_final, no documents named after the person receiving them, dates instead of sequence numbers.

It also has five modes -- generate, full-review, rewrite, targeted, quick -- so it applies at writing time rather than only as a cleanup pass. The author's stated preference is the first one: apply the principles while producing the document, "not as an afterthought."

The single most quotable paragraph is about Claude specifically:

"Claude's default document aesthetic -- warm cream backgrounds, serif display type (Georgia, Fraunces, Playfair), terracotta or amber accents, and a 'small all-caps label over a body copy block' slide layout -- is recognizable as AI-generated and inappropriate for most professional contexts. Do not apply it."

That is a named, specific, checkable list of tells. It is the same instinct as a banned-words list, pointed at visual design instead of prose.

What it replaces, and what that costs

Nothing. And that is the honest answer.

Repo Madness usually opens by naming an expensive product and printing its price. This entry cannot, because no product does what this file does. It is worth being direct about that rather than manufacturing a comparison.

What it stands opposite is a default -- the output an agent produces when nobody told it what a good document looks like. That default is free, already installed, and costs you in ways that never appear on an invoice: the deck that didn't get the decision, the proposal where the ask was on slide 14, the memo that read as machine-written to the one person you needed to convince.

The nearest paid market is AI document and deck generation, and it is a real market with real prices. Beautiful.ai publishes: Pro at $14.50/month billed annually, Team at $40/user/month billed annually or $50 monthly, with a two-seat minimum, Enterprise at 20+ seats on contact-sales, and $45 for a single presentation as a one-off. Gamma publishes four tiers -- Free, Plus, Pro and Ultra -- with Team and Business on contact-sales; its figures did not render to a scrape, so they are not printed here rather than guessed at.

But those tools sell generation and templates: give them a prompt, get a formatted deck. better-documents sells judgement: it does not make anything look good, it tells the thing making your document what "good" means. Someone paying Beautiful.ai $174 a year and someone using this file are not solving the same problem, and subtracting one from the other would be arithmetic this entry has not earned.

So the row in the directory reads "Alternative to: nothing you can buy." That is a real category, and until now the directory had no way to represent it.

Is it still alive?

Slow -- and the verdict needs a caveat this column does not usually have to make.

The facts first. There are five commits in the entire repository. Four landed 2026-05-28, the last of them a rename from document-review to better-documents. The fifth, on 2026-07-24, added the GPL-3.0 licence file. The instructions themselves have not been touched since May. There are no releases, no forks, and no open issues -- and no closed ones either, because nobody has filed any.

For software, that pattern is how a dead project looks.

For a single-file prompt artifact, it is not the same signal. This is a finished piece of writing. It has no dependencies to bump, no CVEs to patch, no platform API moving underneath it. A markdown file that says "state the conclusion first" does not rot the way a WhatsApp client does. Judging it by commit frequency imports an assumption that does not transfer.

What would actually make it stale is the platform changing around it -- Claude's default aesthetic shifting, or the SKILL.md format itself moving. The fonts named in that paragraph are a hostage to fortune: the moment Anthropic changes its defaults, that list is wrong, and there is no evidence anyone is watching for it.

The honest verdict is slow: the author shipped a finished thing and moved on, which is a legitimate way to release a document and a fragile way to maintain one.

Not on Trend- shift. It never trended. The 144 stars came from the author's own blog and Threads posts, not from GitHub's front page -- worth stating plainly, because a directory that implied otherwise would be misleading.

What people say

Thin signal, and the reason is structural rather than a research failure. The repository has zero issues, zero forks and zero discussions. There is no community around it to quote, because it is a file people copy rather than a project people join.

Reddit is blocked from the research sandbox, so nothing from there is quoted and no vote counts are claimed. A crosspost of the repo exists at r/cryptogeum -- an unrelated subreddit, which tells you something about how it spread.

The author's own framing, on Threads:

"I made a skill to at least help you clean up your docs"

-- Anil Dash, threads.com/@anildash

And on the reception, also on Threads:

"Thanks for the kind words! Hard to know what resonates these days"

-- Anil Dash, threads.com/@anildash

Beyond that, pickup has been in the LLM-tips genre -- the file turns up inside "Claude hacks" listicles on LinkedIn rather than in engineering discussion. That is a real signal about the audience it found, and not the one a careful piece of writing deserves.

The catch

It is instructions, not enforcement. Nothing verifies the agent followed the five passes. You get a better prior, not a guarantee, and you cannot diff the output against the rules.

The font list will go stale and nobody is watching. Georgia, Fraunces, Playfair, terracotta, amber -- that specificity is what makes the paragraph useful and also what makes it perishable. It has already been frozen for nearly three months.

GPL-3.0 on a prose file is unsettled ground. Copyleft on a document that an agent reads and acts on raises questions nobody has answered: does output derived from it inherit anything? Almost certainly not in any way a court would recognise, but if your organisation has a licence-review process, expect a conversation.

Some passes fight real conventions. Pass 2 flags "murder mystery structure" as a defect. Investor narratives, case studies and keynote openings deliberately withhold the conclusion. The file does anticipate this -- it says to "respect intentional choices" and flag the convention as a risk rather than a violation -- but an agent applying five passes mechanically will still nag you about it.

One person, no succession. Five commits, one author, no contributors. If it needs updating when the platform moves, there is exactly one person who might do it.

It solves the second-hardest problem. Structure, ordering and formatting are real failures and this fixes them. It cannot tell you whether the thing you are proposing is any good -- and its own constraints say so: "Don't invent content. If information is missing... flag the gap -- don't fill it in." That restraint is the best decision in the file and also the limit of what it can do for you.

Credits

Anil Dash (anildash), who wrote the 2024 post Make better documents and turned it into a skill two years later. Pricing verified against Beautiful.ai's and Gamma's own pricing pages on 2026-08-18; where a figure did not render, it is marked unverified rather than estimated. Repository facts read directly from GitHub the same day.