CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

unslop

Cut AI tells from any writing. Must always apply.

62

Quality

78%

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 ./plugins/pstack/skills/unslop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 a highly actionable, well-organized editing checklist: concrete tells, specific fixes, and a process with a built-in self-audit loop. Its only weaknesses are minor verbosity in a few pattern entries and no offloading of longer explanations.

DimensionReasoningScore

Conciseness

The body explains nothing Claude already knows; nearly every line is a tell plus a fix (e.g. "'In order to' becomes 'To'"). A few entries carry long inline digressions (the em dash rule's parenthetical ban, the colon rule's two full example sentences) that could be trimmed, which keeps it just below the lean-and-efficient anchor.

4 / 5

Actionability

Every one of the 31 patterns pairs a concrete tell ("pivotal moment", "serves as", "utilize") with a specific fix, including full before-to-after rewrites ("'the file is parsed by the loader' becomes 'the loader parses the file'"). For an instruction-only skill, this is fully concrete, example-backed guidance covering the common cases.

5 / 5

Workflow Clarity

The Process section sequences scan, rewrite, add soul, and self-audit, with step 4 acting as an explicit validation feedback loop ("What makes this obviously AI generated? Fix remaining tells."). This is a clear sequence with a built-in check-and-fix checkpoint, matching the top anchor.

5 / 5

Progressive Disclosure

A single-file skill with no bundle files and well-organized sections (Process / Adding soul / patterns grouped by category), where the pattern catalog is core operating content that appropriately lives inline. Scored 4 rather than 5 because at ~80 lines a few verbose pattern entries could be tightened or split out to keep SKILL.md leaner.

4 / 5

Total

18

/

20

Passed

Description

58%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 communicates a clear niche (removing AI-sounding patterns from prose) in very few words, and its always-apply directive gives explicit (if broad) trigger guidance. Its weaknesses are the thin capability list and the absence of natural keyword variations, which leave routing and trigger-matching under-specified.

Suggestions

Replace "Must always apply" with concrete trigger phrases, e.g. "Use when editing or writing prose that might read as AI-generated, or when the user says it sounds like AI, AI slop, or too robotic."

Enumerate the core actions so the "what" is comprehensive, not just one action: e.g. "Detects AI tells (clichés, hedging, em dash overuse), rewrites them in plain speech, and adds human voice."

Include natural synonyms users actually say — "AI slop", "sounds AI-generated", "make it sound human" — to improve trigger matching.

DimensionReasoningScore

Specificity

"Cut AI tells from any writing" names the domain and one concrete action, but the skill's fuller capabilities (detecting specific AI patterns, rewriting, adding human voice) are not surfaced. This matches the anchor for naming the domain with 1-2 concrete actions without being comprehensive.

3 / 5

Completeness

It has a clear "what" ("Cut AI tells from any writing") and explicit trigger guidance ("Must always apply" is equivalent to a Use-when clause, so the missing-trigger cap at 3 does not bind). Scored 4 rather than 5 because the "when" is maximally broad rather than concrete trigger phrases.

4 / 5

Trigger Term Quality

"AI tells" is a relevant, domain-specific keyword, but the description misses common natural variations users would say such as "sounds AI-generated", "AI slop", or "make it sound human". Some relevant keywords are present, but synonyms and variations are missing.

3 / 5

Distinctiveness Conflict Risk

"AI tells" carves a fairly distinct niche, but "any writing" combined with "Must always apply" overlaps with virtually every writing and editing task, so it could still trigger alongside similar writing/editing skills.

3 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

adamsardo/pstack-claude

Path

plugins/pstack/skills/unslop/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.