plugins/daloopa/skills/comp-sheet/SKILL.md
Build an industry comp sheet Excel model with deep operational KPIs
npx skillsauth add openai/plugins comp-sheetInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Build a multi-company industry comp sheet Excel model for the company named in the user's request. If no ticker or company is provided, ask for one before proceeding.
This produces an interactive .xlsx workbook — the kind of comp sheet every analyst on a coverage team maintains. Multi-company, multi-tab, with deep operational KPIs alongside standard financials.
Before starting, read ../data-access.md for data access methods and ../design-system.md for formatting conventions. Follow the data access detection logic and design system throughout this skill.
Follow these steps:
Look up the target company by ticker using discover_companies. Capture company_id, latest_calendar_quarter (anchor for all period calculations — see ../data-access.md Section 1.5), and latest_fiscal_quarter. Note the firm name for report attribution (default: "Daloopa") — see ../data-access.md Section 4.5.
Then identify 6-10 comparable companies using the same logic as the comps skill:
Look up all peer company_ids via Daloopa. If a peer isn't available in Daloopa, include it with market data only and note the limitation.
List the full peer group with brief justification for each.
For each company (target + all peers), pull from Daloopa:
Calculate 8 quarters backward from latest_calendar_quarter. Pull financials:
Segment revenue breakdown (all available segments, 8 quarters)
Company-specific operational KPIs — use the 9-sector taxonomy to know what to search for:
Stock prices & valuation multiples:
Use get_stock_prices (see ../data-access.md Section 1.7) to pull prices for ALL companies in a single batch call. Get:
dates = 3 most recent calendar days for all company_idsdates = quarter-end dates matching the financial periods (for historical multiples)Then compute valuation metrics by combining stock prices with Daloopa fundamentals:
For beta, use web search (see ../data-access.md Section 2). For forward multiples, use consensus estimates if available (Section 3).
After pulling data, build the KPI mapping:
For each company, calculate:
Margins:
Growth rates:
Capital metrics:
Historical multiples (from quarter-end prices pulled in Section 2):
Implied valuation:
Generate the Excel workbook directly as a local .xlsx file. For Codex, prefer bundled spreadsheet tooling or Python/openpyxl when available.
The workbook must contain 8 tabs with the following structure:
One-page overview with all companies side-by-side:
Unit economics decomposition per company (trailing 4 quarters):
Cross-company KPI comparison matrix:
Side-by-side income statements (trailing 4 quarters):
Trend analysis (up to 8 quarters):
Implied prices by methodology:
Leverage and capital returns:
Full quarterly appendix for each company:
Styling requirements:
../design-system.md conventionsThe workbook generation should:
.xlsx filereports/{TARGET_TICKER}_comp_sheet_{DATE}.xlsxAfter generating the Excel workbook, provide a concise summary highlighting:
Target positioning vs peers:
Most differentiated KPIs:
Implied valuation range:
Key risk:
All financial figures in the summary must use Daloopa citation format: $X.XX million
tools
Top-level workflow skill for USD performance diagnosis and optimization. Use for slow loading, high memory, low FPS, or 'optimize my scene' requests; delegates auth/runtime setup to Phase 0 owners.
data-ai
Use when the user mentions MagicPath, designs, UI components, themes, canvas selections, or repo-to-canvas UI work; run magicpath-ai to search, inspect, install, or author components.
documentation
Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents.
tools
Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.