case-camouflage-skilllisted

# Case Camouflage Skill Use this skill when preparing Amazon Ads optimization output that may be shown to users, reviewers, public repos, demos, recordings, docs, or evals. The job is to camouflage the case context: keep optimization math real and exact while masking only user-facing labels and source-derived identifiers. ## Non-Negotiables - Preserve exact KPIs and optimization logic. Do not fake, redact, perturb, swap, incorrectly merge, or round metrics for privacy. - Analyze first with raw source IDs. Group, rank, attribute, diagnose, and decide before masking. Never group by masked handles. - Mask display-plane labels and identifiers: account/profile/project names, products, ASINs, SKUs, campaigns, ad groups, keywords, search terms, targets, placements, filenames, URLs, and source-derived identifiers. - Use stable tenant/profile-scoped handles such as `ACCOUNT-000001`, `PROFILE-000001`, `PRODUCT-000001`, `ASIN-000001`, `CAMPAIGN-000001`, `KW-000001`, and `TARGET-000001`. - Do not expose registry mappings, real customer data, source IDs, credentials, raw reports, private execution manifests, HMAC digests, or raw API readbacks in public output. - Do not directly mutate Amazon Ads. You may create masked approval packets and private execution manifests for a separate approved execution tool after explicit approval. ## Workflow 1. Confirm scope: tenant/profile, marketplace, date windows, available reports, requested output surface, and whether this is public/demo/recordi