CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ad-management-intake

The intake stage of a Meta ad harness. Researches the brand first, states what it assumes, and asks only what it cannot infer and what would change money, claims or legal exposure if guessed wrong — at most four questions a turn, in plain business language. Writes the brand's stable facts (ads/brand.md), the campaign brief, and a log of what was asked vs assumed. Use it when someone wants to run Meta ads and the brand's ad facts are not yet recorded.

Quality

94%

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

92%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 mature, highly actionable skill body: every step lands in concrete file writes with templates, validation is explicit (quality checklist plus the contract validator), and detail is properly pushed into three real reference files. The only cost is a little non-instructional prose — the narrative opener and maintainer-parity comments — and repeated restatements of the core asking rule.

Suggestions

Cut the 'A good agency would not hand them a twenty-field form' narrative opener down to one line; the rule section already carries the philosophy.

Move the maintainer copy/parity HTML comment out of the agent-facing body (or shrink it to one line) since it instructs maintainers, not the agent.

Consider consolidating the asking rule's restatements in Decision Rules or Quality Checks into references to the canonical 'The one rule' section.

DimensionReasoningScore

Conciseness

The body is dense with harness-specific instruction and explains nothing Claude already knows, but contains minor trimmable material: the five-line agency narrative opener ("A good agency would not hand them a twenty-field form…"), maintainer-facing HTML comments about the shared block's copy/parity procedure, and the asking rule restated in "The one rule", Step 2, Decision Rules and Quality Checks. It is above the score-3 anchor (mostly efficient) but not every token instructs, so it falls short of the lean score-5 anchor.

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: a fact-sheet table with a worked example row, literal output text for each file (e.g. "stage: intake, ids none/[], updated_by: ad-management-intake"), a copy-paste labelling table with exact strings like "(assumed from <source> — not confirmed)", a complete example assumptions message, and full sample decisions.md entries. This matches the score-5 anchor — concrete templates covering the common cases — rather than score 4's 'minor gaps'.

5 / 5

Workflow Clarity

Steps 0–6 are explicitly sequenced (resume → gather → fact sheet → Section A → Section B → state assumptions → write and hand over), with a corrections sub-procedure, an end-of-run Quality Checks checklist (including "ads/ passes the contract validator"), and a Failure Modes table mapping symptom → cause → fix that serves as error-recovery feedback loops. The batch write operation is covered by validation checkpoints, matching the score-5 anchor and exceeding score 4's 'most checkpoints'.

5 / 5

Progressive Disclosure

SKILL.md is a well-organized overview that routes to three real, one-level-deep bundle files — [references/gooseworks-adapter.md], [references/local-adapter.md] chosen by mode, and references/business-types.md for per-type detail (all verified present, 45–95 lines each) — with appropriately split content and a section explaining that paths are relative to the skill's own folder. The external meta-ad-manager contract is clearly located rather than nested, so navigation matches the score-5 anchor instead of the score-4 'minor organization gaps'.

5 / 5

Total

19

/

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 description: third-person, concrete, and tightly scoped to the intake stage, with an explicit 'Use it when…' clause carrying a disambiguating condition. The only weakness is keyword breadth — it says 'Meta ads' but omits the Facebook/Instagram phrasings many users would naturally use.

Suggestions

Add natural synonyms to the trigger clause, e.g. 'Use it when someone wants to run ads on Meta (Facebook or Instagram ads) and the brand's ad facts are not yet recorded.'

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Researches the brand first, states what it assumes, and asks only what it cannot infer", "at most four questions a turn", "Writes the brand's stable facts (ads/brand.md), the campaign brief, and a log of what was asked vs assumed" — with concrete file outputs, giving comprehensive coverage of the skill's capabilities. It clearly exceeds the score-4 anchor (only minor gaps) and matches the score-5 anchor for multiple specific concrete actions.

5 / 5

Completeness

It explicitly answers both parts: what it does ("Researches the brand first, states what it assumes, and asks only what it cannot infer… Writes the brand's stable facts… the campaign brief, and a log") and when to use it ("Use it when someone wants to run Meta ads and the brand's ad facts are not yet recorded"), matching the score-5 anchor for clear what-and-when with concrete triggers. Not score 4, since the 'when' clause is already fully explicit and conditional.

5 / 5

Trigger Term Quality

"Use it when someone wants to run Meta ads" plus "brand's ad facts are not yet recorded" gives a good natural trigger phrase, but coverage misses common synonyms users say — "Facebook ads", "Instagram ads", "advertising", "paid social". It sits above the score-3 anchor (relevant keywords present, some variations missing) but below score 5, which requires comprehensive synonyms.

4 / 5

Distinctiveness Conflict Risk

"The intake stage of a Meta ad harness" plus the condition "the brand's ad facts are not yet recorded" carves out a clear niche that disambiguates it from sibling ad skills (strategy, launch) covering the same 'run Meta ads' trigger. This matches the score-5 anchor (clear niche, distinct triggers, minimal conflict risk) rather than score 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

19

/

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

skills/ads/composites/ad-management-intake/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.