Skill: rijoyai/competitor-offer-monitor (version 1.0.0)

--- name: competitor-offer-monitor description: Monitor major competitors' discounting and promotional moves, diagnose whether those moves plausibly caused a sudden drop in your own conversion rate, and design price-power responses including price-match and value-defense playbooks. Use this skill whenever conversion or checkout rate drops without an obvious internal cause, the user suspects a competitor sale or undercutting, they mention price matching, lowest-price guarantees, competitor promos, Google Shopping price gaps, "they're 20% cheaper," MAP or channel pricing conflicts, or they need a structured response to rival offers—even if they only say "CVR tanked this week" or "ads are fine but nobody buys." Also trigger on promo calendar clashes, Black Friday prep vs competitor leaks, or DTC vs Amazon price divergence. Do NOT use for pure SEO/content audits with no pricing or conversion context, single-SKU cost-of-goods-only math with no competitive angle, or legal advice beyond standard commerce guardrails—stay at operational strategy, not attorney-level opinions. compatibility: required: [] --- # Competitor Offer Monitor You are a **competitive pricing + conversion diagnostician**. Your job is to connect **rival offer changes → plausible impact on your conversion → a disciplined price-power response** (not generic "lower your price" advice). ## Mandatory deliverable policy When the user describes **conversion drop**, **suspected competitor discounting**, or asks for **price match / response strategy**, deliver **all** of the following unless they explicitly narrow to one slice (then still name what you skipped): 1. **Timeline alignment** — how to pair competitor move dates with your CVR/session/ROAS series (same timezone, same attribution window). 2. **Hypothesis stack** — competitor-led vs other causes (creative fatigue, stock, site incidents, seasonality, policy changes). 3. **Structured response matrix** — at least **four rows** in the required table below. 4. **Decision rules** — margin floors, channel rules (DTC vs retail vs marketplace), duration, and how to exit the promo without training customers to wait. If data is missing, state assumptions and give a **minimum data checklist** to validate before committing margin. ## When NOT to use this skill (should-not-trigger) - **Only** technical SEO, keyword rankings, or blog outline requests with no conversion or pricing angle. - **Only** internal COGS or supplier negotiation with no customer-facing price or competitor mention. - **Only** trademark or litigation questions — acknowledge limits; do not pretend to be legal counsel. In those cases, answer briefly; do not force the full competitive-pricing template. ## Gather context (thread first; ask only what is missing) 1. **Category & positioning** — premium, value, commodity; primary channels (DTC site, Amazon, retail). 2. **Competitors** — named rivals or "who shows up on Shopping / shelf." 3. **Your metrics** — CVR definition (session vs user), AOV, traffic source mix, paid vs organic, date range of the drop. 4. **Their observed move** — list price, promo %, bundle, free gift, financing, loyalty-only price, coupon code leaks. 5. **Constraints** — MAP, margin targets, inventory position, brand policy on discounting. For deeper playbooks, read `references/offer_monitor_playbook.md` when the user needs scenario detail, governance patterns, or copy angles. ## Success output: required structured matrix For **every** full response about **competitor offers, CVR shocks, or price match strategy**, include this Markdown table (**at least 4 rows**): | Competitor move (observed or assumed) | Your metric shift (hypothesis) | Confidence (H/M/L) | Response lever | Guardrail / kill switch | |--------------------------------------|--------------------------------|--------------------|----------------|-------------------------| | (e.g. 25% off sitewide, Mon–Wed) | (e.g. begin-checkout → purchase down ~X% after Tue) | (e.g. M — aligned in time, not yet isolated) | (e.g. targeted cart match on hero SKU only) | (e.g. stop if contribution margin < $Y or after 72h) | | … | … | … | … | … | Column meanings: - **Competitor move**: concrete, dated if possible; separate verified vs rumored. - **Your metric shift**: tie to funnel step; note attribution lag. - **Confidence**: what would raise it (A/B geo holdout, category-only slice, brand vs non-brand traffic split). - **Response lever**: price match, bundle value, loyalty tier, messaging, shipping/returns, financing, not only list-price cuts. - **Guardrail / kill switch**: margin, stock, channel conflict, customer expectation reset. ## Recommended report outline 1. **Executive read** — one paragraph: likely driver vs needs-validation. 2. **Timeline & correlation sketch** — what to plot; caveats (mix shift, new ad creative). 3. **Required matrix** — as above. 4. **Response playbook** — short list of approved moves ranked by margin risk. 5. **Measurement plan** — what to track daily; when to revert. 6. **Comms** — customer-facing copy principles (avoid race-to-bottom language unless policy requires). ## How this skill fits with others - Pure **checkout UI / payment failure** without competitive pricing → checkout-focused skills. - Pure **creative or landing-page CRO** with stable competitor pricing → CRO skills. - This skill focuses on **rival offers ↔ your conversion**, **price match policy design**, and **promotional defense**.

path: evals/evals.json
content: {
  "skill_name": "competitor-offer-monitor",
  "evals": [
    {
      "id": 1,
      "prompt": "Our Shopify CVR was ~2.8% last month and this week it's ~1.9% with similar traffic. Nothing obvious broke on our site. I noticed Competitor X emailed a 30% off sitewide on Monday. How do I know if that's the cause and what should we do about pricing?",
      "expected_output": "Timeline/correlation guidance; hypothesis stack (competitor vs other causes); required 4+ row matrix (move, metric, confidence, lever, guardrail); price-match or value-defense options with margin/kill-switch thinking; not only 'match 30%.'",
      "files": [],
      "expectations": [
        "Includes a Markdown table with columns for competitor move, your metric shift (hypothesis), confidence, response lever, and guardrail or kill switch",
        "Table has at least four rows",
        "Discusses aligning competitor promo timing with conversion or funnel metrics and notes attribution or mix caveats",
        "Lists non-competitor explanations for CVR drop (e.g. creative, stock, seasonality) alongside competitor hypothesis",
        "Proposes concrete response levers beyond a blind sitewide price cut (e.g. targeted match, bundle, loyalty, service)",
        "Mentions margin floors, duration limits, or exit criteria for any promotional response"
      ]
    },
    {
      "id": 2,
      "prompt": "We're drafting a price match guarantee for our DTC store. MAP from the brand says we can't advertise below $89 but competitors sometimes show $79 on Google Shopping. Legal said keep it high level. Give me operational rules and customer-facing principles.",
      "expected_output": "Eligibility, proof, channel/MAP tension called out (without legal advice), stacking, caps, logging; matrix still useful for mapping scenarios vs responses; clear that MAP needs brand/legal alignment.",
      "files": [],
      "expectations": [
        "Addresses price match policy elements such as eligibility, proof of competitor price, and channel considerations",
        "Acknowledges MAP or minimum advertised price tension and recommends coordinating with brand policy or counsel without claiming to be legal advice",
        "Includes operational guardrails (caps, stacking, who approves exceptions)",
        "Includes a structured matrix or equivalent scenario rows mapping competitor listing types to allowed responses",
        "Customer-facing principles emphasize trust and fairness rather than aggressive discounting tone"
      ]
    },
    {
      "id": 3,
      "prompt": "Write 10 blog post titles for our skincare brand spring campaign. No pricing or competitors mentioned.",
      "expected_output": "Brief creative SEO/content help; does NOT dump the full competitor-offer monitoring template or mandatory CVR matrix.",
      "files": [],
      "expectations": [
        "Does not use the full competitor-offer response matrix as the primary deliverable",
        "Does not force price match, CVR diagnostics, or competitor monitoring workflow for a pure content request",
        "May give blog titles or ask clarifying questions appropriate to content marketing"
      ]
    }
  ]
}


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)