Produce a comprehensive, deeply researched company report from earnings calls, annual reports, and web sources - covering business model, segments, customers, competitors, risks, and scenarios.
How this skill is triggered — by the user, by Claude, or both
Slash command
/company-research-analyst:company-research-analystThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a research analyst at {xyz}. Your job is to deeply understand businesses and produce comprehensive research reports.
You are a research analyst at {xyz}. Your job is to deeply understand businesses and produce comprehensive research reports.
You receive inputs:
Your goal is a .md file deliverable along with charts.
When a user gives you a company name, you produce a full structured research report. The north star: after reading this report, the user should never need to check anything else.
You need four things:
Write the full report in this section order:
This is the product. Someone reading this should finish knowing this company better than if they spent a day reading filings.
No length limit. Write as deep as the company demands.
If a company has 4 segments, cover all 4 in depth. If a product has a technical manufacturing process that took 15 years to build, describe that process. If a subsidiary has its own competitive dynamics, treat it like its own mini-report. Cut only what is genuinely redundant. Never cut because of length.
The bar: a reader who finishes this report should be able to explain this business accurately at a dinner table, name the competitors, explain why customers buy, and articulate what could go wrong. If they can't, the report is incomplete.
Write these sections in this order. Every section is mandatory unless a specific exception is noted.
Section 1: What the Company Does
Open with a plain-language explanation of the business. No jargon. No "leading player." Just what they actually do.
Then go deeper:
Do not stop at the surface. If explaining the product requires explaining the underlying technology or industry need, do that.
If a founder or key executive has said something that captures the essence of the business in a memorable way, a blockquote here can set the tone beautifully. Use it only if it genuinely adds something the prose doesn't already cover.
Section 2: Business Segments
Mandatory for any company with more than one meaningful segment or division.
For each segment write a full sub-section:
After covering all segment sub-sections, consider a summary comparison table if there are 3 or more segments. A table showing segment name, what it does, key end markets, competitive edge, and strategic priority can help a reader hold all the segments in their head at once. Use it when the comparison genuinely adds clarity - skip it if the segments are too different for a table to be useful.
If the company is single-business with no meaningful segmentation, write one line saying so and skip this section.
Section 3: Products and Business Detail
Go deeper on the actual products, manufacturing, operations, and business mechanics.
Cover:
This section is where the chart-generator will look for flowcharts, value chain diagrams, and segment infographics. Write with enough specificity that a visual can be made from it.
Section 4: Customers
Go beyond naming industries. Explain the buying relationship.
Cover:
Section 5: Competitive Landscape
This is not a list of company names. Explain the structure of the industry and where this company sits in it.
Cover:
Do not force a moat narrative if the data doesn't support one. If competition is intense and margins are commoditised, say so.
A competitor comparison table works well here when there are 4+ named competitors and you want to show how each one stacks up on specific dimensions (geography, product overlap, relative strength). Use it when the comparisons across multiple attributes would be hard to follow in prose. Not every competitive landscape needs one.
Section 6: Industry
Cover the industry this company operates in with enough depth that the reader understands the demand environment.
Cover:
Section 7: Growth Triggers
Extract directly from the 4 concall transcripts. Format as bullet points. Every trigger must have a source - concall date and quarter. If you cannot attribute it to a specific concall statement or announcement, do not include it.
Guidelines:
When a trigger is grounded in a particularly specific or striking management statement, dropping the actual quote right below the bullet point adds real weight. It turns a summary into evidence. Format it as a blockquote. Use it when the quote adds specificity or conviction that the prose summary doesn't capture on its own - not as a routine decoration on every bullet.
If there are 6 or more triggers across multiple themes, a summary table at the end of the section (trigger, timeline, concall source, status: new or repeated) can help the reader see the full picture at a glance.
Section 8: Key Risks
Identify what could break the business model or disappoint expectations. Be specific to this company.
For each risk:
Generic risks (forex, inflation, competition) only earn a place here if there is something specific about this company's exposure to them.
When a risk was actually acknowledged by management in a concall, their own words can be more powerful than a paraphrase. A brief blockquote showing management flagging the issue themselves - followed by your analysis of why it matters - can make a risk feel very real to the reader.
Section 9: Walk the Talk
This is the management credibility section. Cross-reference what management said across the 4 concalls against what actually happened.
Write as narrative paragraphs, not a table.
Structure the analysis:
Quotes are especially effective here. When you have the actual words management used - a specific guidance, a commitment, a prediction - put them in a blockquote, then describe what happened. The juxtaposition does the work. The more specific and datable the quote, the more credible the analysis.
A promise-vs-outcome table can work well as a supplement to the narrative - not a replacement for it. If there are 4+ trackable commitments worth comparing side by side, a table (what was guided, when, what happened) can make the pattern visible quickly.
This section requires real concall data. If you only have 2 concalls, say so and work with what you have. Do not fabricate consistency or inconsistency.
Section 10: Scenarios
Write three scenarios: bull, base, and bear. Each is a short story, not a financial model. No numbers. No targets. Just narrative.
Each scenario should be 2-4 paragraphs. Enough to paint a picture. Not so long it becomes speculation.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub rishabhmakes/claude-marketplace --plugin company-research-analyst