CtrlK
BlogDocsLog inGet started
Tessl Logo

summarize

Summarize, condense, or digest content

61

Quality

72%

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 ./src/opensquilla/skills/bundled/summarize/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 tight, well-organized instruction-only skill that gives a concrete summary template without padding; its only weakness is the absence of a worked example that would make the output fully unambiguous.

DimensionReasoningScore

Conciseness

The 10-line body is lean and efficient — a one-line instruction, a concrete Format template, and a single closing guideline — with no padding and no explanation of what summarization is that Claude would already know, matching the score-5 anchor 'Lean and efficient; assumes Claude's competence; every token earns its place'. It is not 4 because there are no noticeable instances of over-explanation to trim.

5 / 5

Actionability

The body gives a concrete, executable template — Key Points (3-5 bullets), Details, Action Items (if applicable) — so Claude knows exactly what to produce, matching the score-4 anchor 'Mostly executable guidance; concrete ... with minor gaps'. It is not 5 because there is no worked example output and phrases like 'Brief expansion on each key point if needed' are slightly imprecise; it is above 3 because the guidance is a real, specific template rather than pseudocode or vague direction.

4 / 5

Workflow Clarity

This is a simple single-purpose skill under 50 lines whose single action — produce a structured summary in the given format — is unambiguous, so per the simple-skill exception workflow clarity can score 5. Summarization is neither destructive nor a batch operation, so the destructive-operations cap does not apply; it is not 4 because no checkpoint is genuinely missing for a task of this kind.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (no references/, scripts/, or assets/ bundle files exist, and the body references none), and it is organized into a clear title, instruction, and Format section, so per the simple-skill guidance progressive disclosure scores 5 with well-organized sections alone. It is not 4 because there are no organization gaps or misplaced inlined content.

5 / 5

Total

19

/

20

Passed

Description

52%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 clearly names the skill's purpose with good natural trigger synonyms, but it lacks any explicit 'Use when' guidance and relies on synonymous verbs over distinct concrete actions, leaving it moderately specified with cap-limited completeness.

Suggestions

Add an explicit 'Use when' clause naming concrete trigger phrases (e.g., 'Use when the user asks to summarize, get a TL;DR, recap, or condense content').

Replace the synonymous verb list with at least one distinct concrete action that differentiates the skill's output (e.g., '...into Key Points / Details / Action Items format').

Narrow the generic 'content' or pair it with source types to reduce overlap with general content skills.

DimensionReasoningScore

Specificity

The description names the summarization domain but the actions are minimal and generic — 'Summarize, condense, or digest' are three near-synonyms for a single action applied to generic 'content', rather than distinct concrete actions, matching the score-2 anchor 'Names the domain but actions are minimal or generic'. It is below 3 because there is not a set of 1-2 genuinely distinct concrete actions, only one action repeated as synonyms.

2 / 5

Completeness

It has a clear 'what' (summarize/condense/digest content) but no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 3 — 'Has a clear what but when is missing or only weakly implied'. It is above 2 because the 'what' is not vague, and below 4 because the 'when' is entirely absent rather than present-but-imprecise.

3 / 5

Trigger Term Quality

'Summarize, condense, or digest content' provides three natural keywords users would actually say, giving good synonym coverage, matching the score-4 anchor 'Good keyword coverage; a few natural terms missing'. It is not 5 because common variations a user might say — such as 'tldr', 'recap', or 'summary' — appear only in the separate triggers field, not in the description itself.

4 / 5

Distinctiveness Conflict Risk

Summarization is a recognizable niche signaled by three specific verbs, but the bare generic noun 'content' and the absence of any 'when' clause leave moderate overlap risk with general content-handling skills, fitting the score-3 anchor 'Somewhat specific but could still overlap with similar skills'. It is not 4 because nothing sharpens the trigger context to reduce that overlap.

3 / 5

Total

12

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
TokenRhythm/opensquilla
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.