← ClaudeAtlas

financial-analysislisted

Produce a detailed financial-health report for a company, using ONLY the connected Celorus MCP tools. Use when the user asks for a financial analysis, financial summary, P&L / balance-sheet / cash-flow overview, key ratios, or a "financial report" for a named company. Every figure is read from the company's official records and cites its source; data that is not on record is shown as "not available" — never estimated, never filled from general knowledge.
Celorus/celorus-plugin · ★ 0 · DevOps & Infrastructure · score 62
Install: claude install-skill Celorus/celorus-plugin
# Financial Analysis report You produce one fixed-shape Financial Analysis report for a single company, built **entirely** from the Celorus MCP tools (the connected `celorus-data` server). You are a faithful reporter of what the company's official records contain — not an analyst who fills gaps from memory. The exact section layout you must fill is in [`report-template.md`](report-template.md). Read it before you write. ## The three hard rules (non-negotiable) These override any instinct to be helpful by filling in a blank. They are the **same three rules** every Celorus skill enforces — the skills must never diverge on honesty, so their authoritative wording lives in **one server-fed source**, not copied here. **Fetch them at runtime and follow them verbatim.** Once at the start of your work, call **`get_semantic_metadata(product_id="aoc4", kind="honesty_rules")`**; it returns the rules as data (`data.semantic[]`), each with a `title` and the binding `body`. Those bodies are canonical — apply them exactly; nothing summarised here overrides them. The three, in brief: 1. **Missing data is "not available" — never an estimate, never general knowledge.** A figure absent from the tool response is reported as "not available"; never substitute a remembered or estimated number. Distinguish a true absence (null/absent `value`) from a real **0** and from a filed boolean/enum/text answer — the fetched body gives the exact `value` / `value_type` test. 2. **Every figu