CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

make-video-ads

Use when the marketer says: make me a video ad, a 30-second ad for paid social, a Reel / TikTok / Shorts ad, a UGC-style video made with AI (no real creator), a product demo video, remake this ad I like for my brand, cut our best organic video into an ad, more like my winning video with new hooks, my video ad got rejected — fix it. Delivers a produced, ready-to-post video ad grounded in a researched angle: one message, a hook for the first two seconds, every claim traced to the brand's signed-off claims, no generated person posing as a customer, the exact words and the price approved before anything renders (one video, or one plus two hook variants), an honest review of the result, priced fixes only on a yes, and launch copy and notes for the ads team. Works in chat apps. Never publishes or spends ad budget. Not for real creators filming for you — work-with-creators (unsure? ask: AI-made or a real person); not for a phone-shot organic post — run-organic-social; not for static ads — make-static-ads.

Quality

98%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

96%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly operational playbook: fully executable tool-level guidance, an 11-step sequence with explicit approval gates and human-confirmation feedback loops, and disciplined offloading of detail to references — with no token spent teaching Claude things it already knows. The only structural weakness is bundle hygiene: one orphaned reference file and atom paths that don't resolve inside the bundle as shipped.

Suggestions

Reference references/excellent-script-example.md from the script step (Step 5 / script-craft.md) or remove it from the bundle — as shipped it is orphaned and cannot be discovered through navigation.

Make the atoms/ paths resolvable or annotate where they live (e.g. a one-line note that atoms are shared across the marketing skills), since atoms/write-script/ATOM.md and its siblings do not exist inside this bundle.

Consider a short 'Bundle map' line at the top (one line per references/ file) so the reference set, including currently unreferenced files, is visible at a glance.

DimensionReasoningScore

Conciseness

The body is relentlessly operational — tool calls, file paths, gate conditions, exact sentences to say — with zero explanation of concepts Claude already knows (no 'what a video ad is', no library or platform primers). Every clause carries domain-specific information Claude could not infer (e.g. 'expect candidates_too_similar if two say the same thing', 'budget_exceeded → stop and ask'), matching the 5 anchor 'every token earns its place'; a 4 would require over-explanation that could be trimmed, which is absent.

5 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact tool calls with parameters ('gooseworks:video_batch more_like (change: "hook", free)', 'video_read (include: ["renders","recipe","scenes"])'), exact phrasing for the human ('Connect GooseWorks first — I make your video ads through it'), file paths ('ads/videos/<project_id>.md'), and error branches ('budget_exceeded → stop and ask'). This matches the 5 anchor 'copy-paste ready… specific examples cover the common cases' — chat vs shell hosts, batches, and rejection fixes are all covered.

5 / 5

Workflow Clarity

Steps 1–11 are clearly sequenced with explicit validation checkpoints and feedback loops: script-check atoms run on every candidate 'before saving', the gate ('show it, price it, wait') blocks rendering until video_approve records the marketer's exact words, Step 8's honest review labels findings 'please confirm' with 'Two rounds at most', and budget_exceeded halts production. This matches the 5 anchor (explicit validation, error-recovery loops, checklists for complex processes); spend-bearing operations all pass through gates, so no cap applies.

5 / 5

Progressive Disclosure

Structure is good: per-step load signals ('Load references/reading-the-brain.md', 'references/paths-and-gates.md §3') point to one-level-deep files that all exist, keeping the overview lean. Two minor gaps keep it from the 5 anchor: references/excellent-script-example.md is present in the bundle but referenced nowhere in SKILL.md or the other reference files (orphaned, undiscoverable), and the four atoms/*/ATOM.md paths do not resolve within this bundle. This fits the 4 anchor ('most content appropriately placed; references mostly clear; minor organization gaps') better than 5, and is well above 3 ('references present but not clearly signaled').

4 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: explicit 'Use when' triggers in the user's natural words with synonyms, a concrete statement of deliverables and constraints, and explicit negative routing to sibling skills. Its only weakness is density — it runs roughly three times the length of typical good examples, though every clause is functional rather than padded.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions and deliverables — 'Delivers a produced, ready-to-post video ad', 'cut our best organic video into an ad', 'remake this ad I like for my brand', 'priced fixes only on a yes', 'launch copy and notes for the ads team' — covering make, remake, cut-down, hook variants, rejection fixes, review, and launch copy. This matches the 5 anchor ('multiple specific concrete actions; comprehensive coverage'); a 4 would require minor coverage gaps, and none are evident.

5 / 5

Completeness

Both halves are explicit: 'Use when the marketer says: …' gives concrete trigger phrases for when, and 'Delivers a produced, ready-to-post video ad grounded in a researched angle: one message, a hook for the first two seconds, … and launch copy and notes for the ads team' states what. This is exactly the 5 anchor ('clearly and explicitly answers both what AND when with concrete trigger phrases'), not the 4 anchor where the 'when' could be more explicit.

5 / 5

Trigger Term Quality

Trigger phrases are the natural words a marketer would say, with synonyms and platform names: 'make me a video ad', 'a 30-second ad for paid social', 'a Reel / TikTok / Shorts ad', 'a UGC-style video made with AI', 'a product demo video', 'my video ad got rejected — fix it'. Coverage is comprehensive with variations, matching the 5 anchor; a 4 ('a few natural terms missing') would understate the synonym coverage.

5 / 5

Distinctiveness Conflict Risk

The niche is clear and wrong-skill triggers are explicitly routed away: 'Not for real creators filming for you — work-with-creators (unsure? ask: AI-made or a real person); not for a phone-shot organic post — run-organic-social; not for static ads — make-static-ads.' With distinct triggers and named sibling disambiguation, conflict risk is minimal (5 anchor); a 4 would require unresolved overlap with closely related skills, which the exclusions resolve.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

gooseworks-ai/goose-skills

Path

drafts/marketing/make-video-ads/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.