Skip to content

bg-szy/TOP-SKILLS / skills/agent-skills/avoid-ai-writing

avoid-ai-writing

Verified

Audit and rewrite content to remove AI writing patterns ("AI-isms"). Supports detect-only audits, edit-in-place file cleanup, voice and context profiles, and an iterate-to-convergence pass.

FileKindSize
CHANGELOG.mdmarkdown9.2 KB
CONTRIBUTING.mdmarkdown4.4 KB
GLOSSARY.mdmarkdown3.5 KB
LICENSEother1.0 KB
LICENSE.txtmarkdown1.0 KB
PROOF.mdmarkdown7.2 KB
README.mdmarkdown35.7 KB
SKILL.full.mdmarkdown151.4 KB
SKILL.mdskill md34.8 KB
package.jsonmanifest1.5 KB

CONTRIBUTING.md

View on GitHub
# Contributing

Thanks for helping improve this skill. It teaches an LLM (and now a deterministic
engine) to spot and fix AI-writing tells. Contributions are welcome — a few things
keep the project coherent.

## How the repo fits together

| Path | What it holds |
|------|---------------|
| `SKILL.md` | The human-readable workflow and activation instructions. |
| `references/patterns.md` | The canonical catalog of rules, word tiers, and context profiles. |
| `detector/patterns.js` | The deterministic engine — the executable subset of the rules. |
| `detector/CATEGORIES.md` | The map between `references/patterns.md` rules and detector `type`s. Keep it current. |
| `README.md` | The pitch and the numbered prose-pattern list. |
| `cursor-rules/`, `plugins/` | Editor and tool integrations. |

## Adding or changing a rule

First decide which kind of rule it is:

- **Regex-detectable** (a phrase, a character, a structural shape) → add it to
  `references/patterns.md`, add the detection to `detector/patterns.js` with a new `type`, and
  add a row to `detector/CATEGORIES.md`. Cover it with a fixture in
  `detector/patterns.test.js` (both a true positive and a case that must *not*
  fire).
- **Judgment-only** (needs reading for meaning — tone, structure, name-dropping)
  → add it to `references/patterns.md` prose and list it under "Skill-only" in
  `detector/CATEGORIES.md`. There is no detector type for these.

If you are unsure which it is, open an issue first and we will sort it out.

## Precision over recall

This skill is deliberately biased toward false negatives: a rule that wrongly
flags ordinary human writing is worse than one that misses a tell, because false
positives erode trust in every other rule. Before proposing a rule, ask who would
get flagged by mistake, and add carve-outs for the legitimate cases. A signal
that fires on most normal prose is not worth adding.

## Cite your sources

If your rule rests on a factual claim about how AI or humans write — "ChatGPT
emits curly quotes by default," "most writers rarely do X" — link a source for
it. These claims get checked, and some turn out wrong or more nuanced than they
first seem (smart quotes, for instance, are a typing-time default on macOS and in
Word, not a publication-step artifact). A claim with a citation can be verified;
an asserted one can't. Put the links in the PR description or inline in the rule.

## Style guides and licensing

The rules from the [#88 license audit](https://github.com/conorbronsdon/avoid-ai-writing/issues/88), recorded here so nobody has to rediscover them:

- **This repo bundles no style guide it cannot verify the license for.** The `--style` layer is config-driven; users supply their own conventions.
- **Openly-licensed guides may ship later as example configs** (Google, Microsoft, GOV.UK, and 18F qualify), using Vale's attribution pattern: disclaim endorsement, name the license, link the guide upstream.
- **Paywalled guides (CMOS, APA, MLA, AP) are never shipped, in any form, under any name.** Passing one to `--style` falls through to the fallback that claims no compliance. The reason is trademark and verifiability, not maintenance burden.

## Run the tests

```bash
npm test
```

This runs the engine fixtures, quote-normalization tests, and the `CATEGORIES.md` contract checks: every
detector `type` must be documented, every documented type must be real, and every
prose statement of the engine `type` total must match the code. All must pass. No
dependencies to install; Node 18+ only.

## Write clean prose

This repo polices writing quality, so the prose you add has to clear the same
bar. Run your additions through the skill itself. Keep rule bullets terse and
lead with the directive — match the length and tone of the bullets already in
`references/patterns.md`. Drop intensifiers like "strong" or "powerful"; let the rule stand on
its own.

## Changelog and versioning

Add an entry to `CHANGELOG.md` under a dated, versioned heading
(`## [X.Y.Z] — YYYY-MM-DD`), matching the existing entries. A new rule is a minor
version bump; update the `version:` field in the `SKILL.md` frontmatter to match.

## Generated artifacts

After changing `SKILL.md` or `references/patterns.md`, run
`bash scripts/sync-cursor-rules.sh`. Run `bash scripts/sync-plugin-skill.sh`
only when the optional plugin tree is present; this catalog intentionally keeps
that packaging surface out of the maintained copy.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall