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 ./openclaw/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'. However, it lacks an explicit 'Use when...' clause which caps completeness, and the actions described are somewhat general (summarize/extract) rather than listing specific concrete capabilities. The parenthetical fallback note is a nice touch for disambiguation but doesn't substitute for proper trigger guidance.
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 local file.'
List more specific concrete actions beyond summarize/extract, such as 'generate transcripts from audio, pull article content from web pages, convert podcast episodes to text'.
| 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 fallback partially implies when, but it's not a proper trigger guidance statement. | 2 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'summarize', 'extract text', 'transcripts', 'URLs', 'podcasts', 'transcribe', 'YouTube', 'video', and 'local files' — good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of URLs, podcasts, and transcription is somewhat distinctive, but 'summarize' and 'extract text from URLs' could overlap with general web scraping or summarization skills. The YouTube/video fallback note helps but doesn't fully disambiguate. | 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 to do when commands fail or keys are missing. Overall it's a strong skill that efficiently teaches Claude how to use the summarize tool.
Suggestions
Add brief error handling guidance: what to tell the user if the API key is missing or the URL/file is inaccessible.
Consider noting common failure modes for YouTube transcript extraction (e.g., private videos, age-restricted content) and fallback behavior.
| 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 with concrete commands, flags, and configuration details. | 3 / 3 |
Actionability | Provides fully executable bash commands for all common use cases, specific flag names with their values, environment variable names, and a concrete config file example. Copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | The skill covers a relatively simple single-command tool, but the YouTube transcript workflow has a useful conditional (huge transcript → summarize first, then ask to expand). However, there's no validation or error handling guidance—e.g., what happens if the API key is missing, if the URL is unreachable, or if YouTube transcript extraction fails. | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines, the content is well-organized into clearly labeled sections (trigger phrases, quick start, YouTube specifics, model/keys, flags, config). No unnecessary nesting or external references needed. | 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
- trpc-group/trpc-agent-go
- Commit
09cce3e
- 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.