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

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

SKILL.md
Quality
Evals
Security

Quality

Content

62%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 delivers genuinely actionable, well-validated workflows with per-mode step lists, exact commands, and rigorous verification requirements. Its weaknesses are verbosity — the same scope, pass-budget, and reporting rules restated several times — and a set of references to non-existent bundle files (examples/, detector/) that undermines navigation.

Suggestions

Consolidate the pass-budget, verification-reporting, and protected-content rules, each of which is stated 3-4 times across the Editing contract, Modes, Marks pass, and Output format sections, into one authoritative statement referenced from the modes.

Fix or remove references to bundle paths that do not exist: examples/README.md, examples/<name>.json (cited as the --style config schema), and detector/validate.js (cited as the preservation validator).

Move the detailed Output-format policy and Tone-calibration material into a one-level-deep reference file, keeping a short per-mode checklist in SKILL.md to reduce the 317-line body.

DimensionReasoningScore

Conciseness

The 317-line body restates the same policies many times: editing-pass budget rules appear in "Iterate to convergence," the marks pass, and three separate Output-format paragraphs ("A later repair that restores the original text still retains the passes actually used"); protected-content and scope rules are given in the Editing contract, again under Modes ("Follow the editing contract for protected material..."), and again under Edit-mode Verification. That is noticeably verbose with several padded sections (anchor 2), though it never explains concepts Claude already knows, so it is not a 1.

2 / 5

Actionability

Guidance is largely concrete and executable: exact commands ("node scripts/normalize-quotes.js <rewritten-prose> --reference <original> --write", "node scripts/check-style.js <file> --config <path>"), explicit CLI flags, and a specified output structure (Issues found / Assessment; the four-item Verification checklist). It falls short of 5 because referenced tooling is not fully bundled — "examples/README.md", "examples/<name>.json", and "detector/validate.js" do not exist in the bundle — and no worked before/after rewrite example is given.

4 / 5

Workflow Clarity

Each mode has a numbered job list (rewrite: audit → rewrite → summarize; edit: read → edit in place → verify), validation is explicit (re-read the file, compare final text against the source span-by-span, "Only proceed when validation passes"-style gates), feedback loops exist (repair within the remaining pass budget, re-verify), and the four-item Verification checklist covers the complex process. This matches the 5 anchor; a 4 would require missing checkpoints, and none are missing.

5 / 5

Progressive Disclosure

The main reference is well signaled ("Before auditing or rewriting any text, read [references/patterns.md] in full" in a marked loading block) and the four scripts are referenced with exact invocations, but the body cites bundle paths that do not exist ("Schema and rationale: examples/README.md", "a bare name matching examples/<name>.json", "node detector/validate.js"), and ~150 lines of editing-contract and output-format policy are inlined in SKILL.md that could live one level deep. Structure is present with clear signaling, so above 2, but broken navigation and inline bulk keep it below 4.

3 / 5

Total

14

/

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 a model example: concrete capabilities, an explicit 'Use when' clause with natural quoted trigger phrases, third-person voice, and a distinct niche. It covers modes and options without padding or over-claiming.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Audit and rewrite content to remove AI writing patterns," a "detect-only mode," an "edit-in-place mode for files," voice profiles (casual / professional / technical / warm / blunt), and an "iterate-to-convergence pass" — giving comprehensive coverage of the skill's capabilities. It matches the 5 anchor (multiple specific concrete actions, comprehensive) rather than 4, which would require noticeable gaps in what the skill does.

5 / 5

Completeness

Both questions are answered explicitly: "what" in the opening sentence (audit and rewrite content to remove AI-isms, plus modes and options) and "when" via "Use this skill when asked to" followed by concrete trigger phrases. This is exactly the 5 anchor's pattern; 4 would require the 'when' to be less explicit or lack concrete phrases, which is not the case.

5 / 5

Trigger Term Quality

It quotes five natural phrases 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"), covering synonyms and paraphrases comprehensively. No file extensions exist for this domain, so that part of the 5 anchor is inapplicable; the synonym coverage is complete, keeping it at 5 rather than 4.

5 / 5

Distinctiveness Conflict Risk

The niche (removing AI writing patterns) is clearly staked out and the triggers are specific to it, so minimal conflict risk with generic editing or grammar skills. It is not merely "somewhat specific" (3) nor does it carry more than minor overlap with closely related editing skills (4) — the quoted trigger phrases are unambiguous about which skill should fire.

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

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