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

85%

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

82%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.

A well-structured, actionable skill body with clear phased workflow and real bundled references. Minor conciseness repetition, a missing artifact-validation checkpoint, and one dangling reference path keep it just below top marks.

Suggestions

Add an explicit validation checkpoint in Phase 2 (e.g. confirm analysis.md, transcript.md, and frames/ exist and are non-empty before drafting the brief, with a fallback if transcription failed).

Remove or fix the dangling reference to scripts/eval_video_review.py in references/dependencies.md — the file is not present in the bundle.

Tighten the opening: the intro paragraph and 'What this skill does' restate the frontmatter description; collapse them into a single concise framing.

DimensionReasoningScore

Conciseness

Mostly lean with executable commands and tight gotchas, but the intro and 'What this skill does' section restate the frontmatter description, and a few transitions could be trimmed.

4 / 5

Actionability

Copy-paste ready commands for local files, hosted URLs, and the full options example, all pointing at the real bundled script path with concrete flags.

5 / 5

Workflow Clarity

Phases 1-3 are clearly sequenced and the transcription fallback order acts as a resilience checkpoint, but there is no explicit validation that the bundle/artifacts are complete before producing the brief.

4 / 5

Progressive Disclosure

Body cleanly signals one-level-deep references to dependencies.md and output-schema.md (both real files), but dependencies.md references a non-existent scripts/eval_video_review.py, a minor bundle-integrity gap.

4 / 5

Total

17

/

20

Passed

Description

87%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 strong, third-person description that pairs concrete capabilities with an explicit 'Use when' trigger and branded source names. Minor specificity gaps around the download/audio-extraction mechanics keep it just short of perfect on action coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'Analyze... using Minutes transcription plus visual review' and 'durable brief with transcript, key frames, issues, and next steps' — but omits explicit download/audio-extraction steps, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (analyze via Minutes + visual review into a durable brief) and when via a concrete 'Use when the user wants a recorded demo or bug clip...' trigger clause.

5 / 5

Trigger Term Quality

Strong natural trigger coverage ('product walkthrough', 'bug report video', 'Loom', 'ScreenPal', 'recorded demo', 'bug clip'), though generic 'screen recording' phrasing and file extensions are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche — Minutes-first review of meeting-adjacent product/bug videos — with branded triggers (Loom, ScreenPal) that minimize overlap with generic video skills.

5 / 5

Total

18

/

20

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.