extract-source-sample

Given the path to a finished content-goose ad-run folder, extract everything that defines that ad — recipe shot list, VO script, characters, voices, world, atom-skills, master mp4 — and emit a `source-sample.json` in the exact shape the `upload-ad-sample` skill writes to the Goose Ads library. Also links every character and voice to the central character library at `<repo-root>/assets/character-library/` (repo-root derived from the run-dir, not a hardcoded path), and if a character isn't in the library yet, adds it first then links. Use when the user wants to remix one of their existing ads — this skill produces the source JSON that the script-rewriting step and `remix-ad` consume.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%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.

Highly actionable and well-sequenced content with strong validation feedback loops, undermined by noticeable verbosity and a missed progressive-disclosure opportunity: the bundled schema reference is duplicated inline rather than linked.

Suggestions

Replace the inlined JSON schema in the body with a one-line pointer to references/source-sample-schema.md to eliminate duplication and make the bundle file discoverable.

Trim anecdotal retro notes (e.g. 'Hume run-03 lost ~$3 + 25 min') and remove internal [[feedback_...]] memory wiki-links that do not belong in a distributable SKILL.md.

Move the formatProfile known-slugs table and the library index/character.json schemas into the reference file, keeping only the routing rules inline.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and dense with actionable specifics, but includes trimmable anecdotal padding (e.g. 'Hume run-03 lost ~$3 + 25 min'), internal [[feedback_...]] memory wiki-links, and retro 'Origin' notes on the slug table that could be tightened.	3 / 5
Actionability	Fully executable guidance: exact JSON shapes, concrete file paths, runnable commands ('git lfs fetch --include=<relative path>'), a filename-to-role mapping table, and an explicit atom-derivation cascade covering common cases.	5 / 5
Workflow Clarity	Clear four-step sequence (read → build → link → write) with explicit validation (file audit, LFS materialization), feedback loops (404 → leave pointer; no match → extend library; null → surface), a failure-modes section, and a summary checklist.	5 / 5
Progressive Disclosure	Good header structure, but the body inlines the full JSON schema even though references/source-sample-schema.md exists, and that bundle file is never linked from the body — content that belongs in a separate file is inlined and the reference is orphaned.	3 / 5
	Total	16 / 20 Passed

Description

92%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.

A strong, specific description that clearly states both capability and trigger conditions for a narrow domain. Minor improvement possible in trigger-term synonym coverage, but it is otherwise comprehensive and distinct.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions with comprehensive coverage: 'extract...recipe shot list, VO script, characters, voices, world, atom-skills, master mp4', 'emit a source-sample.json', 'links every character and voice to the central character library', 'adds it first then links'.	5 / 5
Completeness	Explicitly answers both what ('extract...emit a source-sample.json...links...adds') and when ('Use when the user wants to remix one of their existing ads') with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Good natural terms like 'remix one of their existing ads' and 'ad-run folder', but vocabulary is narrow with few synonyms or variations users might say, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche ('content-goose ad-run folder', 'source-sample.json', references to upload-ad-sample and remix-ad) with distinct triggers and minimal overlap risk.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (512 lines); consider splitting into references/ and linking	Warning
referenced_paths_exist	Referenced path issues: 6 missing, 2 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/ads/composites/extract-source-sample/SKILL.md
Commit: 2523432

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.