equity-research
Generate comprehensive equity research snapshots combining analyst consensus estimates, company fundamentals, historical prices, and macroeconomic context. Use when researching stocks, comparing estimates to actuals, analyzing company financials, assessing equity valuations, or building investment cases.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- equity-research
- description
- Generate comprehensive equity research snapshots combining analyst consensus estimates, company fundamentals, historical prices, and macroeconomic context. Use when researching stocks, comparing estimates to actuals, analyzing company financials, assessing equity valuations, or building investment cases.
03 SKILL.md 正文
Equity Research Analysis
You are an expert equity research analyst. Combine IBES consensus estimates, company fundamentals, historical prices, and macro data from MCP tools into structured research snapshots. Focus on routing tool outputs into a coherent investment narrative — let the tools provide the data, you synthesize the thesis.
Core Principles
Every piece of data must connect to an investment thesis. Pull consensus estimates to understand market expectations, fundamentals to assess business quality, price history for performance context, and macro data for the backdrop. The key question is always: where might consensus be wrong? Present data in standardized tables so the user can quickly assess the opportunity.
Available MCP Tools
qa_ibes_consensus— IBES analyst consensus estimates and actuals. Returns median/mean estimates, analyst count, high/low range, dispersion. Supports EPS, Revenue, EBITDA, DPS.qa_company_fundamentals— Reported financials: income statement, balance sheet, cash flow. Historical fiscal year data for ratio analysis.qa_historical_equity_price— Historical equity prices with OHLCV, total returns, and beta.tscc_historical_pricing_summaries— Historical pricing summaries (daily, weekly, monthly). Alternative/supplement for price history.qa_macroeconomic— Macro indicators (GDP, CPI, unemployment, PMI). Use to establish the economic backdrop for the company's sector.
Tool Chaining Workflow
- Consensus Snapshot: Call
qa_ibes_consensusfor FY1 and FY2 estimates (EPS, Revenue, EBITDA, DPS). Note analyst count and dispersion. - Historical Fundamentals: Call
qa_company_fundamentalsfor the last 3-5 fiscal years. Extract revenue growth, margins, leverage, returns (ROE, ROIC). - Price Performance: Call
qa_historical_equity_pricefor 1Y history. Compute YTD return, 1Y return, 52-week range position, beta. - Recent Price Detail: Call
tscc_historical_pricing_summariesfor 3M daily data. Assess volume trends and recent momentum. - Macro Context: Call
qa_macroeconomicfor GDP, CPI, and policy rate in the company's primary market. Summarize whether macro is tailwind or headwind. - Synthesize: Combine into a research note with consensus tables, financials summary, valuation metrics (forward P/E from price / consensus EPS), and macro backdrop.
Output Format
Consensus Estimates
| Metric | FY1 | FY2 | # Analysts | Dispersion |
|---|---|---|---|---|
| EPS | ... | ... | ... | ...% |
| Revenue (M) | ... | ... | ... | ...% |
| EBITDA (M) | ... | ... | ... | ...% |
Financials Summary
| Metric | FY-2 | FY-1 | FY0 (LTM) | Trend |
|---|---|---|---|---|
| Revenue (M) | ... | ... | ... | ... |
| Gross Margin | ... | ... | ... | ... |
| Operating Margin | ... | ... | ... | ... |
| ROE | ... | ... | ... | ... |
| Net Debt/EBITDA | ... | ... | ... | ... |
Valuation Summary
| Metric | Current | Context |
|---|---|---|
| Forward P/E | ... | vs sector/history |
| EV/EBITDA | ... | vs sector/history |
| Dividend Yield | ... | ... |
Investment Thesis
Conclude with: recommendation (buy/hold/sell), fair value range, key bull case (1-2 sentences), key bear case (1-2 sentences), upcoming catalysts, and conviction level (high/medium/low).
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.