CtrlK
BlogDocsLog inGet started
Tessl Logo

bro

Restate the last message in plain human language, with no jargon.

62

Quality

73%

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 ./pstack/skills/bro/SKILL.md
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 a model of token efficiency: a single unambiguous, imperative instruction with no padding and no structure the skill doesn't need. Its only weakness is the absence of a brief example showing the desired plain-language restatement style, which keeps actionability at 4.

DimensionReasoningScore

Conciseness

The body is two lean lines — "Restate your last message. Stop using jargon and speak coherently. State it more simply and concisely, like one human talking to another." — with zero padding and no explanation of concepts Claude already knows. Every token earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

The guidance is direct, imperative, and executable for an instruction-only skill (restate, drop jargon, be simpler and more conversational), with only a minor gap — no example of the before/after transformation to anchor the desired style. It sits between 'some concrete guidance but incomplete' and fully concrete instruction, hence 4.

4 / 5

Workflow Clarity

This is a single-task skill and the single action is unambiguous: restate the last message plainly. Per the rubric's simple-skill exception, workflow clarity can score 5 for an unambiguous single action, and no validation checkpoints are relevant to a non-destructive restatement.

5 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files (references/, scripts/, assets/ do not exist), and nothing in the body belongs in a separate file. Per the rubric's small-skill guidance, an appropriately self-contained two-line body with no external-reference need scores 5.

5 / 5

Total

19

/

20

Passed

Description

53%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 single concrete capability clearly but stops there: no trigger guidance, no natural user phrasings beyond 'plain language'/'jargon', and no action coverage beyond the one behavior. It is a clear, jargon-free description that would benefit most from an explicit 'Use when...' clause.

Suggestions

Add a trigger clause, e.g. "Use when the user asks to simplify, restate, or de-jargon your last reply" — this directly lifts the completeness dimension.

Include natural user phrasings/synonyms such as "plain English", "in other words", or "ELI5" so trigger_term_quality reflects what users actually say.

Consider extending the 'what' slightly (e.g. mentioning tone: conversational, concise) to raise specificity from a single action toward fuller coverage.

DimensionReasoningScore

Specificity

"Restate the last message in plain human language, with no jargon" names one concrete action and its manner, matching the '1-2 concrete actions, not comprehensive' anchor. It is not 4 because there is no enumeration of specific actions or coverage of what the skill handles beyond the single restatement behavior.

3 / 5

Completeness

The 'what' is clear (restate the last message without jargon), but there is no 'Use when...' clause or any equivalent explicit trigger guidance. Per judging guidelines this caps completeness at 3, which fits the 'clear what, when missing or only weakly implied' anchor.

3 / 5

Trigger Term Quality

"plain human language", "no jargon", and "restate" are somewhat natural phrases, but common user variations like "simplify", "plain English", or "in other words" are missing. This matches the 'some relevant keywords but missing common variations or synonyms' anchor, not 4 which requires broad natural-term coverage.

3 / 5

Distinctiveness Conflict Risk

De-jargonizing/restating responses is a fairly distinct niche with clear intent, but it could overlap with general "simplify" or "explain" style skills. This fits 'mostly distinct; minor overlap risk with closely related skills' rather than 5, which requires a clear niche with distinct triggers.

4 / 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
cursor/plugins
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.