← ClaudeAtlas

hector-search-term-negationlisted

Use ONLY when the user explicitly asks to add negative search terms based on bleeding data — trigger phrases include "run search term negation for X", "negate bleeding search terms for X", "add negatives for bleeding in X", "execute bleeding negation on X", and close paraphrases where "negation" or "negative" + a named brand co-occur. Identifies bleeding search terms per the standard Hector bleeding rules (SP-only, ≥ floor(1/CR) clicks, 0 orders, exclude branded, exclude ASIN-pattern, ungrouped), then negates each identified SearchTerm as a NEGATIVE EXACT MATCH in the specific ad group where it is bleeding. Does NOT fire on conversational mentions of negation, on single-term negation requests, on audit requests, or on requests to edit this skill. ALWAYS presents a preview and requires explicit CONFIRM before any write. Runs independently of the audit skill — no prior audit required.
hectorai-live/hector-amazon-ads · ★ 0 · Code & Development · score 72
Install: claude install-skill hectorai-live/hector-amazon-ads
# Hector Search Term Negation (v1) > ## ⚠️ CRITICAL OBLIGATIONS — READ BEFORE EVERY USE > > 1. **ALWAYS present preview + require explicit CONFIRM before any write.** Present summary + top-10 preview. User must type CONFIRM (case-insensitive) to proceed. Any other input = CANCEL. This is a hard gate — never write without an explicit CONFIRM. > 2. **NEVER guess the profile_id.** Resolve via `find_profile_by_name`. If a brand was already discussed earlier in this chat, ask the user to confirm rather than asking cold. If multiple profiles match, present them and let user pick. If zero match, stop. > 3. **Match type is LOCKED at negative exact match.** Never negative phrase, never negative broad. This is non-negotiable. > 4. **Negations are scoped to the specific ad group where the term is bleeding.** If SearchTerm "soap" bleeds in ad group A AND ad group B, that becomes two separate negation writes — one per ad group. Never negate the same term across all ad groups. > 5. **Bleeding logic is IDENTICAL to the audit skill.** SP-only, `Clicks > floor(1/CR)-1`, `Orders = 0`, exclude branded (via brand classifier), exclude ASIN-pattern (`^b0[a-z0-9]{8}$`), ungrouped. Same rules, same filter, same click floor computation. > 6. **Duplicate negations are SKIPPED and LOGGED.** If a SearchTerm is already negated as exact in the target ad group, do not re-add. Log the skip in the change-log CSV with reason "already negated." > 7. **Every run produces a change-log CSV** at `/mnt/user-data/o