CtrlK
BlogDocsLog inGet started
Tessl Logo

shh

keep-it-down

41

Quality

41%

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 ./skills/shh/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tightly written, action-first style guide with concrete Bad/Good pairs and a clear pre-send checklist; it assumes Claude's intelligence and avoids padding. Its only weakness is mild repetition around the compression-vs-correctness rules.

DimensionReasoningScore

Conciseness

The body is dense and skill-tight, assuming Claude's competence and avoiding textbook explanation of what APIs or frameworks are; a few sections (e.g. the long 'Never ADD word to sound caveman' paragraph) restate the same compression point multiple ways and could be trimmed, landing just below a 5.

4 / 5

Actionability

Concrete Before/After ('Bad'/'Good') pairs and specific commands like 'Run npm test -- auth.spec.ts' make the rules executable and copy-pasteable; it is instruction-shaped rather than code-shaped, and the guidance is mostly concrete with only minor gaps.

4 / 5

Workflow Clarity

The 'Pre-send check' and numbered 'Rules' sections sequence the response-construction process with explicit checkpoints (delete announcing first sentence, verify first/last line test), and 'When to break the style' covers error-recovery branches; it is not a destructive/batch workflow so the validation cap does not apply, and it stops short of 5 only because the main flow is presented as a checklist rather than a fully chained validate->fix->retry loop.

4 / 5

Progressive Disclosure

The SKILL.md is a single self-contained file with well-organized sections (Style, Rules, When to break, Pre-send check, Boundaries) and no bundle files or external references, which for a sub-50-line-equivalent single-purpose skill matches the simple-skill 5 anchor for well-organized content needing no external references.

5 / 5

Total

17

/

20

Passed

Description

3%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 frontmatter description is effectively a cryptic slogan ('keep-it-down') that fails to communicate the skill's purpose or trigger conditions. It scores at the floor on specificity, trigger quality, and completeness.

Suggestions

Replace 'keep-it-down' with a third-person description of the concrete behavior, e.g. 'Compresses chat responses into terse, action-first replies. Use when the user wants concise, no-preamble answers or says "be terse" / "keep it short".'

Add an explicit 'Use when...' clause naming natural user phrases ('be brief', 'no fluff', 'terse mode') so Claude can trigger it correctly.

Avoid figurative slogans as the description; use literal capability language consistent with the skill body's own anti-idiom rule.

DimensionReasoningScore

Specificity

The description 'keep-it-down' names no concrete actions whatsoever — it is a vague slogan, matching the score-1 anchor 'Entirely vague; no concrete actions; pure abstract language'.

1 / 5

Completeness

It answers neither 'what does this do' nor 'when should Claude use it' — there is no action and no 'Use when' clause, matching score-1 'Missing both what and when'.

1 / 5

Trigger Term Quality

'keep-it-down' is figurative slang rather than a natural keyword a user would say when they need terse-response behavior; it has no natural trigger phrases, matching the score-1 anchor for no natural keywords.

1 / 5

Distinctiveness Conflict Risk

It is extremely generic and could overlap with any noise/verbose-reduction skill, but it does gesture at a single narrow niche (keeping output short) rather than being totally content-free, placing it between anchors 1 and 2.

2 / 5

Total

5

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

description_field

'description' is very short (12 chars), consider making it more detailed

Warning

Total

15

/

16

Passed

Repository
choegyumin/agent-skills
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.