BF regulated-agent-human-gate
Build, review, or test KYA (Know Your Agent) human-gate controls for AI agents that prepare or execute regulated financial actions. Use for payments, withdrawals, stablecoin off-ramps, lending, onboarding, identity or account-control changes, MCP execution chains, action-bound approvals, delegation receipts, audit evidence, and adversarial evaluations.
Build, review, or test KYA (Know Your Agent) human-gate controls for AI agents that prepare or execute regulated financial actions.
As a process F 37/100 · Will not run — References files that are not bundled: templates/action-intent-schema.json, templates/gate-decision-schema.json, templates/audit-log-schema.json
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: templates/action-intent-schema.json - warning
missing-refreference to a missing file: templates/gate-decision-schema.json - warning
missing-refreference to a missing file: templates/audit-log-schema.json - warning
missing-refreference to a missing file: templates/mcp-tool-contract-example.json - warning
missing-refreference to a missing file: templates/policy-template.yaml
Process rating: all ten parameters 37/100
- 0Tools and files. 5 referenced file(s) missing: templates/action-intent-schema.json, templates/gate-decision-schema.json, templates/audit-log-schema.json
- 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
- 20When it triggers. No condition that starts the skill
- 100Steps. 45 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1504 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
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
- -31 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 354: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.