← PrePilot LiteCONTENT HISTORY

Update to PrePilot Lite

Snapshot Sep 30, 2026 · 23:14 UTC · version 0.1.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use when the user wants competitor research, category analysis, positioning comparison, offer comparison, content or channel gaps, battlecards, alternative pages, or a market narrative scan.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 245
    }
  ],
  "name": "competitive-intelligence",
  "skill_md_contents": "---\nname: competitive-intelligence\ndescription: Use when the user wants competitor research, category analysis, positioning comparison, offer comparison, content or channel gaps, battlecards, alternative pages, or a market narrative scan.\n---\n\n# Competitive Intelligence\n\n## Use it for\n\n- Competitor profiling\n- Category and narrative mapping\n- Offer, pricing, message, channel, SEO, or content comparison\n- Building battlecards or alternative-page evidence\n\n## Operating rules\n\n- Use context already present in the conversation before asking for more input.\n- Separate known facts, reasonable assumptions, and unknowns. Do not present assumptions as evidence.\n- When the answer depends on current platform rules, market conditions, pricing, benchmarks, or competitors, verify them with current sources when tools are available.\n- Prefer concrete decisions, examples, and next actions over generic marketing advice.\n- Do not invent campaign performance, customer quotes, research findings, testimonials, rankings, or competitor claims.\n- Keep the requested market, language, funnel stage, audience awareness, budget, and channel constraints visible throughout the work.\n- Compare competitors on the same criteria.\n- Use current public evidence when the request concerns live competitor behavior.\n- Do not infer revenue, spend, traffic, or performance without a source.\n- Treat absence of evidence as unknown, not weakness.\n\n## Workflow\n\n1. Define the decision the comparison must inform.\n2. Select a small set of direct competitors, substitutes, and the status quo when relevant.\n3. Collect comparable evidence for audience, promise, proof, offer, pricing, experience, channels, and visible acquisition patterns.\n4. Separate parity, meaningful advantage, unproven claim, and open territory.\n5. Translate findings into specific strategic choices and watch items.\n\n## Output contract\n\n- Comparison matrix\n- Narrative and claim map\n- Opportunity list ranked by evidence and strategic fit\n- Risks and items requiring verification\n\n## Quality gate\n\n- Every important observation points to evidence\n- No vanity feature-counting\n- Recommendations explain why the user can credibly own the territory\n- Current claims include dates or source recency when material\n\n## Sales battlecard mode\n\nWhen the request is for a competitive battlecard, keep it usable during a sales conversation. Include the competitor's current position, the few dimensions that matter to the buyer, where the user's offer is stronger, where the competitor is stronger, evidence-backed objection responses, and observable win/loss patterns when data exists. Never invent weaknesses, customer quotes, funding, pricing, or win rates. Unknowns stay unknown.\n\n## Handoff\n\nIf the task is part of a larger marketing request, return the completed deliverable plus the evidence or decisions the next PrePilot skill needs. Do not repeat upstream analysis unless it changes the result.\n"
}

SHA-256 of public snapshot: 3e4eaf89ea56866be40d15342aca830185afb3395cec8a57d8f299e944e6fcc0