mcpbeat

Ads Plan

agricidaniel/ads-plan

Create a professional paid-advertising strategy covering objectives, economics, platform selection, campaign architecture, audiences, budget, creative, measurement, experiments, governance, rollout, and reporting. Use for ad plan, media plan, PPC strategy, paid-social strategy, campaign architecture, advertising roadmap, or channel planning.

7k tokens
context cost
the whole folder, loaded on every use
13
files
instructions only
0
copies elsewhere
how many repositories repackaged it
7798
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/AgriciDaniel/claude-ads --skill ads-plan

The instruction itself

1 sections, as written by the author
  • Read the setup profile, business economics, evidence, current account state, and

relevant industry template as optional input.

  • Define objective, customer, offer, conversion, value, constraints, geography,

regulated category, time horizon, and success criteria.

  • Evaluate channel roles and exclusions from first principles; do not require every

supported platform. For a channel outside the twelve-platform contract, load

ads/references/additional-platforms.md and return a research lead unless

its current buying, eligibility, measurement, and creative evidence is present.

  • Specify campaign architecture, audience strategy, creative system, budget and

pacing, measurement, experiments, policy controls, and operating cadence.

  • Phase prerequisites before launch, learning, optimization, and scale.
  • Assign every action an owner, timing, dependency, guardrail, evidence, success

measure, and rollback or exit condition.

  • Return canonical JSON and render the requested human plan.

A plan is advisory. It becomes an account change only through launch or optimize

mutation gates.

How to use it

Copy the folder

Take agricidaniel/ads-plan from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.