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 has good trigger term coverage with natural keywords like 'transcribe', 'YouTube', 'podcasts', and 'summarize' that users would commonly use. However, it lacks an explicit 'Use when...' clause which limits its completeness score, and the scope of 'local files' is broad enough to potentially conflict with other file-processing skills.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to summarize a URL, transcribe a podcast or video, or extract text from a media file.'
Narrow or clarify 'local files' to reduce overlap with general file-processing skills—specify file types like audio files, video files, or transcript formats.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (URLs, podcasts, local files) and some actions (summarize, extract text/transcripts), but doesn't list comprehensive specific actions beyond summarize/extract. | 2 / 3 |
Completeness | The 'what' is reasonably clear (summarize/extract text from URLs, podcasts, files), but there is no explicit 'Use when...' clause. The parenthetical hint about YouTube/video serves as an implicit trigger but doesn't constitute explicit trigger guidance, capping this at 2. | 2 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'summarize', 'extract text', 'transcripts', 'URLs', 'podcasts', 'YouTube', 'video', 'transcribe'. Good coverage of common variations including the parenthetical fallback note. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of URLs, podcasts, and transcripts gives it some distinctiveness, but 'extract text from local files' and 'summarize URLs' could overlap with general file processing or web scraping 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 for routing. The content is efficiently organized and avoids unnecessary explanation. The only minor weakness is the somewhat vague guidance around handling large YouTube transcripts, which could benefit from a more explicit decision flow.
Suggestions
Clarify the large-transcript workflow: specify a concrete threshold (e.g., character count) for when to summarize first vs. return the full transcript, and add an explicit step sequence.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what URLs, PDFs, or YouTube are. The trigger phrases section is useful for routing, and flag/config sections are terse reference material. | 3 / 3 |
Actionability | Provides fully executable bash commands for all primary use cases (URLs, local files, YouTube). Flags, environment variables, and config file format are all concrete and copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill is relatively simple (single CLI tool), but the YouTube transcript workflow has a conditional step ('if huge, summarize first then ask') that lacks explicit validation or error handling. For a CLI wrapper skill this is mostly adequate but the guidance on handling large transcripts is vague. | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into clearly labeled sections (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
- attilaczudor/Test
- Commit
b3cef5f
- 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.