Individual skill
amazon-ads-create-dsp-campaign
Create and launch an Amazon DSP Performance+ (P+) or Brand+ (B+) campaign end-to-end using this amazon-ads-mcp server's allv1_* tools. Drives the full setup: gather user inputs, query the advertiser account to resolve the DSP account ID, create the DSP campaign in PAUSED state, attach ASIN conversion tracking, query eligible automated targeting tactics, create one ad group per (inventoryType, tactic) combination, optionally create ads and ad-group associations, then activate everything in strict parent-first order with verification reads between writes. Supports P+ tactics (CUSTOMER_ACQUISITION, REMARKETING, RETENTION, MAXIMIZE_PERFORMANCE) and B+ tactics (PROSPECTING) across DISPLAY, VIDEO_OLV, VIDEO_STV, AUDIO, and LIVE_EVENTS inventory. Trigger whenever the user mentions creating a DSP P+ or B+ campaign, launching automated DSP targeting, setting up Performance+ or Brand+ ad groups, or any variant like 'spin up a P+ campaign', 'launch Brand+ prospecting', 'create DSP automated targeting'.
plugins/KuudoAI/skills/skills/amazon-ads-create-dsp-campaign/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,530
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- marketing Derived category
- sales Derived category
- testing Derived category
- testing-browser Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
CHANGELOG.mddoc · 3,326 bytesLICENSE.txtdoc · 443 bytesSKILL.mdcore · 24,524 bytesevals/evals.jsonasset · 6,829 bytesreferences/inventory_type_mapping.mddoc · 1,882 bytesreferences/step0_gather_inputs.mddoc · 3,828 bytesreferences/step1_query_account.mddoc · 2,673 bytesreferences/step2_create_campaign.mddoc · 4,259 bytesreferences/step3_conversion_tracking.mddoc · 6,254 bytesreferences/step4_query_eligible_tactics.mddoc · 4,290 bytesreferences/step5_create_adgroup.mddoc · 3,528 bytesreferences/step6a_create_ad.mddoc · 5,983 bytesreferences/step6b_create_ad_association.mddoc · 1,676 bytesreferences/step7_activate.mddoc · 4,042 bytes
Read excerpt
# Create DSP P+/B+ Campaign
## When to use this skill
- Create a new DSP **Performance+ (P+)** or **Brand+ (B+)** campaign
- Set up automated targeting tactic ad groups under a DSP campaign
- Launch DSP campaigns across DISPLAY, VIDEO_OLV (online video), VIDEO_STV (streaming TV), AUDIO, or LIVE_EVENTS inventory
If the user wants manual targeting (e.g., specific audience or supply targets), this skill does not apply — they need the standard DSP campaign workflow with explicit targets, not the automated tactic workflow.
## Account-context recovery
If Amazon account scope, identifier type, marketplace mapping, or account relationships become unclear, consult `amazon-ads-accounts` when it is available. Resume this skill after resolving the ambiguity. If it is unavailable, use equivalent read-only discovery and ask the user when multiple valid choices remain. Never guess or interchange identifier types.