Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →guaardvark/film-crew
Run Guaardvark's five-role Film Crew locally: screenwriter, casting (Cast Library LoRAs), cinematographer storyboards, keyframe renders, editor. Turns a logline or screenplay into a finished short video with human gates at casting and storyboard.
Passed 19 of 19 test cases with the skill, and 5 of 19 without it.
and 16 more in the full report
14 fixed5 passed either way0 still failing0 broke3 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
When constructing backend REST API calls for Guaardvark film productions without custom GUAARDVARK_URL environment settings, what is the default base URL protocol, host, and port used?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies http://localhost:5000 as the default base URL. | Missed | Passed |
The instructions your model reads when the skill loads.
Read setup first. Needs comfyui; casting with trained characters needs
lora_trainer (see the cast skill). Renders take minutes per shot.
start_film_crewscript_text: a screenplay or a plain scene list. A logline works; the screenwriter expands it.name (defaults to the first line), video_model (defaults to the active scene model,
minimax-h3-int8 on a typical box; wan22-5b for silent i2v).B=${GUAARDVARK_URL:-http://localhost:5000}, P = production id from the tool.
| stage | call | note |
|---|---|---|
| status | GET $B/api/production/$P | stage, subjects, shots, errors |
| subjects found by the writer | GET $B/api/production/$P/subjects | characters, environments, props |
| cast one subject | POST $B/api/production/$P/cast/<subject_id> with {"action": ...} | link to an existing Cast Library subject or plan a new one |
| confirm casting | POST $B/api/production/$P/casting/confirm | user gate: every subject needs a cast plan first |
| storyboard shot image | GET $B/api/production/$P/storyboard/shot/<shot_id>/image | review keyframes |
| redo one shot | POST $B/api/production/$P/storyboard/shot/<shot_id>/regenerate | |
| approve storyboard | POST $B/api/production/$P/storyboard/approve | user gate: releases the renders. A 409 with flagged_shots lists frames the curator flagged; show them, and resend with {"confirm_flagged": true} only if the user says to render them anyway |
| retry a failed stage | POST $B/api/production/$P/retry | |
| list / delete | GET $B/api/production, DELETE $B/api/production/$P |
Without the MCP tool: POST $B/api/production with {"name", "script_text", "settings": {"video_model": "..."}}.
test cases passed, vs 5 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.