BC ai-short-video-factory
AI Short Video Factory creates MP4 videos from HTML using HyperFrames. Use for captioned talking-head edits, product launches, data visualizations, code walkthroughs, social clips, GSAP animations, transitions, audio muxing, and deterministic rendering.
AI Short Video Factory creates MP4 videos from HTML using HyperFrames.
As a process C 60/100 · Has gaps — weak spots: result and completion, execution cost, progress reporting
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Dangerous commands
cmd-privilegeSKILL.md:119Privilege escalation / world-writable permissions (detector / deny-list definition; documentation table row)| `EACCES` permission error | npx cache permission issue | `sudo chown -R $(whoami) ~/.npm` |
detectortable
Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 253 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
body-longSKILL.md body ≈ 17856 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "agent_created" - note
frontmatter-keyunknown frontmatter key "description_zh"
Process rating: all ten parameters 60/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 10Execution cost. Instruction body is 17856 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, python, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 183 steps, 3 vague phrases
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 30 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (7 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -249 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 253: enough signal without eating the budget
- +4Structure: 139 headings
- +3Step-by-step instructions: 183 items
- +4Has examples (68 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.