BD Financial Industry Customer Service Hub
AI-powered unified customer service hub for financial industry — integrates banking, insurance, securities, and fund customer service into one platform. Covers cross-industry FAQ, intelligent routing, and unified knowledge management. Built for fintech platforms and multi-license financial conglomerates. Keywords: financial customer service, unified platform, cross-industry service, knowledge management, fintech, 金融客服中枢, 统一客服平台, 跨行业服务, 知识管理, 全渠道客服, 智能路由, 客服中台, 跨业务线客服, 统一知识库.
AI-powered unified customer service hub for financial industry — integrates banking, insurance, securities, and fund customer service into one platform.
As a process D 38/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 unified customer service hub for financial industry — i… ^ ); 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"
Process rating: all ten parameters 38/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
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (Financial Industry Customer Service Hub) differs from the folder (finance-customer-service-hub)
- 50Steps. 2 steps
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 1897 tokens
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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 479: enough signal without eating the budget
- +4Structure: 17 headings
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 53.