{"id":99342,"plugin_id":"plugin_asdk_app_6af24ca3a618819184368ec28ad1a933","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-16T18:17:22.200Z","digest":"7f75e710fc9441d679124dd137bc9854e70cb5eeb4d54376cad7d66995e1b6c7","against":null,"payload":{"description":"\"revenue and cost drivers\", \"driver tree\", \"what moves the P&L\" — breaks a company's revenue and cost segments into their drivers via Samaya and renders an HTML relationship graph.","included_files":[],"name":"samaya-revenue-cost-drivers","skill_md_contents":"---\nname: samaya-revenue-cost-drivers\ndescription: >-\n  \"revenue and cost drivers\", \"driver tree\", \"what moves the P&L\" — breaks a company's revenue and\n  cost segments into their drivers via Samaya and renders an HTML relationship graph.\n---\n\n# Revenue and Cost Drivers (Visual)\n\n## Samaya rules\n- Use `financial_qa` for every lookup. If it returns `running`, poll `financial_qa_result` with the `job_id`. Never re-call for the same question.\n- Keep relative time wording (\"most recent quarter\") verbatim in the question.\n- `financial_qa` returns citations, not answers. Write your own answer from the snippets. Cite each source with its date and link.\n- If a source has no publication date, cite it as \"undated\". Never guess a date.\n- Batch related lookups into one call. Aim for 6-8 `financial_qa` calls per run.\n\n## Input\n- A company.\n- The period. It defaults to the most recent reported quarter.\n\n## Steps\n\n1. **Segments.** Call `financial_qa` for the period's revenue segments, cost lines and the rest of the P&L, with dollar values.\n   - Keep the 4 largest revenue lines and the 4 largest cost lines.\n   - Combine the remaining lines on each side into \"Other revenue\" or \"Other costs\", marked as calculated.\n   - Rest of the P&L, fixed list:\n     - Operating income\n     - Net interest and other\n     - Pretax income\n     - Tax\n     - Net income\n     - Diluted shares\n     - EPS\n\n2. **Formulas.** Write how each line is built from its inputs, for example: Passenger revenue = ASMs × Load factor × Yield. Mark each value as either \"reported\" (it appears in a filing) or \"calculated\".\n\n3. **Drivers.** Use one call for revenue drivers and one for cost drivers. Ask for each driver's current value and management's commentary on it.\n   - Sort each driver into Revenue driver, Capacity / supply, or Macro.\n   - Show each driver in the units the company reports it in (%, bp, units, price). Don't convert drivers to dollars.\n   - If some lines get no drivers back, make one follow-up call covering all of them.\n\n4. **Catalysts.** Ask for events that moved a macro driver during the period.\n   - Record the category (for example GEOPOLITICAL or MACRO), the status (confirmed or expected), and the impact.\n   - Tag any event dated after the period ended as \"POST-PERIOD\".\n   - A catalyst that doesn't move a macro driver may point straight to the P&L line it hits.\n\n5. **Takeaways.**\n   - The 3 main earnings takeaways from the most recent call.\n   - A 1-2 sentence main takeaway naming the driver that moved the quarter most.\n\n6. **Build the HTML** (layout below), then publish it with the Artifact tool.\n\n## HTML layout (from Scenario Analysis v3)\n\n- **Main takeaway:** 1-2 sentences at the top, above the takeaways strip.\n- **Header:**\n  - Logo tile, name, ticker, exchange and sector. Leave out any field Samaya didn't return. Never show \"—\".\n  - Title: \"Drivers of the [period] P&L\".\n  - Include a period selector or Export button only if it works. A CSV export is fine; label it \"CSV\".\n- **Takeaways strip:** 3 numbered one-line takeaways, labelled \"REPORTED · EARNINGS TAKEAWAYS\".\n- **Canvas:**\n  - Dotted-grid background.\n  - Columns from left to right: THE P&L, REVENUE DRIVERS, CAPACITY & SUPPLY, MACRO DRIVERS, PERIOD CATALYSTS.\n  - On load, scale the canvas to fit the window width so every column, including catalysts, is fully visible.\n  - Zoom controls: −, + and a % readout.\n- **Bands:**\n  - REVENUE: green tint, green label.\n  - COSTS: red tint, red label.\n  - REST OF THE P&L: neutral, laid out left to right in P&L order.\n- **Node card** (white, thin border, small radius):\n  - Status dot and name. Dot colours: grey = calculated, green = reported input, blue = headline output.\n  - Value in large monospace.\n  - A formula line in small monospace, or \"drives $X.XB\" (the size of the line the driver feeds).\n  - A citation line with a link icon, for example \"10-Q Q3'26A\", or \"Calculated — N inputs, not reported\".\n  - Optional commentary below a divider:\n    - At most 3 lines, with the full text on hover.\n    - A source line, for example \"Q3'26 call · CFO\".\n  - Badge \"ENT\" for entitled broker research.\n  - Footer \"ALSO IN COSTS\" or \"ALSO IN REVENUE\" for a driver that feeds both bands.\n  - Operating income, net income and EPS get a pink fill and a teal border.\n  - Two node heights only: with commentary and without.\n- **Edges:**\n  - Smooth curved grey lines (bezier) from each driver to the line it feeds, with the arrowhead pointing into the P&L.\n  - Draw the edge layer beneath the cards. Lines may pass behind cards.\n  - Give each incoming edge its own attachment point, spaced along the target card's edge, so arrowheads never stack.\n  - Line weight scales with the size of the line fed.\n- **Catalyst card:**\n  - Orange border.\n  - A category tag and a status tag, including \"POST-PERIOD\" where it applies.\n  - A one-line headline, the impact in orange monospace, and a short explanation.\n  - A dashed orange curved arrow to the driver or P&L line it moves.\n\nEvery value and commentary line carries its source and date. Leave a value blank rather than estimate it."},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}