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.

69

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, highly actionable skill body with copy-paste commands, a clear phased workflow, and appropriate offloading of detail to reference files. Main improvements are adding an explicit failure/validation checkpoint and deduplicating the transcript-backend ordering.

Suggestions

Add an explicit validation/error-recovery step in Phase 1 (e.g., 'if the script exits non-zero or transcript_method is empty, fall back to the next backend per the preferred order') to raise workflow clarity.

De-duplicate the transcript backend preference list between the body's 'Minutes-first transcription rules' and dependencies.md by keeping the canonical ordered list in dependencies.md and briefly referencing it from the body.

Link output-schema.md from the 'Output contract' section (where its fields are most useful) in addition to the Dependencies section, so the reference is discoverable at the point of need.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence, but the 'Minutes-first transcription rules' preferred-order list duplicates content also in dependencies.md, and a few sections could be tightened.

4 / 5

Actionability

Fully executable copy-paste-ready bash commands with real plugin-root paths and a useful-options block covering common cases (focus, cookies, env-file, frame-step, max-frames, keep-temp).

5 / 5

Workflow Clarity

Clear three-phase sequence (run pipeline, inspect artifacts, produce brief) with named outputs, but lacks an explicit validation/error-recovery checkpoint if the script or transcription fails.

4 / 5

Progressive Disclosure

Good structure with one-level-deep references to real files (dependencies.md, output-schema.md) signaled via plugin-root paths, though output-schema.md is linked only under Dependencies rather than near the Output contract where it is most relevant.

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 description that clearly states what the skill does and when to invoke it, using third-person voice with concrete natural trigger terms including specific platform brands. Minor room to expand enumerated actions and add a few more generic synonyms.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Minutes transcription plus visual review', 'durable brief with transcript, key frames, issues, and next steps'), with only minor gaps in action coverage versus the comprehensive 5-anchor.

4 / 5

Completeness

Explicitly answers both what ('Analyze a product walkthrough... using Minutes transcription plus visual review') and when ('Use when the user wants a recorded demo or bug clip turned into a durable brief...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms users say ('product walkthrough', 'bug report video', 'Loom', 'ScreenPal', 'recorded demo', 'bug clip') with brand synonyms, but misses a few common variants like generic 'screen recording'.

4 / 5

Distinctiveness Conflict Risk

Clear niche (meeting-adjacent product artifact review via Minutes transcription + visual review) with distinct triggers (Loom, ScreenPal, bug clip, product walkthrough) and minimal overlap risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.