competitor-intel
by ognjengtcompetitor-intel is a research-first skill for Competitive Analysis that uses web research to verify competitor signals, surface likely strengths and weak points, and suggest actionable leverage. Use the competitor-intel skill when you need evidence before pricing, messaging, GTM, or market positioning decisions.
This skill scores 78/100, which means it is a solid listing candidate for directory users who want a competitor-intelligence workflow that is more specific than a generic prompt. The repository gives enough operational guidance to trigger the skill, understand its expected inputs, and see that it is intended for real web-based research and actionable analysis rather than a placeholder.
- Clear trigger and scope: the frontmatter explicitly says to use it for competitive intelligence, competitor analysis, market positioning, and strategic leverage opportunities.
- Operational workflow is concrete: it tells the agent to check $ARGUMENTS, request missing competitor context, then run a mandatory web research phase.
- Trust signals are strong enough for adoption: the content emphasizes verified business metrics, no assumptions, no made-up numbers, and includes structured execution logic with constraints.
- Some implementation details are truncated in the provided excerpt, so users may still need to inspect the full SKILL.md for the complete research workflow.
- No supporting scripts, references, resources, or install command are present, so reliability depends entirely on the instructions in SKILL.md.
Overview of competitor-intel skill
competitor-intel is a research-first skill for Competitive Analysis when you need verified competitor signals, not generic positioning advice. It helps you turn a competitor name, website, or market segment into a data-backed read on business metrics, likely strengths, weak points, and next moves. The competitor-intel skill is best for founders, product leads, marketers, and operators who need evidence before making a pricing, messaging, or GTM decision.
What competitor-intel is best at
Use competitor-intel when you want grounded competitive intelligence: who the competitor is, what they likely sell, how they market, and where leverage may exist. It is strongest when the target has a public web footprint and enough external signals to verify.
When this skill is a good fit
Choose this skill if you need competitor-intel for Competitive Analysis, market positioning, sales prep, or launch planning. It is useful when you have a real competitor name plus context such as industry, website, region, or the question you are trying to answer.
What makes it different
The skill is designed around web research and explicit execution logic, so it can wait for missing inputs or proceed when the request is complete. Its value is in reducing guesswork: it prioritizes observable evidence over assumptions and pushes toward actionable leverage, not just summary.
How to Use competitor-intel skill
Install and activate competitor-intel
Use the competitor-intel install workflow in your skills manager, or install from the repo with npx skills add ognjengt/founder-skills --skill competitor-intel. After installation, trigger the skill with a competitor name and enough context to scope the research. If you send no arguments, the skill is meant to acknowledge loading and wait for details.
Give inputs the skill can actually research
Strong input looks like: Analyze Notion for pricing and messaging against smaller B2B AI note-taking tools. Focus on conversion angles and likely weak spots. Weak input looks like: Tell me about Notion competitors. The first gives the skill a competitor, category, and decision lens; the second forces broad, low-signal output.
Read the right files first
Start with SKILL.md, then inspect any repo-level context the skill points to, especially FOUNDER_CONTEXT.md if it exists. Because this repo has no supporting rules/, resources/, or scripts, the main decision logic is in the skill file itself. That makes the opening instructions and task sections the key parts to read before you rely on the output.
Use a workflow that matches the task
For best competitor-intel usage, pass: competitor name, website, industry, target market, and the specific question you need answered. Ask for one decision at a time if possible, such as pricing risk, messaging gaps, distribution channels, or feature parity. That keeps the analysis focused and improves the quality of leverage recommendations.
competitor-intel skill FAQ
Is competitor-intel only for big strategic audits?
No. It is also useful for faster, narrower questions like pre-sales prep, objection handling, launch positioning, or a quick scan before a product meeting. The skill is built for web-based competitive analysis, so the depth can scale with the question.
Do I need to provide a website or just a name?
A name is enough to start, but a website, product category, or geography makes the research much more reliable. The more ambiguous the name, the more likely you are to get wasted effort or wrong matches.
How is this better than a normal prompt?
A normal prompt often produces a polished but shallow summary. competitor-intel is structured to wait for or extract the right inputs, check optional company context, and force a research phase that supports evidence-based conclusions for competitor-intel for Competitive Analysis.
When should I not use this skill?
Do not use it when you only need a quick opinion, a private/internal competitor with no public footprint, or a task that cannot be researched from web signals. In those cases, a simpler briefing prompt or internal analysis may be faster and more honest.
How to Improve competitor-intel skill
Provide the decision you are making
The best way to improve competitor-intel is to state the decision behind the request: pricing change, positioning update, outbound angle, feature prioritization, or launch timing. That tells the skill what evidence matters and prevents a generic competitor profile.
Add context that changes interpretation
Include your own product category, target customer, region, and what you believe your differentiator is. If FOUNDER_CONTEXT.md exists, keep it current so the skill can compare competitors against your actual strengths instead of a vague market idea.
Ask for one output shape at a time
If the first pass is too broad, narrow the next request to one artifact: a leverage memo, messaging gaps, top risks, or predicted moves. This is often the difference between a surface-level competitor-intel guide and a decision-ready brief.
Watch for shallow evidence and refine
If the result feels speculative, improve the input by naming the exact competitor site, adjacent competitors, and the evidence you want cited or summarized. The main failure mode is underspecified scope; the fix is usually a tighter brief, not a different prompt.