plugins/daloopa/skills/guidance-tracker/SKILL.md
Track management guidance accuracy over time for a given company
npx skillsauth add openai/plugins guidance-trackerInstall 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.
Track management guidance accuracy for the company named in the user's request. If no ticker or company is provided, ask for one before proceeding.
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 company by ticker using discover_companies. Capture:
company_idlatest_calendar_quarter — anchor for all period calculations below (see ../data-access.md Section 1.5)latest_fiscal_quarter../data-access.md Section 4.5Search for series with keywords like "guidance", "outlook", "estimate", "forecast", "target" to find all available guidance metrics. Common guidance series include:
Financial guidance:
Operational KPI guidance — many companies guide on KPIs, and tracking these beats/misses is often more informative than financial guidance:
Search explicitly for KPI-specific guidance series using terms like "subscriber guidance", "unit guidance", "ARPU guidance", "same-store sales outlook", "deliveries forecast", "bookings target". These are separate from financial guidance and often reside in different series.
Calculate 8+ quarters backward from latest_calendar_quarter. Pull all discovered guidance series for those periods.
For each guidance metric, pull the corresponding actual result series for the same periods.
CRITICAL OFFSET RULES:
For each guidance-actual pair, calculate:
Analyze the guidance track record:
Management credibility assessment:
Search SEC filings/documents across multiple queries to build a complete picture of guidance practices. If any search returns empty, try alternative keywords before giving up.
Extract direct management quotes where available and cite the document source.
When a company raises, cuts, or materially changes its guidance, the implications often matter more for adjacent names than for the company itself. This section translates guidance signals into actionable read-throughs.
For each major guidance change identified in the tracker, analyze the implications for adjacent companies:
Identify who is affected by this company's guidance:
For each read-through (aim for 4-6), state:
Focus on the highest-signal guidance changes:
Example:
Web research for validation:
Run 1 targeted search: "{TICKER} guidance change implications read through {year}" — analyst commentary on cross-company signals from guidance moves.
Present as a structured section in the report after the Pattern Analysis, grouped by guidance change (each major guide raise/cut gets its own sub-block with the read-throughs beneath it).
Save to reports/{TICKER}_guidance_tracker.html 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:
| Guidance Source Quarter | Guidance Applies To | Actual Result Quarter |
| CQ1 2024 | CQ2 2024 | CQ2 2024 |
| CQ2 2024 | CQ3 2024 | CQ3 2024 |
This makes the offset rule visible and auditable for every row in the tracker.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.
Highlight the key patterns (e.g., "Management has beat revenue guidance 7 of the last 8 quarters by an average of 2.3%"). Include an honest credibility verdict: Is management's guidance informative or performative? Should investors trust the forward guidance, and if not, what should they anchor to instead?
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.