Thanks for helping make AI text more human. Here's how to contribute.
- Follow the existing format (P1-P53 use this exact template — see SKILL.md for examples)
- Include:
- Trigger words: what to search for (regex-friendly when possible)
- What's happening: why AI does this — cite a source if you have one
- Fix: how to replace it (prescriptive, not "consider...")
- Before/after table: at least one real example, not invented
- Place it in the right category (Content P1-P8, Language & Style P9-P18, Communication P19-P21, Filler & Hedging P22-P30, Emerging P31-P43, Craft & Forensic P44+)
- Update three places in lockstep:
- Pattern count in README.md badge (
patterns-NN) - Pattern count threshold in
.github/workflows/ci.yml(EXPECTED=NN) - CHANGELOG entry under a new version
- Pattern count in README.md badge (
- Put the short entry (name, trigger, one-line fix, before/after) in
SKILL.md; put any longer "what's happening" notes or sources inreferences/patterns.mdso the core stays lean.
- Add more trigger words from real AI text you've encountered
- Add before/after examples
- Refine the fix instructions
If the skill flags something that's genuinely human writing, open an issue with:
- The flagged text
- Which pattern triggered
- Why it's a false positive
- Fork and create a branch (
feat/pattern-31-whateverorfix/false-positive-p7) - Make your changes in SKILL.md
- Keep
SKILL.mdlean: it is the always-loaded core, so push verbose deep dives, extra examples, and sources intoreferences/rather than growing the core. New patterns add a compact entry here and their depth there. - If you touch the CLI (
cli/), runcd cli && node --testand keep it green. New metrics or vocabulary entries should ship with tests (aim for a few positive and negative cases each, in the spirit of "every pattern earns its tests"). - Open a PR with a clear description
Be direct. Be helpful. Skip the pleasantries. We're humanizers, not sycophants.
If you found this skill useful, the highest-leverage way to help is submitting it to skill aggregators. Each row below is one PR away from listing.
| Aggregator | URL | Submission method |
|---|---|---|
| awesome-claude-code | hesreallyhim/awesome-claude-code | Open issue using "[Resource]" template, then PR adding row to THE_RESOURCES_TABLE.csv |
| awesome-claude-skills | ComposioHQ/awesome-claude-skills | Fork, add to "Communication & Writing", PR |
| awesome-claude-skills (Travis) | travisvn/awesome-claude-skills | README PR |
| awesome-claude-code (jquery) | jqueryscript/awesome-claude-code | README PR |
| awesome-claude-code (jman) | jmanhype/awesome-claude-code | README PR |
| ClawHub | docs.openclaw.ai/clawhub | clawhub skill publish |
| LobeHub Skills | lobehub.com/skills | Web form |
| awesomeclaude.ai | awesomeclaude.ai | Submission form |
| claudepluginhub | claudepluginhub.com | Auto-indexed via repo topics |
PRs in this direction are very welcome. If you submit and the listing goes live, drop a link in an issue so we can credit you here.