Research Company
When To Use
Use this skill when the user provides a company name, domain, or website URL and asks for a company summary, company research, business profile, or structured findings.
Inputs
- Target company name or website URL.
- Any user-provided focus areas, such as products, market, customers, pricing, leadership, or positioning.
If the user gives only a company name, identify the official website before scraping. If there are multiple plausible companies, ask a brief clarifying question.
Workflow
Open the official company website. Prefer the homepage, then inspect likely high-signal pages such as About, Products, Services, Solutions, Customers, Pricing, Blog, Careers, Contact, and Terms/Privacy when available.
Extract relevant page text and metadata. Capture concise evidence for:
- What the company does.
- Primary products or services.
- Target customers, industries, or use cases.
- Differentiators, positioning, or claims.
- Company location, leadership, funding, or team details if present on the site.
- Notable calls to action, pricing signals, or contact channels.
Use an LLM to synthesize the gathered material into neutral, factual language. Prioritize information directly supported by the website and do not invent missing facts.
Read templates/summary.md and produce the final response in that exact structure:
- Replace every placeholder with concise, website-supported content.
- Use
Not found on the website for fields that cannot be supported by available website content.
- Keep
<EXECUTIVE_SUMMARY> to 2-4 sentences.
- Keep
<COMPANY_SUMMARY> to one concise paragraph explaining what the company does and the most important supporting details from the website.
- Use the caveats section for ambiguity, sparse evidence, inaccessible pages, or analyst inference.
Quality Bar
- Cite the company website URL in the summary text when useful.
- Keep the summary concise and avoid raw scraped dumps.
- Separate observed facts from inference.
- Mention uncertainty when the website is sparse, inaccessible, or ambiguous.
- Do not use unrelated sources unless the user asks for broader research.
Edge Cases
- If the website is inaccessible or blocks retrieval, explain the limitation and summarize only accessible content.
- If the site is not in English, translate only enough to produce the requested summary and state that the source site was in another language.
- If the website has no clear company description, report that clearly rather than guessing.
1---2name: research-company3description: Research a target company by navigating and reviewing the company's website, extract key business information, and use an LLM to produce a structured summary in templates/summary.md. Use when the user asks to research, profile, summarize, or analyze a company from its website.4---56# Research Company78## When To Use910Use this skill when the user provides a company name, domain, or website URL and asks for a company summary, company research, business profile, or structured findings.1112## Inputs1314- Target company name or website URL.15- Any user-provided focus areas, such as products, market, customers, pricing, leadership, or positioning.1617If the user gives only a company name, identify the official website before scraping. If there are multiple plausible companies, ask a brief clarifying question.1819## Workflow20211. Open the official company website. Prefer the homepage, then inspect likely high-signal pages such as About, Products, Services, Solutions, Customers, Pricing, Blog, Careers, Contact, and Terms/Privacy when available.22232. Extract relevant page text and metadata. Capture concise evidence for:24 - What the company does.25 - Primary products or services.26 - Target customers, industries, or use cases.27 - Differentiators, positioning, or claims.28 - Company location, leadership, funding, or team details if present on the site.29 - Notable calls to action, pricing signals, or contact channels.30313. Use an LLM to synthesize the gathered material into neutral, factual language. Prioritize information directly supported by the website and do not invent missing facts.32334. Read `templates/summary.md` and produce the final response in that exact structure:34 - Replace every placeholder with concise, website-supported content.35 - Use `Not found on the website` for fields that cannot be supported by available website content.36 - Keep `<EXECUTIVE_SUMMARY>` to 2-4 sentences.37 - Keep `<COMPANY_SUMMARY>` to one concise paragraph explaining what the company does and the most important supporting details from the website.38 - Use the caveats section for ambiguity, sparse evidence, inaccessible pages, or analyst inference.3940## Quality Bar4142- Cite the company website URL in the summary text when useful.43- Keep the summary concise and avoid raw scraped dumps.44- Separate observed facts from inference.45- Mention uncertainty when the website is sparse, inaccessible, or ambiguous.46- Do not use unrelated sources unless the user asks for broader research.4748## Edge Cases4950- If the website is inaccessible or blocks retrieval, explain the limitation and summarize only accessible content.51- If the site is not in English, translate only enough to produce the requested summary and state that the source site was in another language.52- If the website has no clear company description, report that clearly rather than guessing.
gabepublic