amazon-ads-skills
CLAUDE.md8 starsChanged 53 days agoMITView on GitHub
This repository is an Amazon Ads Agent Skills library. Use the canonical skill definitions in skills/*/SKILL.md; do not fork or duplicate their business rules into Claude-specific copies. For first-run installation, cloning, plugin/workspace choices, bootstrap prompts, and smoke tests, read docs/GETTING-STARTED.md. Prefer the whole repository as the workspace so CLAUDE.md, the canonical skills/ tree, and shared references stay resolvable. If automatic Skill discovery fails, explicitly load the matching skills/<name>/SKILL.md instead of inventing a runtime-specific copy or path. See AGENTS.md for repository-wide…
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- amazon-ads-auditSkill
- amazon-ads-optimizerSkill
- anomaly-detectionSkill
- bid-optimizationSkill
- budget-optimizationSkill
- campaign-health-monitorSkill
- experiment-plannerSkill
- growth-opportunity-finderSkill
- keyword-optimizationSkill
- negative-targetingSkill
- performance-drop-diagnosisSkill
- placement-optimizationSkill
- post-change-reviewSkill
- profitability-analysisSkill
- search-term-analysisSkill
The file
We split this CLAUDE.md into the rules it gives an agent
9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read that skill's SKILL.md first.
- Very specific: line 12
Use skills/amazon-ads-optimizer/SKILL.md when the request spans multiple optimization domains.
- Very specific: line 13
When compared windows come from different APIs, MCPs, exports, warehouses or report definitions, load references/data-lineage.md before …
- Very specific: line 14
When a conclusion depends on live MCP/connector evidence, load references/connector-capability.md, resolve canonical IDs with …
- Very specific: line 15
When compact history needs decision-time measurement identity, use the read-only scripts/project_measurement_history.py projection contract …
- Very specific: line 16
When evaluating whether a Skill adds value, use schemas/skill-effectiveness-benchmark.json plus scripts/summarize_skill_effectiveness.py …
- Very specific: line 17
Default to Suggest mode unless the user explicitly requests another mode and an external executor is available.
- Distinctive: line 23
Never fabricate missing metrics, source lineage, or silently mix marketplaces, profile/account scopes, currencies, timezones, attribution …
- Distinctive: line 28
Never expose secrets or authentication material.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CLAUDE.md
This repository is an Amazon Ads Agent Skills library. Use the canonical skill definitions in skills/*/SKILL.md; do not fork or duplicate their business rules into Claude-specific copies.
For first-run installation, cloning, plugin/workspace choices, bootstrap prompts, and smoke tests, read docs/GETTING-STARTED.md. Prefer the whole repository as the workspace so CLAUDE.md, the canonical skills/ tree, and shared references stay resolvable. If automatic Skill discovery fails, explicitly load the matching skills/<name>/SKILL.md instead of inventing a runtime-specific copy or path.
How to work with this repository
- Match the user intent to one skill under
skills/. - Read that skill's
SKILL.mdfirst. - Load
references/orschemas/only when the skill asks for them or the task requires exact definitions. - Use
skills/amazon-ads-optimizer/SKILL.mdwhen the request spans multiple optimization domains. - When compared windows come from different APIs, MCPs, exports, warehouses or report definitions, load
references/data-lineage.mdbefore high-confidence trend/causal conclusions. - When a conclusion depends on live MCP/connector evidence, load
references/connector-capability.md, resolve canonical IDs withscripts/resolve_skill_capabilities.py, then runscripts/evaluate_connector_capability_gate.pyagainst the active capability snapshot before metric interpretation. Do not invent capability IDs; missing connector support is not a zero measurement. - When compact history needs decision-time measurement identity, use the read-only
scripts/project_measurement_history.pyprojection contract rather than inventing lineage from current metrics. - When evaluating whether a Skill adds value, use
schemas/skill-effectiveness-benchmark.jsonplusscripts/summarize_skill_effectiveness.pyonly for completed paired trial records; actual model/harness execution remains external. - Default to
Suggestmode unless the user explicitly requests another mode and an external executor is available.
Non-negotiable safety
- Skills in this repository do not directly mutate live Amazon Ads accounts.
Executemeans producing a validated action payload for an external connector/executor after explicit authorization.- Never fabricate missing metrics, source lineage, or silently mix marketplaces, profile/account scopes, currencies, timezones, attribution windows, date ranges, or incompatible source definitions.
- Missing/retired historical reporting, unsupported connector fields, or absent report rows are not zero unless the source contract explicitly proves zero.
- Distinguish when data was fetched from which event dates are actually complete;
extracted_atdoes not implyavailable_through. - Detect promotional periods, operational confounders, and parent/variation-family retail changes before interpreting short-term child-ASIN performance changes.
- Effectiveness summaries do not call models, claim statistical significance, or authorize live advertising mutation.
- Never expose secrets or authentication material.
See AGENTS.md for repository-wide conventions, docs/GETTING-STARTED.md for runtime setup and prompts, references/data-lineage.md for cross-source evidence rules, references/optimization-memory.md for measurement-state memory, and references/decision-boundaries.md for execution guardrails.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

