CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

avoid-ai-writing

Audit and rewrite content to remove AI writing patterns ("AI-isms"). Use this skill when asked to "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," or "make this sound less like AI." Supports a detect-only mode, an edit-in-place mode for files, an optional voice profile (casual / professional / technical / warm / blunt), and an iterate-to-convergence pass.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Failed to scan

The risk profile of this skill

The canonical home for this skill is avoid-ai-writing in conorbronsdon/avoid-ai-writing

SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, dense behavioral contract: modes are unambiguous, commands are executable, and the verification framework (pass accounting, residuals, stop reasons) is exceptionally rigorous. Its weaknesses are repetition — pass-counting, residuals, and protection rules are each explained multiple times — and two dangling examples/ references. Tightening the restated rules and fixing or removing the missing-path citations would raise conciseness and progressive disclosure.

Suggestions

Consolidate the editing-pass, residual, and protected-content rules into one authoritative section and reference it from Output format instead of restating each rule 3-4 times across the Iterate and Output format sections.

Fix or remove the dangling references to examples/README.md and examples/technical.json (either ship the examples directory or describe the config schema inline), since the body presents them as bundled paths.

Add a compact worked before/after example (a short flagged sentence, its rewrite, and the Verification report) to ground the audit-to-rewrite workflow without relying on the external patterns.md catalog.

DimensionReasoningScore

Conciseness

The body mostly adds non-obvious policy (editing contract, provenance constraints) rather than explaining known concepts, but restates the same rules repeatedly: editing-pass counting appears in "Iterate to convergence" and four more times in Output format, residuals are explained in three places, and protected-content rules appear in both the Editing contract and Output format. Mostly efficient but could be meaningfully tightened — not 2 (no padded concept explanations), not 4 (the repetition is substantial, not minor).

3 / 5

Actionability

Provides copy-paste-ready commands ("node scripts/normalize-quotes.js <rewritten-prose> --reference <original> --write", "node scripts/check-style.js <file> --config <path>", "node detector/validate.js --residual-policy warn <original> <rewritten>"), explicit mode triggers ("detect," "flag only," "scan"), and option syntax. Not 5: no worked before/after audit example, and the referenced "examples/README.md" / "examples/technical.json" paths do not exist in the bundle.

4 / 5

Workflow Clarity

Each mode has numbered steps (Read → Edit in place → Verify; Audit → Rewrite → Summarize), explicit validation (re-read the file, span-by-span comparison of final text against source), feedback loops (repair within remaining editing budget, re-validate), and a literal four-item Verification checklist (Editing passes / Checks / Residuals / Stop reason). This matches the 5 anchor's sequenced steps with validation and error-recovery loops.

5 / 5

Progressive Disclosure

The 125KB pattern catalog is properly externalized to references/patterns.md (one level deep, clearly signaled with reference-loading markers and a read-first instruction), and referenced scripts scripts/normalize-quotes.js and scripts/check-style.js exist. Not 5: examples/README.md and examples/technical.json are cited as factual paths but absent from the bundle, and ~300 lines of dense behavioral policy sit inline in SKILL.md; not 3, because the heavy content is well split and clearly signaled.

4 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: it states concrete capabilities in third person, gives an explicit "Use this skill when" clause with five natural trigger phrasings, and enumerates modes and options without padding. It closely matches the rubric's good-overall example pattern. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Audit and rewrite content to remove AI writing patterns," "detect-only mode," "edit-in-place mode," "voice profile (casual / professional / technical / warm / blunt)," "iterate-to-convergence pass" — with comprehensive coverage of the skill's capabilities in third person. No coverage gaps to place it at 4.

5 / 5

Completeness

Explicitly answers what ("Audit and rewrite content to remove AI writing patterns" plus modes and options) and when ("Use this skill when asked to…" with concrete trigger phrases). This matches the 5 anchor example pattern exactly; the when-clause is explicit, so the 3 cap for missing trigger guidance does not apply.

5 / 5

Trigger Term Quality

Five quoted natural phrasings users would actually say ("remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," "make this sound less like AI") plus synonyms and mode keywords. Coverage is comprehensive with variations, exceeding the 4 anchor's "a few natural terms missing."

5 / 5

Distinctiveness Conflict Risk

Clear niche — removing AI writing patterns — with triggers ("AI-isms," "AI writing," "AI tells") distinct from generic editing or grammar skills, giving minimal conflict risk. Not 4, since no meaningful overlap with closely related skills is apparent.

5 / 5

Total

20

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

conorbronsdon/avoid-ai-writing

Path

SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.