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.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

An exceptionally well-structured orchestrator body: concise, fully actionable, and rigorously gated with validation feedback loops. Progressive disclosure is strong but slightly undermined by references to sibling-skill trees not shipped in this bundle.

Suggestions

For standalone review, note which sibling-tree references (../hyperframes-core, ../hyperframes-animation, ../hyperframes-creative, ../media-use) are external dependencies vs. bundled, so reviewers can confirm reachability.

Add the referenced sub-agents/frame-worker.md to the bundle (or clarify it is provided at runtime by the packet builder) since the Read/When table cites it.

Consider a one-line legend explaining the ../<skill>/ reference convention so the one-level-deep navigation is unambiguous outside the full plugin tree.

Dimension	Reasoning	Score
Conciseness	Lean and directive throughout — no tutorial padding about what a PR or diff is, and every sentence is instructional and earns its place assuming Claude's competence.	5 / 5
Actionability	Provides fully executable, copy-paste-ready bash/npx commands with flags, named script invocations, exact output paths, and concrete failure-handling instructions covering the common cases.	5 / 5
Workflow Clarity	A clearly sequenced Step 0→6 workflow with an explicit Gate checkpoint per step, review-loop validate→fix→retry feedback, bounded retries, and stop-on-failure discipline for the render operation.	5 / 5
Progressive Disclosure	Excellent overview structure with a well-signaled one-level-deep Read/When table, and all locally-cited references/ files exist; however several cited references resolve to sibling skill trees (../hyperframes-core, ../hyperframes-animation, ../hyperframes-creative, ../media-use, ../hyperframes) and sub-agents/frame-worker.md that are not present in this bundle.	4 / 5
	Total	19 / 20 Passed

Description

92%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, specific, third-person description that states concrete actions, explicit trigger guidance, and clear disambiguation from neighboring skills. Only minor room to add lay synonyms for trigger terms.

Suggestions

Add one or two lay synonyms (e.g. "code review video") alongside the technical PR terms to broaden natural trigger coverage.

Consider trimming the parenthetical input-form list slightly; the core trigger phrasing already carries the meaning.

Dimension	Reasoning	Score
Specificity	Names multiple concrete outputs ("changelog, feature reveal, fix, or refactor walkthrough") and concrete sources ("diff, commits, and files"), giving comprehensive coverage of the actions performed.	5 / 5
Completeness	Explicitly answers both what (a code-change explainer video with four walkthrough types) and when to use it, reinforced by explicit conflict routing ("Not a product promo", "Unclear → /hyperframes") and the "code change, not a website" trigger.	5 / 5
Trigger Term Quality	Includes natural terms users would say ("GitHub pull request", "PR URL", "diff", "owner/repo#N") plus the concrete input forms, but leans technical and omits a few lay synonyms like "code review video".	4 / 5
Distinctiveness Conflict Risk	Highly distinct niche with explicit disambiguation against sibling skills (/product-launch-video, /faceless-explainer) and a clear input boundary, minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: skills/pr-to-video/SKILL.md
Commit: a562946

Reviewed: about 11 hours ago

Table of Contents

Discovery Implementation Validation

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.