BD greenhelix-agent-payment-rails-playbook
The Agent Payment Rails Playbook. Ship multi-protocol agentic payments (x402, ACP, AP2, UCP, MPP) with spending controls, KYA compliance, and escrow protection from first transaction to production.
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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
body-longSKILL.md body ≈ 21113 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "type" - note
frontmatter-keyunknown frontmatter key "price_usd" - note
frontmatter-keyunknown frontmatter key "content_type" - note
frontmatter-keyunknown frontmatter key "executable" - note
frontmatter-keyunknown frontmatter key "install" - note
frontmatter-keyunknown frontmatter key "credentials"
Process rating: all ten parameters 48/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 10Execution cost. Instruction body is 21113 tokens: crowds the task out of the window
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 55 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 100Steps. 78 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 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
- +2Single-language instructions
- +3Description length 197: enough signal without eating the budget
- +4Structure: 55 headings
- +3Step-by-step instructions: 78 items
- +4Has examples (19 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
External checks
ClawHub: suspicious
This is a non-executable payment guide, but it needs review because its examples can affect real payments while the sandbox and live-production language is inconsistent.
LLM: suspicious (high) · VirusTotal: · 29 May 2026