CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

summarize-pro

When user asks to summarize text, articles, documents, meetings, emails, YouTube transcripts, books, PDFs, reports, conversations, or any long content. Also handles bullet points, key takeaways, action items, TL;DR, ELI5, executive summaries, chapter summaries, comparison summaries, translation summaries, thread summaries, and custom-length summaries. 20-feature AI summarizer with multiple formats, languages, and export options. All processing happens locally — NO external API calls, NO network requests, NO data sent to any server.

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 ./configs/microservice/bff-service/configs/agent-skills/clawhub/summarize-pro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 highly actionable per feature — concrete output templates, exact paths, and JSON schemas — but pays for it with poor token efficiency (triplicated command lists, gamification fluff) and a monolithic single-file structure with no progressive disclosure. The core workflow (log → update stats → trim) is never consolidated into one clear sequence.

Suggestions

Consolidate the three overlapping command listings (Examples, When To Activate, Updated Commands) into a single command reference section, cutting hundreds of redundant tokens.

Move the per-feature output templates into a reference file (e.g., references/formats.md) and keep SKILL.md as a concise overview with format-detection guidance, one level deep.

Define one ordered per-summary workflow (summarize → log to history.json → update stats → auto-trim to 100) including how streak_days is computed, and add a section covering the undocumented "set default [format]" command.

DimensionReasoningScore

Conciseness

The ~670-line body repeats the command list three times ("## Examples", "## When To Activate", "## Updated Commands") and includes padded gamification content ("🏆 ACHIEVEMENTS... Keep summarizing to unlock more! 🚀") plus a promo credit line. Not 1 because it never explains concepts Claude already knows; it is padded and redundant rather than educational filler.

2 / 5

Actionability

Provides concrete, copy-paste-ready output templates for each of the 20 features, exact file paths ("~/.openclaw/summarize-pro/history.json"), complete JSON schemas for saved/history entries, and explicit edge-case responses ("If text is too short (<30 words)..."). Not 5 because "export options" from the description never appears in the body, and stat-update mechanics (e.g., streak calculation) are unspecified.

4 / 5

Workflow Clarity

First-run setup is sequenced (mkdir, init settings, init history) and error handling is addressed, but the per-summary pipeline (summarize → log to history.json → update stats → trim to 100 entries) is scattered across Behavior Rules and feature sections rather than given as one ordered flow, and commands like "set default [format]" are listed with no handling section. Sequence is present but checkpoints and ordering are implicit — matches anchor 3, not 4.

3 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and all 20 feature specifications are inlined in a single ~670-line file. Section headers ("## FEATURE N") provide real structure, so it is not anchor 2's headerless wall, but content that clearly belongs in separate reference files (per-format templates, achievements list) is fully inline — matches anchor 3.

3 / 5

Total

12

/

20

Passed

Description

87%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 strong description with explicit when-to-use guidance and comprehensive natural trigger terms covering many summarization variants and content types. Its weaknesses are breadth ("any long content" invites overlap with any summarization capability) and a few unspecified marketing claims ("20-feature", "export options").

DimensionReasoningScore

Specificity

Enumerates many specific summarization modes ("bullet points, key takeaways, action items, TL;DR, ELI5, executive summaries, chapter summaries, comparison summaries, translation summaries, thread summaries, and custom-length summaries") with minor gaps — "20-feature" and "export options" are unspecified marketing-style claims. Not 5 because a few claims are vague counts rather than concrete capabilities; not 3 because coverage is broad and specific, not just 1-2 actions.

4 / 5

Completeness

Explicitly answers when ("When user asks to summarize text, articles, documents...") and what (a multi-format, multi-language summarizer with local processing: "All processing happens locally — NO external API calls"). Both are explicit with concrete trigger phrases, matching the top anchor; it does not fall to 4 since the when-clause is specific and comprehensive.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms including synonyms: "summarize", "tldr", "key takeaways", "action items", "bullet points", "executive summary", plus content nouns users actually name ("YouTube transcripts", "PDFs", "books", "reports", "meetings", "emails"). Clearly matches the anchor for comprehensive natural-term coverage including variations.

5 / 5

Distinctiveness Conflict Risk

The niche (summarization) is identifiable with distinctive triggers ("eli5", "tldr", "key takeaways"), but the claim "or any long content" and generic nouns like "documents" and "reports" make it very broad, overlapping any general summarization capability. Falls between 'mostly distinct' (4) and 'very broad; high overlap risk' (2) — somewhat specific but still likely to overlap with similar skills.

3 / 5

Total

17

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (679 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

13

/

16

Passed

Repository

UnicomAI/wanwu

Path

configs/microservice/bff-service/configs/agent-skills/clawhub/summarize-pro/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.