CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stop-slop

Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/stop-slop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A tight, well-structured instruction skill: terse rules with inline counter-examples, an explicit pre-delivery checklist, a quantified revise threshold, and clean one-level-deep references. Its only slack is mild duplication between Core Rules and Quick Checks, and a couple of rules that lean abstract.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence ("No passive constructions. No inanimate objects performing human actions"), with no explanations of known concepts; the Quick Checks section restates several Core Rules (adverbs, passive voice, em dashes, vague declaratives), which is trimmable duplication.

4 / 5

Actionability

Guidance is mostly executable for an instruction-only skill: named patterns with inline examples ("the complaint becomes a fix", "The reasons are structural"), a concrete pre-delivery checklist, and a scoring threshold; a few rules like "Trust readers" and "Cut quotables" remain abstract, and worked before/after transformations live only in the reference file.

4 / 5

Workflow Clarity

This single-task skill has an unambiguous action plus explicit validation: the Quick Checks run "Before delivering prose" and the Scoring section defines a feedback loop ("Rate 1-10 on each dimension... Below 35/50: revise"). The simple-skill exception applies and the validation/checklist requirements for a 5 are met.

5 / 5

Progressive Disclosure

The ~60-line overview is well organized with clear sections, and all three references (phrases.md, structures.md, examples.md) are real files, one level deep, clearly signaled with markdown links, holding the bulk detail (128/134/59 lines) appropriately out of the main file.

5 / 5

Total

18

/

20

Passed

Description

66%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 answers both what and when in third person with a natural Use-when clause, but it compresses the skill into a single action and gates on broad writing contexts rather than the specific user requests this skill targets. It is clear and honest, just under-specified.

Suggestions

Enumerate the concrete actions in the description (e.g., "cut filler phrases and em dashes, break binary-contrast structures, apply an active-voice checklist, score drafts on a 5-dimension rubric") to raise specificity beyond a single action.

Add user-side trigger phrases such as "sounds AI-generated", "too robotic", or "make this sound human" so the skill fires on the requests users actually make.

Narrow the "Use when" clause (drafting/editing/reviewing any text is broad) to situations involving AI-pattern removal, reducing conflict with general editing skills.

DimensionReasoningScore

Specificity

"Remove AI writing patterns from prose" names the domain plus one concrete action, matching the 1-2-actions anchor; it does not list several distinct actions (cut filler phrases, break contrast structures, score drafts), so it stays below 4.

3 / 5

Completeness

Both what ("Remove AI writing patterns from prose") and when ("Use when drafting, editing, or reviewing text...") are explicitly stated, but the when clause names broad writing activities rather than the concrete situations that call for AI-pattern removal, so it fits anchor 4 rather than 5.

4 / 5

Trigger Term Quality

"drafting, editing, or reviewing text", "AI writing patterns", and "AI tells" are phrases users would naturally say, giving good keyword coverage; common variations like "sounds robotic", "make it sound human", or "too ChatGPT" are missing, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

The AI-pattern niche is somewhat specific, but "Use when drafting, editing, or reviewing text" would trigger on nearly any prose task, creating real overlap risk with general writing and editing skills.

3 / 5

Total

14

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

valeriibeck-star/claude-skills

Path

skills/stop-slop/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.