AgriciDaniel/claude-ads / skills/ads-plan
ads-plan
VerifiedCreate 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.1 KB |
| assets/agency.md | markdown | 2.2 KB |
| assets/b2b-enterprise.md | markdown | 2.1 KB |
| assets/ecommerce-creative.md | markdown | 2.1 KB |
| assets/ecommerce.md | markdown | 2.0 KB |
| assets/finance.md | markdown | 2.1 KB |
| assets/generic.md | markdown | 2.0 KB |
| assets/healthcare.md | markdown | 2.0 KB |
| assets/info-products.md | markdown | 2.0 KB |
| assets/local-service.md | markdown | 2.0 KB |
| assets/mobile-app.md | markdown | 2.1 KB |
| assets/real-estate.md | markdown | 2.2 KB |
| assets/saas.md | markdown | 2.2 KB |
assets/agency.md
View on GitHub# Agency paid-media planning questions
> Status: qualitative, unscored planning aid.
## Required gates
- Context gate: identify the client, business model, objective, conversion definition,
geography, currency, data window, budget authority, and active platforms separately.
- Evidence gate: use only client-approved inputs and current official source IDs; keep
assumptions, stale evidence, and cross-client comparisons explicit.
- Privacy gate: isolate every client's credentials, exports, audiences, creatives,
reports, run directory, and retention policy.
- Regulatory gate: identify the client's category and jurisdictions, then obtain the
required platform, privacy, and specialist review before proposing regulated activity.
- Capability gate: distinguish export analysis, authorized reads, drafts, and disabled
writes for each client and platform.
- Approval gate: record the client owner, agency owner, creative approval, budget ceiling,
mutation authority, verification plan, and rollback path.
## Planning questions
- Which business outcome does the client own, and how is it reconciled downstream?
- Which client facts, claims, audiences, assets, and account permissions are approved?
- Where do tracking, CRM, consent, feed, and offline outcome definitions disagree?
- Which platforms are eligible and measurable for this client's objective and geography?
- Which responsibilities belong to the client, agency, platform, or another vendor?
- How will findings, approvals, incidents, and changes remain client-specific and auditable?
- What would cause the plan to stop for missing evidence, privacy, policy, or authority?
## Candidate considerations
- Compare platform roles from current client evidence rather than a standard agency mix.
- Consider a small, reversible learning plan with client-defined guardrails.
- Separate internal quality review from client-facing reporting and account execution.
- Preserve unsuccessful hypotheses and contradictory evidence for the next planning cycle.
## Output guardrails
- Return options, tradeoffs, owners, assumptions, source IDs, and verification steps.
- Do not provide universal allocations, unsupported targets, automatic account-action
rules, or cross-client performance promises.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |