summarize
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).
82
76%
Does it follow best practices?
Impact
100%
3.44xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/summarize/SKILL.mdQuality
Discovery
64%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 does a good job including natural trigger terms that users would say (transcribe, YouTube, video, podcasts) and identifies a reasonably clear niche. However, it lacks an explicit 'Use when...' clause which caps completeness, and the capability list could be more specific about what concrete outputs or formats it supports.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to summarize a URL, transcribe a podcast or YouTube video, or extract text from media files.'
Expand the specificity of actions beyond 'summarize or extract' — mention concrete outputs like 'generate text summaries, produce full transcripts, extract key points' to better differentiate from generic summarization skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names specific actions ('summarize', 'extract text/transcripts') and specific input types ('URLs, podcasts, local files'), but doesn't list comprehensive concrete actions beyond summarize/extract. | 2 / 3 |
Completeness | The 'what' is reasonably clear (summarize/extract text from URLs, podcasts, files), and the parenthetical hints at 'when' (fallback for transcribe YouTube/video), but there is no explicit 'Use when...' clause providing clear trigger guidance. | 2 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'summarize', 'extract text', 'transcripts', 'URLs', 'podcasts', 'YouTube', 'video', 'transcribe'. The parenthetical fallback note adds excellent coverage of common user phrasing. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of URLs, podcasts, transcripts, and YouTube creates a somewhat distinct niche, but 'summarize' and 'extract text from local files' could overlap with general summarization or file-processing skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that provides immediately actionable CLI commands with clear trigger phrases and organized sections. Its main weakness is the lack of error-handling or validation guidance—what happens when commands fail, keys are missing, or extraction returns nothing. The structure and token efficiency are excellent for a single-tool skill.
Suggestions
Add a brief error-handling note (e.g., 'If summarize fails with auth error, verify the relevant API key is exported; if extraction returns empty, try --firecrawl always').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what summarization is or how CLI tools work. Every section earns its place—trigger phrases, quick start examples, flags, and config are all presented without padding. | 3 / 3 |
Actionability | Provides fully executable, copy-paste-ready bash commands for all major use cases (URLs, local files, YouTube). Flags are listed concisely with their options, and config examples are concrete JSON. | 3 / 3 |
Workflow Clarity | The skill covers a relatively simple single-command tool, but the YouTube transcript workflow includes a useful conditional (huge transcript → summarize first, then ask to expand). However, there's no validation or error-handling guidance—e.g., what to do if the command fails, if a key is missing, or if extraction returns empty content. | 2 / 3 |
Progressive Disclosure | For a simple CLI wrapper skill under 50 lines with no need for external references, the content is well-organized into clearly labeled sections (trigger phrases, quick start, YouTube specifics, model/keys, flags, config) that are easy to scan and navigate. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 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 | 8 / 11 Passed | |
- Repository
- Hung-Reo/hungreo-openclaw
- Commit
d8d7f4b
- 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.