AB happyhorse-1-0
HappyHorse 1.0 — text-to-video generation on RunComfy. HappyHorse 1.0 is currently #1 on Artificial Analysis Video Arena and produces native 1080p video with in-pass synchronized audio (dialogue, ambient, Foley) and multi-shot character consistency. This skill calls HappyHorse 1.0 through the RunComfy CLI: `runcomfy run happyhorse/happyhorse-1-0/text-to-video`. Triggers on "happyhorse", "happy horse", "happyhorse 1.0", "happyhorse video", "happyhorse t2v", or any explicit ask to generate video with HappyHorse.
HappyHorse 1.0 — text-to-video generation on RunComfy. HappyHorse 1.0 is currently 1 on Artificial Analysis Video Arena and produces native 1080p video with…
As a process B 67/100 · Nearly there — weak spots: result and completion, running it twice, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 0
✓ No critical or high findings
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "emoji" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "clawdis"
Process rating: all ten parameters 67/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 29 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3280 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 515: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (6 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.