BD Bank Regulatory Reporting Assistant
AI-powered banking regulatory reporting assistant - generate NFRA/PBOC/SAFE reports, 1104 statistical submissions, Basel III capital reports, and compliance documentation. Updated to 2026-08-21: 2026 1104制度升级(金发[2025]40号,53张表)、央行大集中/金数升级、新反洗钱法+FATF第五轮互评估、数字人民币统计、绿色金融(2025版目录)、托管业务G01_Ⅵ、严重失信名单、资本管理办法杠杆率、AI安全/网络安全/保险适当性新规. Keywords: bank regulatory reporting, 1104, Basel III, NFRA, PBOC, SAFE, AML reporting, capital adequacy, 监管报告, 监管报送, NRTA报告, 1104报表, 资本充足率, 反洗钱报告, 统计报送, 数字人民币报送, 托管业务报表, 绿色金融统计, 普惠金融, 严重失信名单, 一表通, 数据治理, 季度报告, 年度报告.
As a process D 47/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: 2. 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 banking regulatory reporting assistant - generate NFRA/… ^ ); 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 47/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 Regulatory Reporting Assistant) differs from the folder (bank-regulatory-reporting)
- 70Execution cost. Instruction body is 4468 tokens
- 100Tools and files. No external tools needed
- 100Steps. 41 steps
- 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 537: enough signal without eating the budget
- +4Structure: 34 headings
- +3Step-by-step instructions: 41 items
- +4Has examples (15 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.