CtrlK
BlogDocsLog inGet started
Tessl Logo

summarizer

Condense long articles, reports, and documents into clear, concise summaries.

60

Quality

70%

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 ./apps/desktop/electron/default-skills/summarizer/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 lean, well-organized instruction skill with a clear sequenced workflow and an explicit re-check validation step. Its main gap is the absence of concrete worked examples of output, which keeps actionability and conciseness at 4 rather than 5.

Suggestions

Add one short worked example showing input -> output for a representative case to push actionability toward 5.

Trim the motivational flourish in the intro ("A good summary saves the reader time without costing them accuracy") to tighten conciseness.

Optionally add an explicit fix-and-retry note after step 4 ("if a critical point was lost or misstated, revise and re-check") to give the workflow a full validation feedback loop.

DimensionReasoningScore

Conciseness

The body is lean, well-sectioned, and assumes Claude's competence without explaining what articles or summaries are, with only minor flourish ("A good summary saves the reader time without costing them accuracy") that could be trimmed. It is not a 5 because of that small bit of motivational padding, and not a 3 because the bulk is efficient actionable guidance rather than unnecessary explanation.

4 / 5

Actionability

Concrete, specific guidance is provided — explicit format options (one-liner, bullets, narrative, action items), a 4-step "How to work" procedure, and "lead with the takeaway" direction — which is actionable for an instruction-only skill. It is not a 5 because no concrete worked output examples are shown, and not a 3 because the guidance is specific and executable rather than pseudocode-level.

4 / 5

Workflow Clarity

"How to work" gives a clear 4-step sequence with an explicit validation checkpoint in step 4 ("Re-check against the source to confirm nothing critical was lost or misstated"). It is not a 5 because there is no explicit fix-and-retry error-recovery loop, and not a 3 because a real validation checkpoint is present and the sequence is unambiguous.

4 / 5

Progressive Disclosure

This is a simple skill under 50 lines with no need for external references, and it is organized into clear, well-signaled sections (When to use, Principles, Match the format, How to work, Output format), matching the simple-skill exception that allows a 5 on well-organized structure alone. It is not a 4 because there are no organization gaps or misplaced inlined content.

5 / 5

Total

17

/

20

Passed

Description

61%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 is clear and uses natural trigger terms but is missing an explicit "Use when..." clause, which caps its completeness. Specificity is adequate but lists only one action verb.

Suggestions

Add an explicit "Use when..." clause naming concrete triggers, e.g. "Use when the user asks to summarize, condense, TL;DR, or recap a long article, report, paper, transcript, or thread."

Enumerate one or two more concrete actions (e.g. "extract key takeaways and action items") to lift specificity beyond a single verb.

Include common synonyms (TL;DR, recap, digest) so the trigger-term coverage reaches the top anchor.

DimensionReasoningScore

Specificity

"Condense long articles, reports, and documents into clear, concise summaries" names the domain (articles, reports, documents) and one concrete action (condense into summaries), matching the anchor for naming a domain plus 1-2 actions without comprehensive coverage. It is not a 2 because it names a real action beyond the domain, and not a 4 because only one action verb is given with no enumerated capabilities.

3 / 5

Completeness

The description gives a clear "what" (condense long inputs into concise summaries) but no "when"/"Use when..." trigger clause, so per the judging guideline a missing explicit trigger caps completeness at 3. It is not a 4 because there is no "when" guidance at all, and not a 2 because the "what" is clear rather than vague.

3 / 5

Trigger Term Quality

"articles, reports, and documents" and "summaries" are natural terms users actually say when requesting condensation, giving good keyword coverage. It is not a 5 because common synonyms and variations (TL;DR, recap, digest, recapitulate) are absent, and not a 3 because the terms present are clearly natural rather than jargon.

4 / 5

Distinctiveness Conflict Risk

Summarization is a mostly distinct niche with clear triggers, with only minor overlap risk against general writing or editorial skills. It is not a 5 because the description lacks the explicit trigger phrases that fully minimize conflict, and not a 3 because the niche is narrower than generic "works with document files".

4 / 5

Total

14

/

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
holaboss-ai/holaOS
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.