← ConsultorCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Consultor
Snapshot Sep 30, 2026 · 23:14 UTC · version 0.1.2
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Research and structure competitors, alternatives, substitutes, claims, pricing, channels, proof, positioning openings, and source-backed market comparisons.",
"included_files": [],
"name": "competitive-research",
"skill_md_contents": "---\nname: competitive-research\ndescription: Research and structure competitors, alternatives, substitutes, claims, pricing, channels, proof, positioning openings, and source-backed market comparisons.\ncompatibility: Requires Python 3.11+ only when using the optional bundled table helper.\n---\n\n# Competitive Research\n\nResearch the competitive landscape only when a strategy decision depends on external market reality.\n\nDo not invent competitors, pricing, claims, channels, traction, customer segments, or weaknesses.\n\nUse current external research when needed. Prefer primary sources:\n\n- Competitor websites.\n- Pricing pages.\n- Product pages.\n- Official documentation.\n- App marketplace listings.\n- Public case studies.\n- Public customer reviews when relevant.\n\nAsk one question at a time if the research scope is unclear.\n\n## Evidence Rules\n\nEvery competitor claim must be labeled:\n\n- Verified: directly observed in a cited source.\n- Assumption: inferred from available evidence but not directly stated.\n- Hypothesis: plausible but requires validation.\n\nFor web research, cite URLs in the response and record them in the live document.\n\nNever present scraped or recalled pricing as current unless it has been checked during this task.\n\nWhen competitor pricing becomes central to the decision, hand off to `pricing-strategy` after collecting source-backed pricing evidence.\n\n## Competitive Set\n\nSeparate:\n\n- Direct competitors: same category, similar buyer, similar job.\n- Indirect competitors: different solution, same job.\n- Substitutes: workaround, manual process, agency, spreadsheet, internal team, doing nothing.\n- Non-consumption: the buyer currently accepts the pain or ignores the job.\n\n## What To Extract\n\nFor each relevant competitor or alternative:\n\n- Name.\n- URL.\n- Category.\n- Target audience.\n- Core claim.\n- Offer.\n- Pricing.\n- Pricing basis if observable.\n- Proof.\n- Channels or acquisition clues.\n- Strength.\n- Weakness or opening.\n- Evidence status.\n- Source.\n\n## Live Documents\n\nUse or create these documents only when there is real content to record:\n\n- `consultor/strategy/competitive-research.md`\n- `consultor/strategy/competition.md`\n- `consultor/strategy/pricing-strategy.md`\n- `consultor/strategy/positioning.md`\n- `consultor/marketing/messaging.md`\n- `consultor/assumptions.md`\n- `consultor/risks.md`\n\nUse the shared [`competitive-research.md`](../../templates/competitive-research.md) template when creating a new research document.\n\n## Research Output\n\nPrefer a concise table plus notes:\n\n```text\nCompetitor | Type | Audience | Claim | Offer | Pricing | Proof | Opening | Evidence | Source\n```\n\nWhen the user provides CSV or loose notes, use the table helper:\n\n```bash\npython3 ../../scripts/consultor_competitive_table.py <input-file>\n```\n\nResolve the script path relative to this `SKILL.md` file before running it.\n\nUse `--stdout` when the user wants to see the normalized table in chat.\n\nAfter the table, add:\n\n- Positioning implications.\n- Messaging implications.\n- Risks.\n- Open questions.\n- Validation steps.\n\n## Done Threshold\n\nPause when the decision has enough competitive context to choose or challenge category, alternative, differentiation, proof, pricing, channel, or next validation step.\n"
}SHA-256 of public snapshot: d3e4e5380d36654340acc44b47dd369bcf96cb4099857235d8710aa12c7456ce