agentleFS
zerlinpizerlinpi/amazon-ads-skills/CLAUDE.md

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…

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
  1. Very specific:

    Read that skill's SKILL.md first.

    line 10
  2. Very specific:

    Use skills/amazon-ads-optimizer/SKILL.md when the request spans multiple optimization domains.

    line 12
  3. Very specific:

    When compared windows come from different APIs, MCPs, exports, warehouses or report definitions, load references/data-lineage.md before …

    line 13
  4. Very specific:

    When a conclusion depends on live MCP/connector evidence, load references/connector-capability.md, resolve canonical IDs with …

    line 14
  5. Very specific:

    When compact history needs decision-time measurement identity, use the read-only scripts/project_measurement_history.py projection contract …

    line 15
  6. Very specific:

    When evaluating whether a Skill adds value, use schemas/skill-effectiveness-benchmark.json plus scripts/summarize_skill_effectiveness.py …

    line 16
  7. Very specific:

    Default to Suggest mode unless the user explicitly requests another mode and an external executor is available.

    line 17
  8. Distinctive:

    Never fabricate missing metrics, source lineage, or silently mix marketplaces, profile/account scopes, currencies, timezones, attribution …

    line 23
  9. Distinctive:

    Never expose secrets or authentication material.

    line 28

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

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

  1. Match the user intent to one skill under skills/.
  2. Read that skill's SKILL.md first.
  3. Load references/ or schemas/ only when the skill asks for them or the task requires exact definitions.
  4. Use skills/amazon-ads-optimizer/SKILL.md when the request spans multiple optimization domains.
  5. When compared windows come from different APIs, MCPs, exports, warehouses or report definitions, load references/data-lineage.md before high-confidence trend/causal conclusions.
  6. When a conclusion depends on live MCP/connector evidence, load references/connector-capability.md, resolve canonical IDs with scripts/resolve_skill_capabilities.py, then run scripts/evaluate_connector_capability_gate.py against the active capability snapshot before metric interpretation. Do not invent capability IDs; missing connector support is not a zero measurement.
  7. When compact history needs decision-time measurement identity, use the read-only scripts/project_measurement_history.py projection contract rather than inventing lineage from current metrics.
  8. When evaluating whether a Skill adds value, use schemas/skill-effectiveness-benchmark.json plus scripts/summarize_skill_effectiveness.py only for completed paired trial records; actual model/harness execution remains external.
  9. Default to Suggest mode 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.
  • Execute means 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_at does not imply available_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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.