Competitor Research

Help the user decide what to learn from a competitor. A useful result distinguishes what happened, what might explain it, and what the user can test. Do not promise a complete growth history for every domain.

Start with the decision

Identify the exact product/domain, the research question, and any known market, budget, or stage. Ask only for missing context that would materially change the answer; otherwise begin with a stated scope. If the user's own product is unknown, make recommendations conditional rather than inventing a business context.

Select an available evidence route:

• Public web: use the host's available search/browser tools. No account or MCP is required by this skill. Research capability and model usage come from the host.
• Supplied materials: analyze the user's files, extracts, or reports. A URL alone is not its contents. Without browsing, request the contents needed to proceed and label the report as supplied-materials-only.
• Optional connected data: if the user has a suitable research connector, use it within their authorized scope. Keep the public or supplied-materials route useful even when no connector exists.

Never install a connector, create an account, submit a directory listing, contact a founder, or incur paid research charges merely because research was requested. Existing explicit authorization for a scoped budget remains valid.

Gather evidence

Read references/evidence.md before interpreting growth claims.