Borrowing it
Nothing to install: this file belongs to LeanOS-Technologies/strategy-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/LeanOS-Technologies/strategy-os/main/.claude/skills/stg-analyzing-competition/SKILL.mdgit clone --depth 1 https://github.com/LeanOS-Technologies/strategy-osWrote 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/leanos-technologies/strategy-os/stg-analyzing-competition)<a href="https://agentmods.dev/skills/leanos-technologies/strategy-os/stg-analyzing-competition"><img src="https://agentmods.dev/badge/skills/leanos-technologies/strategy-os/stg-analyzing-competition/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/leanos-technologies/strategy-os/stg-analyzing-competition"><img src="https://agentmods.dev/badge/skills/leanos-technologies/strategy-os/stg-analyzing-competition.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.00040 | $0.01430 |
| Opus 5 | $0.00020 | $0.00715 |
| Sonnet 5 | $0.00008 | $0.00286 |
| Haiku 4.5 | $0.00004 | $0.00143 |
Grade A, and why
stg-analyzing-competition 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 9d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Analysis
Map competitive landscape, identify positioning gaps, and assess competitor response capability. All competitive claims carry tier labels. Output feeds hypothesis evidence across the register.
Procedure
Step 1: Build Competitive Frame [K-grounded]
Grounded in: problem candidates, segment candidates.
Define competitive frame from problem + segment intersection. Competition is framed by what problems you solve for whom, not by technology similarity.
Produce: competitive frame definition (problem domain x target segment = competitive arena).
Gate: frame_defined: bool -- competitive frame states problem and segment, not just technology category.
- Pass: Step 2.
- Fail: If problem/segment not yet defined, use governor's problem space as initial frame. Note that competitive frame may need revision after hypothesis construction.
Step 2: Identify Direct Competitors [S]
WebSearch for companies solving the same problem for the same segment.
Search strategies:
- "[Problem] software"
- "[Problem] solution for [segment]"
- "Alternative to [known competitor]"
- G2/Capterra category pages
- Product Hunt searches
- Crunchbase industry filters
Data sources: G2, Capterra, Product Hunt, Crunchbase, company websites.
For each competitor:
- Positioning (headline/tagline from website)
- Target segment (from marketing copy)
- Pricing model (from pricing page)
- Key differentiators (from feature pages)
All claims cite source URL. Label T1 (directly observable on website).
Produce: direct competitor profiles.
Gate: direct_competitors_identified: bool -- at least 3 direct competitors identified with source URLs, or documented that fewer exist with evidence of search exhaustion.
- Pass: Step 3.
- Fail: Widen search. Try adjacent categories, broader problem framing. If genuinely no direct competitors, document: "No direct competitors found -- this is either a new category or the search missed them."
Step 3: Identify Indirect Competitors [R]
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.
- 9d ago First seen · 138 lines · 40 tokens per session scan A 0ccf3cf16a0f
stg-analyzing-competition is a skill published in the GitHub repository LeanOS-Technologies/strategy-os (37 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 1,430 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
llm-app-patterns
Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.
email-sequence
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle…
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
gepetto
Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
guidance
Control LLM output with regex and grammars, guarantee valid JSON/XML/code generation, enforce structured formats, and build multi-step workflows with Guidance - Microsoft Research's constrained generation framework.
content-research-writer
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.