CtrlK
BlogDocsLog inGet started
Tessl Logo

minutes-video-review

Analyze a product walkthrough, bug report video, Loom, or ScreenPal using Minutes transcription plus visual review. Use when the user wants a recorded demo or bug clip turned into a durable brief with transcript, key frames, issues, and next steps.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The content is well-structured and actionable with executable commands and sensible progressive disclosure, but it is slightly repetitive and lacks an explicit validation/feedback checkpoint in its multi-step pipeline workflow.

Suggestions

Add an explicit verification checkpoint after Phase 1 (e.g., confirm the JSON output exists and check transcript_method / exit status before inspecting artifacts), with a retry-or-diagnose path for failed downloads or transcription.

De-duplicate the transcript-backend material: keep the ordering and method labels in references/dependencies.md and summarize once in the body rather than restating both the order and the label list.

Tighten 'Context discipline' by removing the restatement of the script's adaptive frame caps, leaving only the agent-side judgment guidance that the script does not already enforce.

DimensionReasoningScore

Conciseness

The body is mostly lean and avoids explaining known concepts, but repeats some material across sections — the transcript-backend order and method-label list duplicate dependency details, and 'Context discipline' partly restates the frame caps the script already enforces.

2 / 3

Actionability

Provides copy-paste-ready commands for both local and hosted video plus a complete options example (--focus, --cookies-from-browser, --env-file, --frame-step, --max-frames, --keep-temp), and concrete per-phase guidance with specific expected outputs.

3 / 3

Workflow Clarity

The three phases (run pipeline, inspect artifacts, produce brief) are clearly sequenced, but there is no explicit validation/verification checkpoint for a pipeline that can fail at download or transcription — the script prints JSON paths yet the documented workflow lacks a check-or-retry feedback loop.

2 / 3

Progressive Disclosure

SKILL.md is a clear overview with well-signaled, one-level-deep references (dependencies.md, output-schema.md) that both exist as real files, plus a single bundled script; detail is appropriately split out rather than inlined.

3 / 3

Total

10

/

12

Passed

Description

100%

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 is concise, third-person, and clearly answers both what the skill does and when to use it, with natural trigger terms and named tools. It is a strong, low-conflict description with no over-claims or fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (transcribe via Minutes, sample key frames, produce a brief with transcript, key frames, issues, and next steps) and names specific source types, matching the 'Lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly states what it does ('Analyze ... into a durable brief with transcript, key frames, issues, and next steps') and when to use it via a clear 'Use when the user wants a recorded demo or bug clip turned into a durable brief ...' clause.

3 / 3

Trigger Term Quality

Includes natural user terms plus named tools — 'product walkthrough', 'bug report video', 'Loom', 'ScreenPal', 'recorded demo', 'bug clip' — giving good coverage of phrases a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The Minutes-first video-review niche with named hosted-video tools (Loom, ScreenPal) is a clear, distinct trigger set unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
silverstein/minutes
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.