summarize

Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/summarize/SKILL.md

The canonical home for this skill is summarize in Hung-Reo/hungreo-openclaw

Quality

Content

86%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, actionable CLI reference with copy-paste commands and clean sectioning; its main gap is the absence of error-handling guidance for failed runs or missing credentials.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned with executable commands and terse flag/env lists; minor trim opportunities remain (the default model name is repeated in each quick-start command and the "best-effort" parenthetical appears twice).	4 / 5
Actionability	Quick start gives copy-paste-ready commands covering the common cases (URL, local file, YouTube summary, transcript extraction), and flags/keys are documented concretely.	5 / 5
Workflow Clarity	The single-action CLI flow is unambiguous and the transcript section adds a decision checkpoint (return a tight summary first, then ask which section to expand), but no error-recovery guidance is given for failed extractions or missing API keys.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no need for external references and is organized into clear, well-signaled sections (When to use, Quick start, YouTube, Model + keys, Useful flags, Config), satisfying the simple-skill exception.	5 / 5
	Total	18 / 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 concise and covers the core capability with natural trigger phrasing, but it lacks an explicit "Use when..." trigger clause and only weakly signals when Claude should reach for it.

Suggestions

Add an explicit "Use when..." clause listing concrete triggers, e.g. "Use when the user asks to summarize a URL, article, podcast, or video, or to transcribe a YouTube/video."

Expand action specificity beyond summarize/extract (e.g. mention transcript extraction, length control) to push specificity toward 4-5.

Include common file extensions or synonyms (article, .pdf, .mp3) to broaden natural trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Summarize or extract text/transcripts" names the domain plus 1-2 concrete actions (summarize, extract text/transcripts) across URLs, podcasts, and local files, but does not enumerate a comprehensive set of specific actions.	3 / 5
Completeness	The "what" is clear (summarize/extract from URLs, podcasts, local files), but the "when" is only weakly implied via a single parenthetical fallback hint rather than an explicit "Use when..." clause, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural user phrases appear ("summarize", "extract", "transcripts", "transcribe this YouTube/video", URLs, podcasts), giving good keyword coverage; a few synonyms and file extensions (e.g. .pdf, .mp3, "article") are missing.	4 / 5
Distinctiveness Conflict Risk	The summarize/extract niche with a YouTube-transcript fallback is mostly distinct with a clear trigger, though broad "summarize URLs/articles" usage carries minor overlap risk with general web skills.	4 / 5
	Total	14 / 20 Passed

Validation

81%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: Bitterbot-AI/bitterbot-desktop
Path: skills/summarize/SKILL.md
Commit: 017761f

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.