better-writing SKILL.md skillA
better-writing from forjd/better-writing is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add forjd/better-writing/better-writing@"2.1.0" # x-release-please-versionPins "2.1.0" # x-release-please-version in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- forjd/better-writing
- Path
skills/better-writing/SKILL.md- Versions recorded
- 5
- Latest version
- "2.1.0" # x-release-please-version, committed Oct 31, 2026
- First version recorded
- Jun 14, 2026
- Size
- 15,806 bytes
- Repository stars
- 59
- License
- MIT
Rewrite, draft, and review prose so it is clear, specific, human, and fits its context. Use when improving emails, reports, documentation, marketing copy, UI text, or posts that sound generic, AI-written, verbose, salesy, or formulaic, and when the user asks to humanise/humanize, de-AI, fix text that sounds like ChatGPT, light edit, copy edit, proofread, or keep my voice. Covers voice calibration, anti-slop audits, and preflight checks.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Better Writing Use this skill to make prose stronger without flattening the writer. The goal is not to make everything casual or punchy. The goal is to make the text fit its audience, purpose, and medium while removing generic AI tells, filler, fake authority, and formulaic structure. ## Core workflow 1. Read the brief before editing. - Identify the genre/medium (=channel), audience, relationship, stakes, outcome (=purpose), and constraints (length, requested dialect, house style, exact wording). - Preserve required facts, citations, constraints, legal wording, quoted text, and formatting. - If the user gives a voice sample, audit it against the tell lists first; if it scores high, ask before treating it as the style source of truth. - For a draft from scratch, collect the substance before writing: the point, the facts, the writer's position, and any example or number they have. Draft by default and mark each missing fact with a gap marker such as `[example needed: a customer who hit this]`. Ask first only when the point itself is missing. Cutting tells cannot add missing content, and a brief with no facts produces generic prose however clean the sentences are. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_hmn6c2lsqgxiu6rh/0b34e84a63c22122ba10ffd8eca6373995470d587256938e8f00f546fcc56189.json
Then /plugin install better-writing@markdownregistry-hmn6c2lsqgxiu6rh in Claude Code. It installs "2.1.0" # x-release-please-version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add forjd/better-writing/better-writing@sha256:0b34e84a63c22122The line at the top of this page pins the label "2.1.0" # x-release-please-version, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_hmn6c2lsqgxiu6rh)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in forjd/better-writing/better-writing since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of better-writing from somewhere else? Ask it: where did my better-writing come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Jun 14, 2026 and Oct 31, 2026, about one every 35 days. Its first recorded version is graded C and its latest A.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| "2.1.0" # x-release-please-version latest | 2026-10-31 | ce73688 | 15,806 B | A | view · diff |
| "2.0.0" # x-release-please-version | 2026-10-30 | ad36fb2 | 15,806 B | A | view · diff |
| "2.0.0" # x-release-please-version | 2026-10-07 | 8e45d0b | 14,888 B | A | view · diff |
| "1.3.0" # x-release-please-version | 2026-10-07 | 3e23468 | 14,888 B | A | view · diff |
| git:20260614.0d7c441 | 2026-06-14 | 0d7c441 | 14 B | C | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/better-writing/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15806 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
forjd/better-writing · 59 stars · license MIT · pushed 2026-11-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hmn6c2lsqgxiu6rh GET https://markdownregistry.com/api/v1/resolve?ref=forjd/better-writing/better-writing GET https://markdownregistry.com/api/v1/blob/0b34e84a63c22122ba10ffd8eca6373995470d587256938e8f00f546fcc56189
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from forjd/better-writing
Every file in forjd/better-writing