CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wtf

Re-explain the previous assistant message in short, plain English without adding information. Use when the user invokes "/wtf" or asks what the previous answer means.

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

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.

The body is an exemplary lean instruction-only skill: a single unambiguous directive plus six specific constraints, no verbosity, no padding, and no unnecessary file structure. The only improvement would be a small before/after example to make the expected output format concrete.

DimensionReasoningScore

Conciseness

"Rewrite only the previous assistant message." followed by six terse constraint bullets is maximally lean — no padding, no concepts Claude already knows, and every token earns its place — an exact match for anchor 5 and clearly above anchor 4, which requires "minor instances of over-explanation" that are absent here.

5 / 5

Actionability

The instructions are concrete and executable ("Lead with the main point", "Remove jargon or explain any term that must stay", "Return only the rewrite"), matching anchor 4's "mostly executable guidance with minor gaps"; it falls short of anchor 5 because no worked input→output example covers the common case, and it is far above anchor 3 since nothing is pseudocode or vague.

4 / 5

Workflow Clarity

This is a simple single-purpose skill (10 lines, one task) where the single action — rewrite the previous message under explicit constraints — is unambiguous, so per the rubric's simple-skill guideline workflow clarity scores 5; it is not a destructive or batch operation, so the validation cap does not apply.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is well organized (title plus a short constraint list), which per the rubric's simple-skill guideline earns anchor 5; nothing is inlined that belongs in a separate file, so anchors 4 and below do not fit.

5 / 5

Total

19

/

20

Passed

Description

78%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 well-formed description for a single-purpose skill: it states one concrete action, an explicit non-goal (no added information), and explicit triggers in third person with no fluff. Its only weaknesses are narrow action coverage in the what-clause and a small set of natural trigger synonyms.

Suggestions

Enumerate the concrete rewrite behaviors in the description (e.g., "Rewrites the previous answer to lead with the main point, strip jargon, and preserve the original meaning") so the what-clause lists several specific actions rather than one.

Add one or two natural trigger synonyms such as "put that in simpler terms" or "explain that again" so users who don't know the /wtf command still match the skill.

Optionally add a disambiguating clause (e.g., "only the previous message, not older turns") to further reduce overlap with general explanation skills.

DimensionReasoningScore

Specificity

"Re-explain the previous assistant message in short, plain English without adding information" names the domain and one concrete action with constraints, but does not list several specific actions — it matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive") rather than anchor 4's "several specific actions", and is clearly above anchor 2 because the action stated is fully concrete.

3 / 5

Completeness

It explicitly answers both questions: "what" is stated concretely ("Re-explain the previous assistant message in short, plain English without adding information") and "when" is stated with concrete trigger phrases ("Use when the user invokes '/wtf' or asks what the previous answer means") — an exact match for anchor 5, and clearly better than anchor 4's "when could be more explicit".

5 / 5

Trigger Term Quality

The triggers "invokes '/wtf'" and "asks what the previous answer means" are natural phrases a confused user would actually say, matching anchor 4 ("Good keyword coverage; a few natural terms missing") — below anchor 5 because synonyms like "put that in simpler terms" or "explain that again" are absent, and above anchor 3 because the terms present are natural rather than generic.

4 / 5

Distinctiveness Conflict Risk

The scope "previous assistant message" and the "/wtf" trigger define a clear niche, but the open-ended trigger "asks what the previous answer means" carries minor overlap risk with general explanation/simplification skills, matching anchor 4 ("Mostly distinct; minor overlap risk with closely related skills") rather than anchor 5's "minimal conflict risk".

4 / 5

Total

16

/

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/wtf/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.