planning-campaigns
Skill from SupercmoHQ/superCMO-skills
Install
npx skills add SupercmoHQ/superCMO-skills --skill planning-campaigns
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add SupercmoHQ/superCMO-skills
/plugin install supercmo@superCMO-skills
This skill is part of the plugin “supercmo”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the planning-campaigns skill do?
Description from the SKILL.md in the source repository.
Questions about planning-campaigns
What does the planning-campaigns skill do?
Decides what to make next — turns the brand, the product, your own running ads and competitor research into the concepts worth testing next. Each concept is a full description of one ad, the buyer it targets, the bet it tests and the evidence it rests on — complete enough for a producer to build from directly. Nothing is generated before the plan is approved — it asks which concepts to build, and only then hands each approved concept to the skill that builds it. Use when the user asks what to make, what to test next, what hooks or angles to try, for campaign concepts, or a creative plan — or wants the whole campaign run end to end, from research to finished ads. Not for a single ad with no plan behind it — that goes straight to the producer skill.
How do I install planning-campaigns?
In a terminal: npx skills add SupercmoHQ/superCMO-skills --skill planning-campaigns. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use planning-campaigns?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is planning-campaigns safe to use?
Our automatic check found no risky patterns (piped shell scripts, hidden characters, secret access, prompt overrides). It is not a full audit – read the SKILL.md and any scripts before installing.
More skills from SupercmoHQ/superCMO-skills
Analyzes the ads competitors are running — the ones live now, the ones they have already stopped, and which have run longest.
Generates the storyboard sheets for a video — one image per clip, panels in a row, each panel one action.
Generates a UGC video — a creator or customer, on camera as themselves, sharing their own authentic take on a product.
ALWAYS read this skill before generating or animating any video, or calling video_generate — text-to-video, image-to-video, a start→end transition, or a reference / motion / audio-guided clip.
Finds out who a brand competes with. Reads what the brand sells from its site, searches the web for the alternatives buyers compare it against, and proposes a shortlist with competitor names …
Onboards a new user — sets up their brand for the first time from their website. Analyzes the brand, finds its competitors, and saves both to the company profile that every later …
Writes the words of an ad — the headline, primary text, description and call to action that go into the ad platform's own fields, shaped to the channel it runs on.
Writes what is said in a video — the words a person speaks on camera, or a voiceover heard over the picture.
Related skills in Testing & QA
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any …
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Automate browser interactions, test web pages and work with Playwright tests.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.