Skill

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.

○ declared by the publisher, as-is
Safety
FF: 3 or more highs, or any critical25 severity-bearing · 1 informational
Reliability & Quality
B0 findings
Cost
n/anot assessed
Popularity
6286Forks
Performance tested for◌ not assessed
no controlled task evaluation on this release
Repo★ 69.4k ○6.3k forks181 watchers395 open issueslast commit 0d old when scanned
· context signals ↓
Vettd Note

No Vettd note yet for this asset.

Best for

Not for

Re-assessed 3d ago · 6 of 7 categories assessed
Record lookup
$ vettd directory view 5410f505-89fc-42bb-b77a-38d35bce7ff4

◌ Vettd does not install assets; this record describes a copy you obtain yourself.

Custody chainSource ↗○ linked, not verified by Vettd
heygen-com ◐heygen-com/hyperframes ○version = 388011b ◐ sha256:01e3…ad84 ◐ signature △ not assessedApache-2.0 ○record 5410f505-89fc-42bb-b77a-38d35bce7ff4 · live
◌ public recordYou are signed out, so you see the record and nothing else. sign in
Evidence · 6 of 7 categories · 51 signals · 23 soft spots
Where the record is weakest: 23 soft spots

Ranked worst first.

1Shell execution without sandboxingCriticalSafety · critical · VTD-0018

Detected in scripts/assemble-index.mjs:54 — `import { spawnSync } from "node:child_process";`

2Shell execution without sandboxingCriticalSafety · critical · VTD-0018

Detected in scripts/assemble-index.test.mjs:5 — `import { spawnSync } from "node:child_process";`

3Shell execution without sandboxingCriticalSafety · critical · VTD-0018

Detected in scripts/audio.mjs:25 — `import { spawnSync } from "node:child_process";`

Ranked 4–23: Shell execution without sandboxing, Shell execution without sandboxing, Shell execution without sandboxing, Shell execution without sandboxing, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, INJECTION ATTACK detected by YARA, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution
The soft spots and their evidence are identical when you are signed in.sign in
Safety● gradedFmost recent 3d ago29 signals · 23 soft spotsrecord 5410f505-89fc-42bb-b77a-38d35bce7ff4
how it was established29 signals · 2 sources · scan
vettd directory view 5410f505-89fc-42bb-b77a-38d35bce7ff4 --json
show
Shell execution without sandboxingflaggedsoft spot 1Detected in scripts/assemble-index.mjs:54 — `import { spawnSync } from "node:child_process";`vettd · scan · 3dCritical
Shell execution without sandboxingflaggedsoft spot 2Detected in scripts/assemble-index.test.mjs:5 — `import { spawnSync } from "node:child_process";`vettd · scan · 3dCritical
Shell execution without sandboxingflaggedsoft spot 3Detected in scripts/audio.mjs:25 — `import { spawnSync } from "node:child_process";`vettd · scan · 3dCritical
Shell execution without sandboxingflaggedsoft spot 4Detected in scripts/captions.test.mjs:2 — `import { execFileSync } from "node:child_process";`vettd · scan · 3dCritical
Shell execution without sandboxingflaggedsoft spot 5Detected in scripts/fetch-pr.mjs:28 — `import { execFileSync } from "node:child_process";`vettd · scan · 3dCritical
Shell execution without sandboxingflaggedsoft spot 6Detected in scripts/frame-contract.test.mjs:2 — `import { execFileSync } from "node:child_process";`vettd · scan · 3dCritical
Shell execution without sandboxingflaggedsoft spot 7Detected in scripts/preflight.mjs:3 — `import { spawnSync } from "node:child_process";`vettd · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 8scripts/assemble-index.mjs:54 — Pattern detected: from "node:child_process"cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 9scripts/assemble-index.mjs:85 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 10scripts/assemble-index.mjs:101 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 11scripts/assemble-index.test.mjs:5 — Pattern detected: from "node:child_process"cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 12scripts/assemble-index.test.mjs:10 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 13scripts/assemble-index.test.mjs:11 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 14scripts/assemble-index.test.mjs:35 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 15scripts/assemble-index.test.mjs:97 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 16scripts/assemble-index.test.mjs:123 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 17scripts/audio.mjs:25 — Pattern detected: from "node:child_process"cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 18scripts/audio.mjs:88 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 19scripts/captions.test.mjs:2 — Pattern detected: from "node:child_process"cisco · scan · 3dCritical
INJECTION ATTACK detected by YARAflaggedsoft spot 20scripts/captions.test.mjs:226 — Script injection patterns: onerror="alert(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 21scripts/fetch-pr.mjs:28 — Pattern detected: from "node:child_process"cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 22scripts/frame-contract.test.mjs:2 — Pattern detected: from "node:child_process"cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 23scripts/preflight.mjs:3 — Pattern detected: from "node:child_process"cisco · scan · 3dCritical
Outbound network request primitives in JavaScript/TypeScriptflaggedscripts/fetch-people-avatars.mjs:114 — Pattern detected: fetch(cisco · scan · 3dMedium
Script contacts a destination the documentation never mentionsflaggedscripts/assemble-index.mjs:587 — Script contacts or configures 'cdn.jsdelivr.net' but the skill documentation never visibly mentions it. Undocumented network destinations can indicate behaviour the manifest and description do not disclose.cisco · scan · 3dLow
Skill does not specify a licenseflaggedSKILL.md — Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms.cisco · scan · 3dInfo
behavioral scan passednothing foundNo prompt-injection or jailbreak signals were detected.vettd · scan · 3dnothing found
External URL scan passednothing foundNo external URLs were found in scanned skill text.vettd · scan · 3dnothing found
Name validation passednothing foundThe declared skill name follows the supported naming rules.vettd · scan · 3dnothing found
Reliability & Quality● gradedBmost recent 3d ago7 signalsrecord 5410f505-89fc-42bb-b77a-38d35bce7ff4
how it was established7 signals · vettd · scan
vettd directory view 5410f505-89fc-42bb-b77a-38d35bce7ff4 --json
show
Unresolvable internal referencesflaggedUnresolvable internal path(s): audio/references/tts.md, audio/scripts/heygen-tts.mjs, references/intent-interview.md, references/setup-providers.md, scripts/prefs.mjs, scripts/recipe.mjsvettd · scan · 3dMedium
Checklist patternreadvettd · scan · 3dabsent
Description usage contextreadvettd · scan · 3dabsent
Examplesreadvettd · scan · 3dpresent
Gotchas sectionreadvettd · scan · 3dabsent
Step-by-step workflowreadvettd · scan · 3dabsent
Validation loopreadvettd · scan · 3dpresent
Performance● measured1 measuredmost recent 3d ago2 signalsrecord 5410f505-89fc-42bb-b77a-38d35bce7ff4
how it was establishedtiktoken/cl100k_base/skill-md-body · 2 signals · vettd · scan
vettd directory view 5410f505-89fc-42bb-b77a-38d35bce7ff4 --json
show
Progressive disclosurereadvettd · scan · 3dpresent
Static context tokensmeasuredvettd · scan · 3d7576
Cost◌ not assessednot assessed0 signalsrecord 5410f505-89fc-42bb-b77a-38d35bce7ff4
how it was establishednot assessed; no producer has emitted into this category
vettd directory view 5410f505-89fc-42bb-b77a-38d35bce7ff4 --json
Not assessed; no producer has emitted into cost for this asset. That is different from a check that ran and found nothing, which the record would carry as a row of its own.
Compatibility◌ unjudgednot judgedmost recent 3d ago4 signalsrecord 5410f505-89fc-42bb-b77a-38d35bce7ff4
how it was established4 signals · vettd · scan
vettd directory view 5410f505-89fc-42bb-b77a-38d35bce7ff4 --json
show
CLI helpreadvettd · scan · 3dpresent
Declared environment assumptionsreadvettd · scan · 3d
Declared skill namereadvettd · scan · 3dpr-to-video
Structured outputreadvettd · scan · 3dpresent
Popularity◇ context onlynot judgedmost recent today5 signalsrecord 5410f505-89fc-42bb-b77a-38d35bce7ff4
how it was establishedgithub-repo-object · 5 signals · github-api · research
vettd directory view 5410f505-89fc-42bb-b77a-38d35bce7ff4 --json
show
Forksmeasuredgithub-api · research · today6286
Days since last commitmeasuredgithub-api · research · today0 days
Open issuesmeasuredgithub-api · research · today395
Starsmeasuredgithub-api · research · today69352
Watchersmeasuredgithub-api · research · today181
Characteristics◇ context onlynot judgedmost recent today4 signalsrecord 5410f505-89fc-42bb-b77a-38d35bce7ff4
how it was establishedbundle-extension-share · 4 signals · 2 sources · research/scan
vettd directory view 5410f505-89fc-42bb-b77a-38d35bce7ff4 --json
show
Declared licensereadvettd · scan · 3d
Primary bundle languageobservedvettd · scan · 3d · conf mediumJavaScript
Repository linkreadvettd · scan · 3dabsent
Archivedreadgithub-api · research · todayfalse
Coverage6 of 7 categories assessed · shown
Safety
✓ assessed
behavioral scan passed · External URL scan passed · Name validation passed
Reliability & Quality
✓ assessed
7 signals recorded
Performance
✓ assessed
2 signals recorded
Cost
△ not assessed
no producer has emitted for this category
Compatibility
✓ assessed
4 signals recorded
Popularity
✓ assessed
5 signals recorded
Characteristics
✓ assessed
4 signals recorded
Freshness & re-evaluation
assessed3d ago · Cisco AI Defense · Vettd core● unreachable
source stateThe tracked branch no longer exists.Unreachable
re-check policysource unreachable: re-probed on the scheduler's cadence until it answersnext check in 6d
re-run whena new release ships, the upstream source changes, or the scanner ruleset is revisedauto-scheduled
Limitations & open conflicts
limitationCost is not assessed: behaviour there is unmeasured, not clean△ gap
conflictno two sources report the same quantity on this record
Verify: does this record describe your copy?
What record 5410f505-89fc-42bb-b77a-38d35bce7ff4 covers
scannerv11● current
validityassessed 3d ago · Unreachable
$ vettd scan folder <path>
this record was taken at digest sha256:01e34d507b8c… compare it against the digest your own scan prints
Reproduce: re-run the evidence yourself
$ vettd scan folder /path/to/your/copy
runs the same scanners against your own copy; the published record is never overwritten
How this record comparesagainst other published records · full comparison →
Signal kinds
▲ finding: something to act on, carries a severity● measurement: a reproducible quantityƒ estimate: inferred from a sample▪ fact: read directly off the artifact◆ classification: assigned from a taxonomy◌ nothing found: a producer looked and emitted no object◇ context only: described, never graded
Custody marks
◐ computed by vettd○ declared by the publisher, as-is△ not assessed: nothing looked
$ vettd directory view 5410f505-89fc-42bb-b77a-38d35bce7ff4 --jsonas JSON ↗