Skip to content

AgriciDaniel/claude-ads / skills/ads-plan

ads-plan

Verified

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.

FileKindSize
SKILL.mdskill md2.1 KB
assets/agency.mdmarkdown2.2 KB
assets/b2b-enterprise.mdmarkdown2.1 KB
assets/ecommerce-creative.mdmarkdown2.1 KB
assets/ecommerce.mdmarkdown2.0 KB
assets/finance.mdmarkdown2.1 KB
assets/generic.mdmarkdown2.0 KB
assets/healthcare.mdmarkdown2.0 KB
assets/info-products.mdmarkdown2.0 KB
assets/local-service.mdmarkdown2.0 KB
assets/mobile-app.mdmarkdown2.1 KB
assets/real-estate.mdmarkdown2.2 KB
assets/saas.mdmarkdown2.2 KB

assets/b2b-enterprise.md

View on GitHub
# B2B enterprise paid-media planning questions

> Status: qualitative, unscored planning aid.

## Required gates

- Context gate: document the offer, buying process, decision roles, target accounts,
  sales ownership, regions, contract motion, conversion definition, and data window.
- Evidence gate: ground account selection, channel fit, claims, and proof in approved CRM,
  account, research, and current official source IDs.
- Privacy gate: confirm lawful use, minimization, matching terms, retention, and access
  controls before using account or contact data.
- Regulatory gate: identify applicable industry, employment, credit, privacy, disclosure,
  and regional constraints and route uncertainty to qualified review.
- Measurement gate: define how ad interactions connect to account progression, pipeline,
  revenue, and sales feedback without presenting influence as causation.

## Planning questions

- Who participates in the decision, and what evidence does each role need?
- Which accounts and segments are approved, reachable, sufficiently populated, and current?
- What distinguishes awareness, consideration, evaluation, purchase, and expansion signals?
- Which offers and proof assets have owner approval and substantiation?
- How will marketing and sales handle routing, follow-up, suppression, and disagreement?
- Which platform capabilities and formats are currently eligible for the account and locale?
- What observation window matches the buying process and the available outcome latency?

## Candidate considerations

- Consider role-specific or stage-specific hypotheses only when the supporting context exists.
- Consider account-level measurement alongside person-level signals without merging identities.
- Use platform and search roles as hypotheses, not a fixed hierarchy or budget mix.
- Treat content, event, demo, and sales-conversation outcomes as distinct evidence classes.

## Output guardrails

- Return qualitative options, dependencies, source IDs, owners, and measurement questions.
- Do not prescribe platform shares, audience sizes, bid strategies, attribution windows,
  pipeline ratios, or performance targets.
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall
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: 108kUpdated Claude CodeCodexVerifiedInstall
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: 108kUpdated Claude CodeCodexVerifiedInstall