CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-writing-tropes

Detect and eliminate common AI writing tropes from prose. Use when drafting, editing, or reviewing text to avoid the predictable patterns that mark AI-generated writing.

71

Quality

87%

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

100%Weight 40%Scale 1-3

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

A well-structured catalog skill: concise overview, concrete offender lists, a clear editing workflow with a built-in density check, and clean one-level-deep references to verified bundle files. It is a strong example of progressive disclosure for an instruction skill.

DimensionReasoningScore

Conciseness

The body is lean (~65 lines), assumes Claude's competence, and never pads with definitions of what AI writing or tropes are; every section earns its place.

3 / 3

Actionability

As an instruction-only skill it gives concrete, specific guidance: named offender words ("quietly", "delve", "tapestry"), named structural patterns (negative parallelism, tricolon abuse), and a six-item self-check — actionable without code.

3 / 3

Workflow Clarity

"How to Use" gives a clear four-step sequence (draft → check → rewrite → re-read for density) with the re-read acting as a validation checkpoint, and the self-check provides an explicit checklist; appropriate for a simple single-task skill.

3 / 3

Progressive Disclosure

The body is an overview that signals six one-level-deep references (e.g. "See [references/word-choice.md]"), all of which exist as real files, with detail correctly split out rather than inlined.

3 / 3

Total

12

/

12

Passed

Description

75%Weight 40%Scale 1-3

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 clear, third-person description with an explicit Use-when trigger and a distinct niche. It is held back from the top band only by limited action specificity and trigger terms that under-cover the colloquial vocabulary users actually employ.

Suggestions

Add one or two more concrete verbs to broaden the action list beyond "detect" and "eliminate" (e.g. flag, rewrite, audit pattern density).

Surface the colloquial trigger terms ("slop", "AI patterns") into the description itself rather than only the metadata trigger, so the description matches how users actually ask.

DimensionReasoningScore

Specificity

"Detect and eliminate common AI writing tropes from prose" names the domain and two concrete actions, but stops short of the multiple specific actions (e.g. detect, flag, rewrite, audit density) that would warrant a 3.

2 / 3

Completeness

It states what ("Detect and eliminate common AI writing tropes from prose") and gives an explicit when clause ("Use when drafting, editing, or reviewing text..."), satisfying both halves with third-person voice.

3 / 3

Trigger Term Quality

"drafting, editing, or reviewing text" and "AI-generated writing" are natural terms, but the most colloquial triggers a user would actually say ("slop", "AI patterns", "ChatGPT-style") live only in metadata, not the description, leaving common variations uncovered.

2 / 3

Distinctiveness Conflict Risk

The niche is narrow and explicit — AI writing tropes in prose — with triggers tied to drafting/editing/reviewing, making overlap with unrelated skills unlikely.

3 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
joshuadavidthomas/agent-skills
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.