humanize SKILL.md skillA
humanize from xobotyi/cc-foundry is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add xobotyi/cc-foundry/humanize@git:20260911.101fcdbPins git:20260911.101fcdb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- xobotyi/cc-foundry
- Path
plugins/the-writer/skills/humanize/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260911.101fcdb, committed Sep 11, 2026
- First version recorded
- Aug 31, 2026
- Size
- 12,057 bytes
- Repository stars
- 23
- License
- MIT
Remove AI-writing tells from reader-facing prose and prevent them while drafting: the mechanisms that produce the tells, the thresholds that mark a passage, and the edit that fixes the text without flattening its author.
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
**Editing a good draft makes it worse.** Rubric-guided model editing lifted below-median drafts on every measured dimension and pushed above-median drafts down: coherence −13.92, framing −12.06, both p<.001, across 45 abstract pairs and 869 keystroke-level edit logs. The first decision is never which tells to fix. It is whether this text should be rewritten at all. **Fix the writing, not the detection.** Generated prose is worth fixing because it is vague, padded, and evasive. Detectors fire on post-training artifacts rather than on machine authorship, and they flag second-language and formulaic human writing at the same time. An edit whose purpose is a detector score is out of scope; every edit must improve the text for a reader. Two failures carry equal weight. Under-editing leaves the tells and the text reads as generated. Over-editing flattens voice, deletes specifics, and produces a different slop — and it is the one the measurements above say is easy to cause. ## Decide before editing Read the whole text first. Nothing below is decidable from a search, because every one of these tells has a legitimate twin a few lines away. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_tpqh4vyki66l7top/6070208caba343cb5dc7e76e07566851f66b20ef003a5515dcf486245b1fff72.json
Then /plugin install humanize@markdownregistry-tpqh4vyki66l7top in Claude Code. It installs git:20260911.101fcdb, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add xobotyi/cc-foundry/humanize@sha256:6070208caba343cbThe line at the top of this page pins the label git:20260911.101fcdb, 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_tpqh4vyki66l7top)
5 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 xobotyi/cc-foundry/humanize 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 humanize from somewhere else? Ask it: where did my humanize 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 Aug 31, 2026 and Sep 11, 2026, about one every 3 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260911.101fcdb latest | 2026-09-11 | 101fcdb | 12,057 B | A | view · diff |
| git:20260831.e97fee5 | 2026-08-31 | e97fee5 | 11,879 B | A | view · diff |
| git:20260831.65669d7 | 2026-08-31 | 65669d7 | 11,870 B | A | view · diff |
| git:20260831.a9df496 | 2026-08-31 | a9df496 | 11,712 B | A | view · diff |
| git:20260831.95a13f5 | 2026-08-31 | 95a13f5 | 11,643 B | A | 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/humanize/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 (12057 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
xobotyi/cc-foundry · 23 stars · license MIT · pushed 2026-11-13 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_tpqh4vyki66l7top GET https://markdownregistry.com/api/v1/resolve?ref=xobotyi/cc-foundry/humanize GET https://markdownregistry.com/api/v1/blob/6070208caba343cb5dc7e76e07566851f66b20ef003a5515dcf486245b1fff72
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 xobotyi/cc-foundry
Every file in xobotyi/cc-foundry