CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ce-noslop

Rewrite, check, or draft prose so it carries no AI writing tells, reads plainly on the first read, and keeps every source fact. Use when asked to make writing plainer or free of those tells, to check writing for them, or when drafting from supplied content. Use ce-promote for channel-specific marketing copy.

Quality

88%

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

86%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-only skill: lean prose, deterministic mode routing, a seven-test checklist with remedies, and model bundle separation with conditional read triggers. The two gaps are the absence of any inline worked example showing a test applied to a sentence, and the fact-survival check being stated as a done-condition rather than an explicit verification step in the edit workflow.

Suggestions

Add one short before/after sentence pair to the tests section showing, say, the Mechanism or Portability test applied, so the abstract tests have a concrete anchor without leaving the body.

State the fact check as an explicit step in the edit workflow ("after rewriting, re-check every fact, number, name, and quote against the input before returning") rather than only as a done-condition.

Rewrite the line "Note that the pattern catalog did not apply inside detect findings or inside a change line the caller asked for, and nowhere else" — its double negative makes an exception rule hard to apply correctly on the first read.

DimensionReasoningScore

Conciseness

The ~45-line body is lean throughout: no concept Claude already knows is explained, and every rule is operational ("Rewrite only the sentences a test fails on", "One device proves nothing", "Keep exact identifiers, paths, commands, and thresholds"). One sentence — "Note that the pattern catalog did not apply inside detect findings... and nowhere else" — is dense enough to need rereading, but that is a clarity cost, not token waste, so it does not drop below anchor 5's "every token earns its place".

5 / 5

Actionability

The guidance is concrete and directly executable for an instruction-only skill: seven named tests each pair a check with a remedy ("Does the sentence say what the thing does, or how it feels? Replace the feeling with the fact"), mode defaults are deterministic ("no draft means author; an imperative on a draft means edit; a question about a draft means detect"), and boundaries are explicit ("never touch code blocks, quoted text, frontmatter, link targets, identifiers"). It misses anchor 5 because no worked before/after example of a test applied to a sentence appears in the body — examples live entirely in references/patterns.md.

4 / 5

Workflow Clarity

The sequence is clear (determine mode → apply tests → per-mode action → return) and validation exists in three places: the "Done" line is an explicit completion check ("every fact, number, name, quote, and citation in the input survives, and nothing was added"), edit mode carries an idempotency check ("a second pass on the returned text changes nothing"), and detect output format is specified ("Name each pattern found, quote the line, give the fix in a few words"). It falls just short of anchor 5 because fact-survival is stated as an outcome rather than an explicit re-verify step inside the edit workflow, so there is no stated feedback loop of re-checking the output against the input.

4 / 5

Progressive Disclosure

The split is exemplary: the core method (tests, modes, register, boundaries) is inline while the bulk material — a 7.6KB pattern catalog and a terminology guide — lives in references/patterns.md and references/terminology.md, both verified to exist and to deliver what is promised. Each reference is one level deep and cited with a conditional read trigger rather than a bare pointer: "For edit and detect, and for an author passage the tests alone do not settle, read references/patterns.md" and "For wording choices, read references/terminology.md".

5 / 5

Total

18

/

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: it names its three actions with measurable outcome criteria, gives an explicit multi-trigger "Use when" clause, and routes the closest neighboring use case to its sibling skill. The only weaknesses are un-concretized pattern examples and missing common synonyms like "AI-sounding" or "sound human".

Suggestions

Name one or two example tells (e.g. "seamless", "it's not just X, it's Y") in the description to make the detection capability concrete rather than abstract.

Add the common user phrasings "AI-sounding" or "sound human" to the trigger clause to catch the most frequent way users ask for this.

DimensionReasoningScore

Specificity

Names three concrete actions ("Rewrite, check, or draft prose") with three explicit outcome criteria ("carries no AI writing tells, reads plainly on the first read, and keeps every source fact"), covering all three of the skill's modes. It falls short of anchor 5 only because the tells themselves are never made concrete — no example patterns like "seamless" or "it's not just X, it's Y" appear, leaving a minor coverage gap for a detection capability.

4 / 5

Completeness

Explicitly answers both questions: the "what" is "Rewrite, check, or draft prose so it carries no AI writing tells, reads plainly on the first read, and keeps every source fact", and the "when" is a fully explicit trigger clause — "Use when asked to make writing plainer or free of those tells, to check writing for them, or when drafting from supplied content" — with three concrete triggers. This matches the anchor-5 example's structure exactly; it is not a 4 because the when-clause leaves nothing implicit.

5 / 5

Trigger Term Quality

Includes several natural phrasings a user would actually say — "make writing plainer", "free of those tells", "check writing for them", "drafting from supplied content" — matching anchor 4's "good keyword coverage; a few natural terms missing". It misses common synonyms such as "AI-sounding", "robotic", or "sound human", so it is not a 5.

4 / 5

Distinctiveness Conflict Risk

The niche (prose free of AI tells) is distinct, and the description actively disambiguates from the nearest sibling skill with "Use ce-promote for channel-specific marketing copy" — an explicit carve-out that reduces conflict risk below even the anchor-5 example. Not a 4: the overlap risk with other prose skills is addressed, not merely minor.

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

EveryInc/compound-engineering-plugin

Path

skills/ce-noslop/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.