summarize

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

3.44x

Quality

76%

Does it follow best practices?

Impact

100%

3.44x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./openclaw/skills/summarize/SKILL.md

Quality

Content

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 reference sections. Its main weakness is the lack of error handling or troubleshooting guidance for a tool that depends on external APIs and network connectivity. Overall it's a strong skill that efficiently communicates how to use the summarize CLI.

Suggestions

Add a brief troubleshooting or error handling note (e.g., what to do if API key is missing, URL is unreachable, or the command returns an error) to improve workflow clarity.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It doesn't explain what URLs, PDFs, or YouTube are. Every section serves a purpose—trigger phrases, quick start commands, flags, and config. No unnecessary padding or explanations of concepts Claude already knows.	3 / 3
Actionability	Provides fully executable, copy-paste ready bash commands for all major use cases. Flags are listed concisely with their options, environment variable names are specific, and the config file example is concrete JSON.	3 / 3
Workflow Clarity	The skill covers a relatively simple CLI tool, but the guidance for handling large transcripts ('return a tight summary first, then ask which section/time range to expand') is a nice workflow touch. However, there's no error handling guidance—what if the command fails, the API key is missing, or the URL is inaccessible. For a CLI tool that depends on external APIs and network access, some validation/error recovery guidance would strengthen this.	2 / 3
Progressive Disclosure	For a skill under 50 lines with no need for external references, the content is well-organized into clear sections (trigger phrases, quick start, YouTube specifics, model/keys, flags, config). The structure is logical and easy to navigate without needing separate files.	3 / 3
	Total	11 / 12 Passed

Description

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 users would use (transcribe, YouTube, podcasts, summarize), but lacks an explicit 'Use when...' clause which limits its completeness score. It's moderately specific about capabilities but could benefit from more concrete action listing and clearer trigger guidance to distinguish it from general web scraping or file summarization skills.

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 audio/video files.'

List more specific concrete actions to improve specificity, e.g., 'Summarizes web pages, extracts transcripts from podcasts and YouTube videos, processes local audio/video files for text extraction.'

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 formal trigger guidance. Per rubric, missing 'Use when...' caps completeness 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 and the parenthetical adds a useful fallback trigger.	3 / 3
Distinctiveness Conflict Risk	The combination of URLs, podcasts, and transcripts gives it some distinctiveness, but 'extract text from URLs' and 'summarize local files' could overlap with general web scraping or file processing skills. The YouTube/video fallback note helps but doesn't fully eliminate conflict risk.	2 / 3
	Total	9 / 12 Passed

Validation

72%

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 — 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: fc01b4b

Reviewed: 3 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.