CtrlK
BlogDocsLog inGet started
Tessl Logo

zero-slop

Inspect or rewrite prose that sounds formulaic while preserving source facts, voice, and format. Use for de-slopping, humanizing, prose audits, or a final writing-quality gate. Do not use it as an authorship detector or to evade disclosure requirements.

72

Quality

91%

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

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

Excellent body: a clear mode-selection preamble, a sequenced workflow with a genuine validate-repair-rerun feedback loop, executable commands whose flags all exist in the bundled script, and disciplined one-level-deep references. The only deductions are minor wordiness in the boundaries and division-of-labor notes.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes Claude's competence (no explanation of what prose or readability is), but a few sentences could be trimmed, e.g. "The current AI assistant performs the contextual review and editing; the scorer does not rewrite text and no separate model receives the draft" and some overlapping boundary bullets about not inventing substance. Not a 5 because of these minor padded spots; not a 3 because there is no concept-explanation padding of the kind the anchor 3 example shows.

4 / 5

Actionability

Fully executable guidance: copy-paste commands (`python3 <skill-root>/scripts/slopscore.py --explain <draft>`, `--fidelity <original> <candidate>`), concrete flag guidance (`--genre social` for LinkedIn, `--formal` for research prose), a stdin option, and a defined fallback path (manual inspection via tells.md) — and every documented flag and referenced file was verified to exist in the bundle. Specific examples cover the common cases.

5 / 5

Workflow Clarity

An 8-step numbered sequence with an explicit validation feedback loop: step 7 runs the deterministic fact gate, "A non-zero result blocks an unqualified delivery. Repair the candidate once and rerun the gate", and step 8 rescores the final text with a rule for the residual-failure case. Mode selection and a failure fallback (no Python) are also handled, matching the validate→fix→retry anchor.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview that delegates detail to one-level-deep, well-signaled references, each with an explicit trigger for when to read it: overcorrection.md "before a substantial rewrite", platforms.md for named genres, tells.md as the no-Python fallback. All three reference files plus the bundled script exist and match their stated purposes, so navigation is complete and honest.

5 / 5

Total

19

/

20

Passed

Description

87%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 strong description: concrete capabilities, an explicit 'Use for...' trigger clause with natural keywords, and a rare explicit negative-trigger clause that sharpens routing and reduces conflict risk. Trigger-term coverage has a few synonyms missing, which is the only minor weakness.

DimensionReasoningScore

Specificity

Names several concrete actions — "Inspect or rewrite prose", "preserving source facts, voice, and format", "prose audits", "a final writing-quality gate" — with only minor gaps (e.g., no mention of specific file formats handled). Not a 5 because the action list is not fully comprehensive and each action is described at a fairly high level; not a 3 because it clearly goes beyond 1-2 generic actions.

4 / 5

Completeness

Explicitly answers both questions: what ("Inspect or rewrite prose that sounds formulaic while preserving source facts, voice, and format") and when ("Use for de-slopping, humanizing, prose audits, or a final writing-quality gate"), plus an explicit negative trigger ("Do not use it as an authorship detector or to evade disclosure requirements"). Matches the anchor 5 example structure of concrete what + concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrasings — "de-slopping", "humanizing", "prose audits", "final writing-quality gate", "formulaic" — that a user would plausibly say. A few common variants are missing (e.g., "make this sound less AI", "flat writing"), so it does not reach the comprehensive-with-synonyms level of a 5, but coverage clearly exceeds the 'some relevant keywords' bar of a 3.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (de-slopping/humanizing prose) with distinct trigger terms, and the explicit exclusion clause ("Do not use it as an authorship detector or to evade disclosure requirements") further reduces mis-triggering against adjacent writing/editing skills. Overlap risk with generic editing skills is minimal.

5 / 5

Total

18

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
iflytek/skillhub
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.