BB KYC & Identity
Know-Your-Customer verification via MasterPay Global. Submit personal data, upload identity documents, and track approval status.
As a process B 72/100 · Nearly there — weak spots: result and completion, consistency, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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
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")
Process rating: all ten parameters 72/100
- 0Result and completion. Does not say what the result is
- 30Running it twice. 8 mutating operations with no state check
- 40Consistency. Frontmatter name (KYC & Identity) differs from the folder (aiotnetwork-kyc-identity)
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 39 steps
- 100Failures and branches. 5 branches, has a failure section
- 100Execution cost. Instruction body is 1785 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 129: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 39 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.
External checks
ClawHub: suspicious
This KYC skill is purpose-aligned but should be reviewed carefully because it handles identity documents and personal data while leaving authentication, endpoint choice, and privacy handling under-specified.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026