campaign-brief-generator

Generate a complete marketing campaign brief from a launch goal, ICP, and product context. Pure reasoning skill. Outputs channel plan, messaging angles, content types, timeline, and success metrics. Designed for seed/Series A founders and small GTM teams who aren't professional marketers but need to run focused campaigns. No scripts — pure reasoning.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/content/composites/campaign-brief-generator/SKILL.md

Quality

Content

82%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 well-executed instruction-only skill: the five-phase workflow is clearly sequenced and the guidance is unusually concrete, culminating in a complete output template. Weak spots are mild redundancy (duplicated trigger sections, repeated 'pure reasoning' framing) and the lack of explicit validation checkpoints in the workflow.

Suggestions

Merge the 'When to Use' and 'Trigger Phrases' sections into one — they duplicate each other and both restate the frontmatter description.

Add a validation checkpoint after Phase 0 intake (e.g., 'if goal or ICP answers are vague, ask one round of follow-ups before proceeding') and a brief quality check before emitting the final brief.

Consider moving the full Phase 5 output template and/or the channel reference table into a references/ file to slim the always-loaded SKILL.md body.

Dimension	Reasoning	Score
Conciseness	The body is dense and domain-specific with no explanations of concepts Claude already knows, but 'Pure reasoning skill' is repeated from the description and the 'When to Use' and 'Trigger Phrases' sections duplicate each other's content. Not 3 — the redundancy is minor relative to the whole; not 5 — the duplication is trimmable.	4 / 5
Actionability	Highly concrete throughout: 13 numbered intake questions with examples, a channel selection table with resource requirements, a message structure template, example calendar rows, and a complete copy-paste output brief template. Per the scoring notes, an instruction-only skill with fully actionable guidance merits the top score.	5 / 5
Workflow Clarity	Phases 0–5 are clearly sequenced, with KPIs 'defined before the campaign starts' and a midpoint review date acting as partial checkpoints. Not 5 — there are no explicit validation steps (e.g., confirming intake answers are complete/specific before generating the brief); not 3 — the sequence and existing checkpoints are solid.	4 / 5
Progressive Disclosure	No bundle files exist; the single file is cleanly sectioned and all inline content (channel table, output template) is arguably appropriate for a pure reasoning skill. However, at ~205 lines — well over the 50-line simple-skill threshold — the full output template and channel reference table are inlined where a one-level-deep reference file could carry them; sits between anchors 4 and 5, closer to good-with-minor-gaps.	4 / 5
	Total	17 / 20 Passed

Description

71%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 that clearly states what the skill produces and for whom, with specific output categories and domain terminology. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness and leaves invocation conditions implicit.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user asks for a campaign plan, go-to-market strategy, or campaign brief for a product launch or new segment.'

Include natural trigger synonyms users would actually say ('campaign plan', 'go-to-market plan', 'GTM strategy') to improve trigger term coverage.

Trim the redundant 'Pure reasoning skill' / 'No scripts — pure reasoning' repetition into a single clause to tighten the description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and outputs — 'Generate a complete marketing campaign brief' plus 'channel plan, messaging angles, content types, timeline, and success metrics' — with comprehensive coverage of the skill's outputs. Score 4 was considered but there are no meaningful gaps in coverage.	5 / 5
Completeness	The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent trigger guidance — 'Designed for seed/Series A founders' describes the audience, not when to invoke the skill. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3; not 4 because the 'when' is only weakly implied.	3 / 5
Trigger Term Quality	Good natural keywords ('campaign brief', 'launch goal', 'ICP', 'GTM'), but common user phrasings like 'go-to-market plan', 'campaign plan', or 'help me plan a campaign' are missing. Falls between anchor 3 (missing variations) and 5 (comprehensive synonyms), closer to good coverage.	4 / 5
Distinctiveness Conflict Risk	The niche (founder/GTM campaign briefs) is mostly distinct with specific terminology ('ICP', 'channel plan', 'campaign brief'), but 'marketing campaign' language has minor overlap risk with general content/marketing skills. Not 5 due to that overlap; not 3 because the positioning is clearly differentiated.	4 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/content/composites/campaign-brief-generator/SKILL.md
Commit: cc3e518

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.