CtrlK
BlogDocsLog inGet started
Tessl Logo

summarize

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

87

3.44x
Quality

83%

Does it follow best practices?

Impact

100%

3.44x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is summarize in Hung-Reo/hungreo-openclaw

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is exemplary for a single-purpose CLI skill: lean, copy-paste executable, well-sectioned, and covering the common cases including the nuanced summary-vs-transcript decision. There is no verbosity to trim, no concept over-explanation, and no content that should be moved to separate bundle files.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: no concept explanations, just a trigger list, copy-paste commands, env vars, flags, and a config snippet. Every line is actionable and there is no padding to trim — fits the 'lean and efficient' anchor exactly.

5 / 5

Actionability

Quick start gives fully executable commands for the common cases (URL, local PDF, YouTube summary, best-effort transcript via --extract-only), with concrete env var names, a default model, and exact flag syntax (e.g. "--length short|medium|long|xl|xxl|<chars>"). Copy-paste ready with no gaps.

5 / 5

Workflow Clarity

This is a simple single-purpose skill where the single action is unambiguous (pick provider/model → set key → run one command), so the simple-skill exception applies. It even includes an explicit decision checkpoint: "If the user asked for a transcript but it's huge, return a tight summary first, then ask which section/time range to expand." Operations are read-only, so no destructive-validation cap applies.

5 / 5

Progressive Disclosure

A compact (~63 line), well-sectioned body with clear headers (When to use, Quick start, YouTube, Model + keys, Useful flags, Config) and no nested or buried references. Nothing here warrants splitting into bundle files, so inline organization is the right structure.

5 / 5

Total

20

/

20

Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, appropriately concise description with good natural trigger phrasing and a distinct YouTube/podcast transcription niche. Its main weakness is completeness: the 'when to use' guidance is only weakly implied by a parenthetical fallback note rather than an explicit 'Use when...' clause, and coverage of natural trigger synonyms (article, link, file extensions) has gaps.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to summarize a link, article, or video, asks 'what's this about?', or wants a YouTube/podcast transcript without yt-dlp."

Include common synonyms and file types users would naturally mention: "article", "link", ".pdf", ".mp3", "transcript" — to lift trigger-term coverage toward comprehensive.

Move the transcript-extraction capability out of the parenthetical into the main clause (e.g. "...and best-effort YouTube transcript extraction with no yt-dlp required") so the 'what' covers the skill's differentiator.

DimensionReasoningScore

Specificity

"Summarize or extract text/transcripts from URLs, podcasts, and local files" lists several specific actions (summarize, extract text, extract transcripts) across three concrete source types. Not a 5 because coverage of capabilities is incomplete (no mention of JSON output, length control, or fallback extraction services); not a 3 because it goes beyond 1-2 generic actions with granular input coverage.

4 / 5

Completeness

The 'what' is clear (summarize/extract text and transcripts from URLs, podcasts, local files), but the 'when' is only weakly implied by the parenthetical "great fallback for 'transcribe this YouTube/video'" — there is no explicit 'Use when...' clause covering general trigger scenarios. Per the guideline, a missing or weakly-implied 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural phrases users would say — "summarize", "transcribe this YouTube/video", "podcasts", "URLs", "text/transcripts". Not a 5 because common variations are missing: "article", "link", "summarize this", and file extensions like .pdf or .mp3.

4 / 5

Distinctiveness Conflict Risk

The YouTube/podcast transcription niche ("great fallback for 'transcribe this YouTube/video'") is a fairly distinct trigger with minimal conflict. Not a 5 because generic URL summarization could overlap with other summarization skills; not a 3 because the transcription-fallback framing gives it a clear niche.

4 / 5

Total

15

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

13

/

16

Passed

Repository
trpc-group/trpc-agent-go
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.