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

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

66%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 highly actionable with excellent mode separation, validation checkpoints, and a properly externalized pattern catalog, but it is noticeably padded — the same scope, protection, and pass-accounting rules are restated across many sections. Tightening the duplicated policy language would substantially cut tokens without losing guidance.

Suggestions

Consolidate the pass-accounting and verification rules: state them once in the Editing Contract or Output format section and reference them from the mode sections instead of restating 'editing passes'/'no-op'/'budget' rules in at least four places.

Merge the three per-mode output-format descriptions into a single table or shared template with mode-specific deltas, keeping the four-item Verification checklist as the one canonical definition.

Either bundle the referenced examples/ files (examples/README.md, example configs like examples/technical.json) or remove/qualify those path references the way detector/validate.js is qualified ('If the repo ships the detector engine').

DimensionReasoningScore

Conciseness

At ~5,000 words the body restates its own policy repeatedly: scope/protection/pass-budget rules appear in the Editing Contract, again in 'Iterate to convergence,' again across three paragraphs of the rewrite-mode output format ('0 editing passes' accounting is explained in at least four places), and again in detect and edit mode sections. This matches anchor 2 ('noticeably verbose; several unnecessary explanations or padded sections') — the content is novel, not things Claude already knows, so it is above anchor 1, but the duplication is well beyond the 'some unnecessary explanation' of anchor 3.

2 / 5

Actionability

Guidance is largely executable: exact commands (`node scripts/normalize-quotes.js <rewritten-prose> --reference <original> --write`, `node scripts/check-style.js <file> --config <path>`), explicit flag syntax, quoted trigger phrases per mode, and defined output templates with required sections. It falls short of anchor 5 because there is no worked before/after audit example in SKILL.md itself, the `<rewritten-prose>` scratch-file workflow is intricate to execute, and two referenced paths (`examples/README.md`, `examples/<name>.json`) are not in the bundle.

4 / 5

Workflow Clarity

Each mode has a clearly sequenced job list (edit mode: Read → Edit in place → Verify), validation is explicit and multi-layered (re-read the file, compare final text against source span-by-span, run the preservation validator with documented exit codes), and there are genuine feedback loops (corrective pass within a stated budget, residual reporting, the four-item Verification checklist: Editing passes / Checks / Residuals / Stop reason). This matches anchor 5's 'explicit validation steps; feedback loops for error recovery; checklists' despite the in-place file editing being potentially destructive.

5 / 5

Progressive Disclosure

The heavy material (125KB pattern catalog) is correctly one level deep in references/patterns.md and clearly signaled ('Before auditing or rewriting any text, read references/patterns.md in full'), and referenced scripts (normalize-quotes.js, check-style.js) exist in the bundle. It stays at anchor 4 rather than 5 because the body references files absent from this bundle (examples/README.md, examples/<name>.json) and inlines substantial policy detail (editing contract, tone calibration) that makes the overview itself long.

4 / 5

Total

15

/

20

Passed

Description

95%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.

A strong description: concrete capabilities, five explicit natural-language trigger phrases, and both 'what' and 'when' answered clearly. The only soft spot is that the core actions are stated a bit abstractly relative to the feature list that follows.

DimensionReasoningScore

Specificity

"Audit and rewrite content to remove AI writing patterns" plus "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" lists several specific concrete capabilities. It sits at anchor 4 rather than 5 because the two core verbs (audit, rewrite) stay somewhat abstract and the description never hints at what kinds of patterns are targeted, a minor coverage gap.

4 / 5

Completeness

It explicitly answers both questions: what ("Audit and rewrite content to remove AI writing patterns") and when ("Use this skill when asked to..." followed by five concrete trigger phrases). This is a direct match to the anchor-5 good example, which pairs a capability list with an explicit 'Use when...' clause; anchor 4's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

The trigger list — "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," "make this sound less like AI" — covers comprehensive natural phrasing with synonyms users would actually say. It clearly matches the anchor-5 example's breadth ("PDF files, PDFs, forms, document extraction, .pdf") rather than the 'a few natural terms missing' anchor 4.

5 / 5

Distinctiveness Conflict Risk

The AI-writing-cleanup niche is clear and the triggers ("remove AI-isms," "make this sound less like AI") are distinct enough that this would not fire for general editing, grammar, or document skills. It matches anchor 5 ('clear niche with distinct triggers; minimal conflict risk'); anchor 4's 'minor overlap risk with closely related skills' would only fit if triggers like "clean up writing" lacked the AI qualifier, but every trigger names AI.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

conorbronsdon/avoid-ai-writing

Path

skills/avoid-ai-writing/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.