本文へ移動
cccskills
無料GitHub で公開

codexkit-financial-statement-analyzer

Read and interpret financial statements — Income Statement, Balance Sheet, and Cash Flow Statement. Calculate key ratios, identify trends, and produce an analysis narrative. Use when reviewing company performance, preparing for investor meetings, or conducting due diligence. Do not use for preparing or auditing financial statements — this is an analysis tool only.

インストール方法を見る

含まれるファイル(5)

  • SKILL.md4.1 KB
  • agents/openai.yaml179 B
  • examples/common-mistakes.md790 B
  • examples/good-output.md895 B
  • verification/checklist.md1.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Financial Statement Analyzer

Purpose

Turn raw financial statements into a structured analysis with key ratios, trend identification, and an executive-ready narrative.

When to use

  • reviewing quarterly or annual financial results
  • preparing for board meetings or investor presentations
  • conducting financial due diligence on a target company
  • comparing financial performance across business units or competitors

When not to use

  • preparing financial statements (use management-accounts-writer)
  • statutory audit or compliance reporting
  • tax preparation

Inputs

  • Income Statement (P&L) for 2+ periods
  • Balance Sheet for 2+ periods
  • Cash Flow Statement for 2+ periods
  • industry context or peer companies for comparison (optional)
  • specific questions to answer (optional)

Procedure

  1. Analyze Income Statement:
    • Revenue trend: growth rate YoY
    • Gross margin and trend
    • Operating expenses as % of revenue
    • EBITDA and net profit margins
    • Unusual or one-off items
  2. Analyze Balance Sheet:
    • Liquidity: Current Ratio (CA/CL), Quick Ratio
    • Leverage: Debt-to-Equity, Interest Coverage
    • Working capital: DSO, DPO, DIO, Cash Conversion Cycle
    • Asset utilization: Total Asset Turnover, ROA
  3. Analyze Cash Flow Statement:
    • Operating CF quality: is it positive and growing?
    • Free Cash Flow = Operating CF − Capex
    • Cash conversion: Net Income → Operating CF (quality of earnings)
    • Investing and financing activities — are they sustainable?
  4. Calculate DuPont decomposition (ROE = Net Margin × Asset Turnover × Equity Multiplier)
  5. Identify red flags: declining margins, rising debt, negative operating CF, DSO spike
  6. Write analysis narrative: structured as Situation → Key Findings → Concerns → Recommendations

Output

  • ratio analysis table organized by category (profitability, liquidity, leverage, efficiency)
  • trend analysis (current vs prior period with directional arrows)
  • DuPont decomposition of ROE
  • red flags and areas of concern
  • executive narrative (1-page analysis summary)

Definition of done

  • minimum 12 financial ratios calculated across 4 categories
  • at least 2 periods compared with trend direction noted
  • red flags are explicitly called out
  • narrative is in plain business language, not accounting jargon

Examples

  • "Analyze our Q3 financials vs Q2 — what's improving and what's not?"
  • "Review this company's annual report and tell me if it's a good acquisition target."
  • "Why is our ROE declining despite growing revenue? Run a DuPont analysis."

Quality Criteria

  • All claims reference specific frameworks, standards, or quantifiable data
  • Content matches the stated audience's expertise level
  • Recommendations are actionable — each includes a concrete next step
  • No unsupported assertions or generic filler language

Verification (4C)

CheckQuestion
CorrectnessDo referenced frameworks and standards match their official definitions?
CompletenessAre all key concepts covered without significant gaps for the stated audience?
Context-fitWould this be useful for someone new to this domain, or is it too advanced/too basic?
ConsequenceIf a stakeholder acted on this immediately, what could they misinterpret?

Edge Cases

  • Conflicting frameworks — State which framework takes precedence and why. Document the trade-off explicitly.
  • Rapidly changing domain — Note information currency date. Flag sections likely to need updates.
  • Audience has mixed expertise levels — Provide a glossary and mark advanced sections as optional.

Changelog

  • v1.0.0 — Initial release

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月8日 更新

Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月8日 更新

Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月8日 更新

Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when preparing for first-time compliance.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月8日 更新

Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月8日 更新

Refine Product Backlog Items to meet INVEST criteria. Write User Stories with Acceptance Criteria in Given/When/Then format, estimate with Story Points, and flag dependencies. Use before sprint planning when backlog items need grooming. Do not use to prioritize the backlog — that is the Product Owner's decision.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月8日 更新

hoavdc のスキルをすべて見る

このスキルの問題を報告する