CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-to-video

Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 skill body is a highly actionable, clearly sequenced workflow with per-step gates, concrete scripts, and well-structured one-level-deep references. Its weaknesses are verbosity in several qualifying sentences and one broken local reference (sub-agents/frame-worker.md).

Suggestions

Resolve or remove the missing `sub-agents/frame-worker.md` reference — the file is cited in Step 5 and the Quick Reference table but no `sub-agents/` directory exists, which breaks a signaled one-level-deep reference.

Tighten the densest paragraphs (Step 0 opening rule, Step 3 review-loop, Step 4 catalog-search) by splitting stacked parenthetical exceptions into short separate lines or a small list, cutting tokens without losing the gates.

Consider lifting the per-step **Gate:** lines into a compact checklist near the top so the gate sequence is scannable without reading each step.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence on the domain, but it is markedly verbose — many sentences are heavily qualified with parenthetical exceptions and inline rationale (e.g. the Step 3 review-loop paragraph and the Step 0 opening-rule sentence run long with stacked clarifications), so it sits between efficient and mostly-efficient with notable tightening possible.

3 / 5

Actionability

Every step supplies concrete, executable commands — exact `node <SKILL_DIR>/scripts/*.mjs ...` invocations with flags, `npx hyperframes` calls, and `gh api` snippets covering the common cases — so guidance is copy-paste ready and specific.

5 / 5

Workflow Clarity

The process is a clearly numbered Step 0→6 sequence with an explicit **Gate** at the end of every step, user-gated steps called out, error/feedback handling (re-dispatch that one frame only, one retry max; surface stderr and stop; fix cheapest safe edit then rerun), and the known-false-positive guidance for `check`, hitting the explicit-validation + feedback-loop anchor.

5 / 5

Progressive Disclosure

Structure is strong: an overview SKILL.md with a 'Quick Reference' Read-table mapping each reference to its step, local references and scripts one level deep, and design/motion rules correctly deferred to sibling-skill files; it is not a 5 because one referenced local file — `sub-agents/frame-worker.md` (cited in Step 5 and the Read table) — does not exist, so a signaled reference is broken.

4 / 5

Total

17

/

20

Passed

Description

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

The description is highly specific and distinct, naming concrete input forms, output video types, and explicit boundaries against sibling skills. The main gap is a missing single explicit 'Use when...' trigger clause; the when-guidance is conveyed via contrast and a fallback redirect rather than direct trigger phrasing.

Suggestions

Add one explicit 'Use when...' sentence naming the natural trigger phrases (e.g. 'Use when the user wants a video explainer of a pull request, PR review walkthrough, or changelog-from-diff video').

Include a few more natural synonyms users actually say — 'PR video', 'turn this PR into a video', 'summarize my PR on video' — alongside the current domain terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions grounded in real inputs/outputs — 'ingest a GitHub pull request', 'understand the change', 'plan a code-change explainer', 'build it frame by frame in HyperFrames' — plus concrete input forms (URL, owner/repo#N, 'this PR') and output video types (changelog, feature reveal, fix, refactor walkthrough), matching the comprehensive-coverage anchor.

5 / 5

Completeness

It clearly answers 'what' (turns a PR into a code-change explainer video built from the diff/commits/files) and supplies concrete when-trigger phrases, but the 'when' is conveyed via contrast and a redirect ('Not a product promo... Unclear → /hyperframes') rather than a single explicit 'Use when...' clause naming the triggers, so it does not fully hit the score-5 concrete-trigger-phrase bar.

4 / 5

Trigger Term Quality

Strong natural trigger coverage — 'GitHub pull request', 'PR URL', 'code-change explainer video', 'changelog', 'feature reveal', 'fix', 'refactor walkthrough' — but it leans on product/domain phrasing rather than the full spread of synonyms a user might say (e.g. 'PR video', 'summarize my PR'); a few natural variations are missing.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — a GitHub PR (a code change) turned into an explainer video — and explicitly disambiguates from adjacent skills ('Not a product promo /product-launch-video or a no-PR topic explainer /faceless-explainer. Unclear → /hyperframes'), giving distinct triggers with minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing, 11 suspicious

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository
heygen-com/hyperframes
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.