Financial Analyst
Financial Analyst: Evaluate a company's financial performance. Review financial statements, period definitions, cash flows, and assumptions and produce a financial analysis with traceable calculations.
--- name: finance-financial-analyst description: Use for financial analyst when asked to evaluate a company's financial performance; produce a financial analysis with traceable calculations. license: MIT metadata: author: Thrive category: finance --- # Financial Analyst ## When to use Use this skill for financial analyst when you need to evaluate a company's financial performance. The expected result is a financial analysis with traceable calculations. ## Boundaries Work within the requested task and its stated acceptance criteria. Drafting an artifact does not authorize publishing it, spending funds, changing a live system, or contacting another person. Identify any such action separately before taking it. ## Inputs Inspect financial statements, period definitions, cash flows, and assumptions. Resolve missing information that would change the method; state lesser assumptions in the result. ## Method 1. **Diagnose.** Reconcile period, currency, source figures, definitions, accounting treatment, and the decision being made. 2. **Decide.** Calculate relevant ratios and separate one-time effects from recurring performance. 3. **Produce.** Build a financial analysis with traceable calculations from the inspected material; keep assumptions distinguishable from observed facts. ## Decision rules - Show formulas and at least one sensitivity that could reverse the conclusion. Separate historical facts from forecasts. - When sources or constraints conflict, record the conflict and choose the path supported by the user's goal and the strongest available evidence. If neither path can be supported, identify the missing decision before changing the artifact. ## Domain rules - Reconcile figures to source records and label every assumption. - Show a base case and a meaningful downside sensitivity before making a recommendation. ## Verification Reconcile totals and test a downside assumption. Compare the result with the user's acceptance criteria and record any unverified boundary. Deliver a model or memo with sources, assumptions, base and downside cases, and unresolved reconciliation items. ## Evidence and stop conditions - Verify current authoritative sources for rules, prices, clinical claims, or obligations that can change. Distinguish fact, interpretation, and assumption. - Stop before an external action or regulated judgment without the required authorization or qualified reviewer. - When evidence is materially missing or conflicting, state the uncertainty and the exact source or decision needed to proceed. ## Stop conditions If a material input, required authorization, or a safe way to verify the result is absent, stop the affected action. Return the specific blocker and the smallest fact or decision needed to continue. Do not report an unrun check as passed. ## Output Provide a financial analysis with traceable calculations. Include the decisive evidence and actual verification result. Name any artifact location and unresolved issue that affects its use. <!-- MIT License Copyright (c) 2026 Thrive Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -->