BC pexoai-agent
Create professional short videos (5–60 seconds) for TikTok, Instagram Reels, YouTube Shorts, and brand ads using AI. Use when the user wants to: make a video, create a TikTok, produce a product ad, generate a promo clip, make UGC content, create social media videos, or any video creation task. Supports product videos, lifestyle content, explainer clips, and more — with automatic scriptwriting, shot composition, transitions, and music. Also handles video revision requests. Pexo outputs 16:9, 9:16 (vertical), or 1:1 aspect ratios.
As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- 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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Create professional short videos (5–60 seconds) for TikTok, Instag… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "repository" - note
frontmatter-keyunknown frontmatter key "requires"
Process rating: all ten parameters 52/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 7 mutating operations with no state check
- 40Consistency. Frontmatter name (pexoai-agent) differs from the folder (pexoai-agent-madu)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 20 steps
- 100Execution cost. Instruction body is 1049 tokens
- 100Progress reporting. Reports progress
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 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
- -31 of 6 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 534: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (10 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.