hector-keyword-harvestinglisted

Use this skill ANY TIME the user asks about keyword harvesting, finding keywords to add, identifying search terms not in exact match, or gap analysis — e.g. "harvest keywords", "what keywords should I add?", "which search terms should I be targeting in exact match?", "find terms with orders not in my exact targeting", "run a harvest for [brand/account]", "show me harvesting opportunities", "keyword gap analysis", or close paraphrases. Also fires when the user wants to add the harvested terms to existing or new campaigns (action phase). Does NOT fire for: "show me my top search terms" (performance report only), "which search terms are wasting spend" (negative keyword task), "what keywords should I pause/remove" (bid or status task), general search-term analytics with no intent to promote terms, placement analysis, or budget questions.
hectorai-live/hector-amazon-ads · ★ 0 · Data & Documents · score 72

Install: claude install-skill hectorai-live/hector-amazon-ads

# Hector Keyword Harvesting (v2) > ## ⚠️ CRITICAL OBLIGATIONS — READ BEFORE EVERY USE > > 1. **Resolve profile_id BEFORE any tool call.** Never guess or invent a profile ID. If not > in context, resolve via `find_profile_by_name` or `get_amazon_profiles` first. This is a > hard blocker — no tool call proceeds without a confirmed profile_id. > 2. **Run date-resolution skill before setting any date.** Always run > `hector-mcp-date-resolution` before setting start_date / end_date. Never trust the > session clock. > 3. **Pull the account snapshot FIRST to derive min_roas dynamically.** Use > `analytics_seller_vendor_master_overview` for the same date window as the harvest to get > average account ROAS. min_roas = account_average_ROAS × 0.60. Never hardcode a ROAS > threshold. > 4. **Default date window is last_30_days.** If fewer than 5 harvest candidates are returned, > automatically re-run with last_60_days. Inform the user when this escalation happens. > Never ask the user for a date range unless they volunteer one. > 5. **Always pull 250 rows (limit: 250).** Never use the default 5-row preview for harvest > calls. The full list must be shown before any action is taken. > 6. **Always group results by product/category.** Claude reads the search terms semantically > and defines the categories — do not rely on any pre-built Hector table. Never present a > flat undifferentiated list. > 7. **Hard threshold: min_orders = 2.** A search term with f