plugins/daloopa/skills/industry/SKILL.md
Cross-company industry comparison across multiple tickers
npx skillsauth add openai/plugins industryInstall 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.
Perform an industry comparison across the companies named in the user's request. If no ticker or company is provided, ask for one before proceeding.
The user will provide multiple tickers separated by spaces (e.g., "AAPL MSFT GOOG AMZN").
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 all provided tickers using discover_companies. For each company, capture:
company_idlatest_calendar_quarter — use the earliest latest_calendar_quarter across all companies as the anchor for period calculations (see ../data-access.md Section 1.5)latest_fiscal_quarter../data-access.md Section 4.5Calculate 8 quarters backward from the anchor latest_calendar_quarter. For each company, find and pull these metrics:
Income Statement:
Cash Flow:
For any derived/computed metric, mark it with "(calc.)" so the reader knows it's not directly sourced.
First, think about what KPIs matter for the specific industry being compared. Use the full sector taxonomy to guide discovery:
For each company, discover and pull the most relevant KPIs. Note which KPIs are common across the group (apples-to-apples comparison) and which are unique to specific companies. For mixed-sector comparisons, focus on the KPIs that apply to the largest revenue segments of each company.
For each company, search the most recent 2 quarters of filings across multiple queries. If any search returns empty, try alternative keywords before giving up.
If a company returns sparse results across all searches, try broader single-keyword searches (e.g., just "competitive" or just "growth") and search additional periods.
For each company, extract:
Use these findings to enrich the rankings analysis — numbers tell you who's winning, filings tell you why.
Save to reports/{INDUSTRY_LABEL}_industry_comp.html (where INDUSTRY_LABEL is derived from the tickers, e.g., "AAPL_MSFT_GOOG_AMZN") using the HTML report template from ../design-system.md. Write the full analysis as styled HTML with the design system CSS inlined. This is the final deliverable — no intermediate markdown step needed.
The report should include:
All financial figures must use Daloopa citation format: <a href="https://daloopa.com/src/{fundamental_id}">$X.XX million</a>
Tell the user where the HTML report was saved.
Give a clear competitive verdict: Who is winning and who is losing? Which company has the strongest competitive position and why? Which company looks most vulnerable? Are any of the companies structurally mispriced relative to peers (too cheap or too expensive given the fundamentals)? Don't hedge — rank them honestly.
development
Use when the user wants to spin up / create / launch / provision a DigitalOcean droplet (or "a remote dev box on DO") and connect to it from Codex as a remote SSH workspace.
data-ai
Search through Microsoft Teams chats or channels, triage unread or recent activity, draft follow-ups, and manage Planner tasks through connected Teams data.
tools
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.
development
SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.