BC ainumbers
Deterministic regulatory-computation estate: 640+ compliance tools, chains, a verify ledger, and a timestamping anchor, callable over MCP with zero-egress in-page twins. Rules: synthetic data only; verify with verify_execution_hash before trusting; return a ledger link; never paste PII. MCP: https://mcp.ainumbers.co/mcp
Deterministic regulatory-computation estate: 640+ compliance tools, chains, a verify ledger, and a timestamping anchor, callable over MCP with zero-egress…
As a process C 53/100 · Has gaps — 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 2, column 14: description: Deterministic regulatory-computation estate: 640+ compliance tools… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 320 tokens
- 100Running it twice. No mutating operations
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)
- +4Structure: 1 headings, hard to scan
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +3Description length 321: enough signal without eating the budget
- +3Step-by-step instructions: 4 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.