Compare products, libraries or approaches on criteria derived from your own constraints rather than from anyone's feature list, and fill each cell with evidence you obtained — hands-on trial, primary docs, source, issue tracker — marking clearly what is only a vendor claim. Use when choosing between real alternatives, when asked how something stacks up against the competition, or when a decision is being made from a marketing comparison table. Not for general investigation method, not for…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Competitive analysis
Whoever sets the criteria wins the comparison. If the criteria come from a vendor's feature matrix,
the analysis was decided before it started — and every row on that matrix was chosen because they
win it.
## When this fires
A choice between real alternatives has to be defended: a library, a service, a vendor, two designs,
build versus buy. It also fires when someone arrives with a comparison table and a conclusion. It
does not fire for a reversible choice nobody will revisit — make it and move on.
## Procedure
1. **State the decision and who makes it.** What gets adopted, by whom, and what changes the day
after. A comparison with no decision behind it becomes a feature table nobody reads.
2. **Derive the criteria from your own constraints, before opening any product page** — your actual
workload, scale, team skills, runtime, compliance and budget. Then weight them: must-have,
tie-breaker, irrelevant. Criteria written after reading the vendors are the vendors' criteria.
3. **Pick the comparison set honestly.** Include the status quo, "do nothing", and "build the small
…
The line at the top of this page pins the label git:20260919.a0d4f55, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_lxvbgrrmrtogb2im
GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/competitive-analysis
GET https://markdownregistry.com/api/v1/blob/7e29c74e380b6bcf49dca1512917caab4868c3d9bdd947cea2ec102ffcf00c1e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
nahid-sparktales/agent-dispatcher · skills/agent-dispatcher/SKILL.md · Handle requested Agent Dispatcher work with direct execution or prepared specialist guidance. Includes named roles…
nahid-sparktales/agent-dispatcher · skills/ai/agent-design/SKILL.md · Scope an agent or subagent before it is built — the one job it owns, the smallest tool set that closes that job, what…
nahid-sparktales/agent-dispatcher · skills/ai/agent-evals/SKILL.md · Build an eval suite that can actually detect a regression — cases pulled from real traffic, graders that check…
nahid-sparktales/agent-dispatcher · skills/ai/context-engineering/SKILL.md · Decide what actually occupies the model's window — progressive disclosure through an index, retrieval versus inlining…
nahid-sparktales/agent-dispatcher · skills/ai/llm-observability/SKILL.md · See what an agent actually did — one trace per run with nested model, tool and retrieval spans, token and latency…
nahid-sparktales/agent-dispatcher · skills/ai/mcp-design/SKILL.md · Build an MCP server, or bring an existing one into a project — choosing the transport, deciding which tools, resources…
nahid-sparktales/agent-dispatcher · skills/ai/memory-design/SKILL.md · Decide what an agent should remember, which layer holds it, who it is scoped to, and how a stale or contradicted memory…
nahid-sparktales/agent-dispatcher · skills/ai/model-routing/SKILL.md · Pick a model per job and degrade sensibly when one fails — a quality bar per call site, candidates compared on the same…
nahid-sparktales/agent-dispatcher · skills/ai/prompt-engineering/SKILL.md · Write or revise a prompt so it holds up — output contract, instruction placement, examples that earn their place, an…
nahid-sparktales/agent-dispatcher · skills/ai/prompt-injection-defense/SKILL.md · Treat everything an agent reads but did not author as data rather than instructions — an explicit trust boundary, a…
nahid-sparktales/agent-dispatcher · skills/ai/retrieval-rag/SKILL.md · Build and fix retrieval that actually returns the right passage — structure-aware chunking, one pinned embedding model…
nahid-sparktales/agent-dispatcher · skills/ai/structured-output/SKILL.md · Get parseable, trustworthy structured results out of a model — schema design, the enforcement mechanism the provider…
mohitagw15856/pm-claude-skills · i18n/es/skills/competitive-analysis/SKILL.md · Analiza competidores y crea documentación de panorama competitivo con matrices de características, mapas de…
yonatangross/orchestkit · plugins/ork/skills/competitive-analysis/SKILL.md · Porter's Five Forces, SWOT, competitor profiles, feature gaps and battlecards. Use when analyzing market position or…
mverab/egeoagents · .claude/skills/competitive-analysis/SKILL.md · Analyze AI-search competitors for a query and recommend ranking strategy. Use when users ask competitor analysis, who…
qa-aman/claude-skills · skills/by-role/pm/competitive-analysis/SKILL.md · Conduct a competitive analysis. Use when the user says "competitive analysis", "how do competitors handle X", "market…
