CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

denoise

Strip noisy AI writing patterns, commentary and filler from text while keeping every fact. Use when the user invokes "/denoise", or asks to denoise, de-fluff or cut the filler from a message, pasted text or file.

Quality

92%

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

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

An exemplary instruction-only skill: lean, fully actionable pattern lists with concrete examples, real one-level-deep references carrying the example load, and an explicit no-op fallback. The only gap is the absence of an explicit fact-preservation check before overwriting a target file.

DimensionReasoningScore

Conciseness

The body is pure directives ("Delete first.", "Do not add facts, caveats, advice, structure or new work.") with no explanations of concepts Claude already knows; inline quotes appear only to operationalize a pattern ("One issue. Two PRs. Bot writes, you review."). Every token earns its place.

5 / 5

Actionability

Concrete, executable guidance throughout: quoted pattern examples, an enumerated hype-word list, explicit phrase mappings ("in order to" -> "to"), character rules, per-target output rules, and a no-op fallback ("If nothing can be cut without losing information, return the text unchanged"). Per the rubric's instruction-only note, absence of code is not penalized when guidance is this specific.

5 / 5

Workflow Clarity

The single action is unambiguous with a clear decision rule ("Delete first... Rewrite only when deleting would lose information"), a Keep checklist, and per-target output handling. However, the file path overwrites the target file ("Write the result back to the file") without an explicit post-transform verification that every fact survived — a minor validation gap that fits anchor 4 rather than 5.

4 / 5

Progressive Disclosure

Both referenced files exist (references/obnoxious-humility.md, references/cute-labels.md), are one level deep, and are clearly signaled in the body ("Read `references/obnoxious-humility.md` for examples"). The example tables live in the reference files so the ~70-line SKILL.md stays a lean rule set — matching the anchor-5 structure of well-signaled one-level references under a clear overview.

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 tight, third-person description that clearly states what the skill does and when to use it, with concrete trigger phrases and good synonym coverage. The only gaps are minor: it describes a single transformation rather than a list of distinct capabilities, and a few natural phrasing variations ("trim", "tighten") are absent.

DimensionReasoningScore

Specificity

"Strip noisy AI writing patterns, commentary and filler from text while keeping every fact" names the domain, enumerates three concrete removal targets, and states the preservation constraint. It goes beyond the 1-2 actions of anchor 3 but is essentially one operation rather than the multiple distinct actions of anchor 5.

4 / 5

Completeness

Explicitly answers both questions: the what ("Strip noisy AI writing patterns, commentary and filler from text while keeping every fact") and the when with concrete trigger phrases ("Use when the user invokes '/denoise', or asks to denoise, de-fluff or cut the filler"). This matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say: "/denoise", "denoise", "de-fluff", "cut the filler", plus target forms ("message, pasted text or file"). A few common variations (e.g. "trim", "tighten", "remove the fluff", "make it concise") are missing, matching anchor 4 rather than comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (removing AI writing noise while preserving all facts) with a distinct slash-command trigger and specific trigger verbs, giving minimal overlap risk with general editing or summarization skills. Fits anchor 5; anchor 4's "minor overlap risk" would understate how narrowly the triggers are scoped.

5 / 5

Total

18

/

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

dwmkerr/editor

Path

skills/denoise/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.