CtrlK
BlogDocsLog inGet started
Tessl Logo

stop-slop

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

66

Quality

80%

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

78%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 well-structured, lean instruction skill that points cleanly to three real reference files and includes a scoring feedback loop. Main gaps are mild redundancy between Core Rules and Quick Checks and an implicit rather than explicit workflow sequence.

Suggestions

Collapse or cross-reference Quick Checks against Core Rules to remove the restated adverb/passive/em-dash items and tighten token efficiency.

Make the workflow explicit with a short numbered sequence (apply rules → run Quick Checks → score each dimension → revise if <35/50) so the feedback loop is unambiguous.

Inline one or two complete before/after transformations in the Examples section rather than only linking out, so the core action is fully demonstrated without a file hop.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but the Quick Checks section restates the Core Rules (e.g. "Any adverbs? Kill them" reprises rule 1, "Em dash anywhere? Remove it" reprises rule 6), a minor redundancy that could be trimmed, placing it just below the 5 anchor.

4 / 5

Actionability

Concrete, specific guidance with inline anti-pattern examples ("the complaint becomes a fix", "The implications are significant") and a pre-delivery checklist; not a 5 because full before/after transformations live only in examples.md rather than inline, leaving minor gaps.

4 / 5

Workflow Clarity

The Quick Checks checklist plus the Scoring gate ("Below 35/50: revise") form an implicit apply → check → score → revise feedback loop, but the sequence is never numbered or explicitly tied together, so it sits at 4 rather than 5.

4 / 5

Progressive Disclosure

The body is a concise overview with well-signaled, one-level-deep references to phrases.md, structures.md, and examples.md (all verified to exist), matching the anchor for clear overview with appropriately split content.

5 / 5

Total

17

/

20

Passed

Description

82%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 tight, third-person description that clearly answers both what and when with natural trigger terms and a distinct niche. Its only weakness is specificity: it names one action rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain (prose/AI writing) with one concrete action phrased two ways — "Remove AI writing patterns" and "eliminate predictable AI tells" — but lists no distinct additional actions, matching the anchor for 1-2 concrete actions rather than the several required for 4.

3 / 5

Completeness

It explicitly states both what ("Remove AI writing patterns from prose") and when ("Use when drafting, editing, or reviewing text...") with concrete trigger phrases, matching the anchor that requires both answered explicitly.

5 / 5

Trigger Term Quality

"drafting, editing, or reviewing text" plus "AI writing patterns" / "AI tells" are natural phrases users say, giving good keyword coverage; not a 5 because it lacks synonyms and file/extension-style variations.

4 / 5

Distinctiveness Conflict Risk

"AI writing patterns" / "predictable AI tells" carves a clear niche (slop removal) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

17

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
holaboss-ai/holaOS
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.