SKILLEMALL.ai

BF influencer-event-vlog

Turn "film me at a match / concert / show" into a polished ~15s 16:9 influencer vlog — the skill co-creates the shot plan, locks the on-camera influencer, generates a storyboard / production-reference sheet, checks it, then renders the clip with native dialogue. How it works: 1. Asks a few questions and co-creates the 5-beat event-vlog arc from whatever the user gives 2. Locks the look first — generates and confirms the influencer (face / outfit / selfie pose) + a venue style frame 3. Generates the storyboard production-reference sheet (GPT Image 2) referencing those locked anchors 4. Checks the board, then writes a motion + camera-POV + dialogue prompt grounded in the ACTUAL board 5. Renders a 16:9 vlog that follows the panels shot by shot with native spoken lines + lip-sync (Seedance 2.0)

genspark Agent Skills author: Genspark 1 file body ≈ 4 269 tokens Open the sourcegenspark.ai analyzed 3 d ago

As a process F 38/100 · Will not run — References files that are not bundled: ../storyboard-to-short-video/SKILL.md

GeneratorMedia and videotype and topics are labelled automatically from the skill text
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
63
Run on models
none yet
Process rating
F
38/100
Will not run
References files that are not bundled: ../storyboard-to-short-video/SKILL.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: ../storyboard-to-short-video/SKILL.md

Process rating: all ten parameters 38/100

Will not run. References files that are not bundled: ../storyboard-to-short-video/SKILL.md
  • 0Tools and files. 1 referenced file(s) missing: ../storyboard-to-short-video/SKILL.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 12 mutating operations with no state check
  • 70Failures and branches. 5 branches
  • 70Execution cost. Instruction body is 4269 tokens
  • 100Steps. 40 steps
  • 100Consistency. Name and required fields are in place
  • 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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 802: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 40 items
  • +4Has examples (5 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.