summarize
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).
82
Quality
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 effectively communicates core functionality around transcript extraction and summarization with good natural trigger terms. However, it lacks an explicit 'Use when...' clause and could be more specific about the types of files supported and output formats. The parenthetical fallback note is helpful but informal.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to transcribe, summarize, or extract text from videos, audio files, podcasts, or web content.'
Specify supported file types and formats more precisely (e.g., '.mp3, .mp4, .wav, YouTube links') to improve distinctiveness and reduce overlap with generic file processing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names domain (URLs, podcasts, local files) and some actions (summarize, extract text/transcripts), but lacks comprehensive detail about specific capabilities like format handling or output options. | 2 / 3 |
Completeness | Clearly answers 'what' (summarize/extract from various sources), but lacks an explicit 'Use when...' clause. The parenthetical hint about YouTube/video is helpful but doesn't constitute proper trigger guidance. | 2 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'summarize', 'extract text', 'transcripts', 'URLs', 'podcasts', 'YouTube', 'video', 'transcribe'. The parenthetical note adds valuable trigger terms. | 3 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to transcript/text extraction from media, but 'URLs' and 'local files' are broad enough to potentially 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 strong, well-crafted skill that efficiently documents a CLI tool. It excels at conciseness and actionability with copy-paste ready examples. The only minor weakness is the slightly ambiguous guidance around handling large YouTube transcripts, which could benefit from more explicit thresholds or decision criteria.
Suggestions
Clarify what constitutes a 'huge' transcript (e.g., '>10k tokens') and provide explicit guidance on how to ask the user about section/time range expansion
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what summarization is or how CLIs work. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides copy-paste ready commands for all common use cases. Concrete examples with real flags, clear environment variable names, and executable config JSON. | 3 / 3 |
Workflow Clarity | For a simple CLI wrapper this is mostly clear, but the YouTube transcript workflow has a decision point ('if huge, return summary first') without explicit guidance on what constitutes 'huge' or how to handle the follow-up. | 2 / 3 |
Progressive Disclosure | Well-organized sections that progress from quick start to specific use cases to configuration. For a skill under 50 lines with no need for external references, the structure is appropriate and easy to 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
- trpc-group/trpc-agent-go
- Commit
8763418
- 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.