Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add assimovt/productskills --skill competitor-analysisgit clone --depth 1 https://github.com/assimovt/productskillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/assimovt/productskills/competitor-analysis)<a href="https://agentmods.dev/skills/assimovt/productskills/competitor-analysis"><img src="https://agentmods.dev/badge/skills/assimovt/productskills/competitor-analysis/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/assimovt/productskills/competitor-analysis"><img src="https://agentmods.dev/badge/skills/assimovt/productskills/competitor-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00041 | $0.00716 |
| Opus 5 | $0.00020 | $0.00358 |
| Sonnet 5 | $0.00008 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
competitor-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze competitors to find positioning gaps, not to copy features. The goal is to understand where alternatives fail your ICP so you can win on what matters to them.
Identify All Alternatives
List every alternative your ICP considers. Three categories:
- Direct competitors: Products that solve the same problem for the same audience.
- Indirect competitors: Products that solve the problem differently or serve an adjacent audience.
- Non-consumption: "Do nothing" and "manual workaround" (spreadsheets, email, hiring someone). ALWAYS include these — they're often the biggest competitor.
Feature Matrix
Build a comparison table focused on what YOUR ICP cares about, not every feature that exists.
| Capability | Your Product | Competitor A | Competitor B | Manual Workaround |
|---|---|---|---|---|
| [ICP-relevant capability] | How you do it | How they do it | How they do it | How people hack it |
Rate each: Strong / Adequate / Weak / Missing. Don't use checkmarks — they hide nuance. Include pricing model in the matrix — it constrains product decisions.
Example row: | Real-time collaboration | Strong (live cursors) | Weak (polling-based) | Missing | Google Docs + Slack — Adequate | So what: Their users are duct-taping two tools; our strength is their pain point.
Positioning Map
Plot competitors on two axes that matter to your ICP. Choose axes where you can credibly win at least one.
Common axis pairs:
- Ease of use vs Power/flexibility
- Speed to value vs Depth of solution
- Price vs Completeness
- Self-serve vs White-glove
The empty quadrant is your opportunity. If no quadrant is empty, you need a different framing.
Example (project management tools, ICP = small remote teams):
Powerful
|
Jira ------+------ Linear
|
Easy ----------------+---------------- Hard
|
Trello -----------+------ Asana
|
Simple
Empty quadrant: Powerful + Easy. That's the opportunity.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 80 lines · 41 tokens per session scan A 6b46ca7d0793
competitor-analysis is a skill published in the GitHub repository assimovt/productskills (68 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 716 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
prd-taskmaster
Zero-config goal-to-tasks engine (the Atlas engine). Takes any goal (software, pentest, business, learning), runs adaptive discovery via brainstorming, generates a validated spec, parses into TaskMaster tasks, and hands off to execution. Use when user says "PRD", "product requirements", "I want to build", invokes…
handoff
Phase 3 of the prd-taskmaster pipeline: smart mode selection and user handoff. Detects installed capabilities (superpowers, ralph-loop, task-master-ai, playwright, research providers), recommends ONE execution mode (A/B/C) with reasoned justification, appends the task-execution workflow to CLAUDE.md, surfaces a…
generate
Phase 2 of the prd-taskmaster pipeline: spec generation and task parsing. Loads a template (comprehensive|minimal), fills it with DISCOVER-phase constraints and answers, validates the spec (placeholdersfound, grade thresholds), parses the PRD into tasks via task-master, runs TaskMaster's native complexity analysis…
customise-workflow
Customise the prd-taskmaster plugin workflow via curated brainstorm questions. The AI asks, the user answers in plain English, and the skill writes their preferences to .atlas-ai/config/atlas.json. Future runs of prd-taskmaster read that file and apply user preferences to phase gates, validation strictness, default…
discover
Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the…
execute-fleet
Phase execution skill for licensed Atlas Fleet runs. Use when HANDOFF has selected Atlas Fleet and the project should be executed across isolated launcher worktrees with inbox-based result collection, verified CDD cards, sequential integration merges, and one final PR.