BD Bank Financial Report Analyst
AI-powered financial statement analysis assistant for banks - analyze corporate balance sheets, income statements, cash flows, peer comparison, and investment thesis. Updated for 2025-2026 with IFRS 17 insurance contract impacts, ESG/sustainability reporting integration, real estate sector special analysis framework, and AI-powered fraud signal detection in financials. Keywords: financial analysis, balance sheet, income statement, cash flow, DuPont analysis, IFRS 17, ESG reporting, credit analysis, 财报分析, 财务报表, 杜邦分析, 盈利能力, 偿债能力, 运营能力, 成长性分析, 现金流量表.
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 3, column 14: description: AI-powered financial statement analysis assistant for banks - anal… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (Bank Financial Report Analyst) differs from the folder (bank-financial-analysis)
- 100Tools and files. No external tools needed
- 100Steps. 48 steps
- 100Execution cost. Instruction body is 1714 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 553: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 48 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.