CC gstable-ai-payment
GStable AI Payment Protocol - enables AI Agents to discover, negotiate, and execute cryptocurrency payments on behalf of users
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The purpose itself is risky: wallets, browser password stores, offensive security. Even an honest implementation gives the agent access to things that cost money.
Explain in the description why the access is needed and how it is limited; add tests that show refusals on dangerous requests.
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 · 9
✓ No critical or high findings
Medium and low: 9
-
medium Risky intent
intent-wallet-secretsskill-card.md:24Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer targetRisk: A primary wallet private key would expose high-value funds to agent-driven signing and transaction execution. <br>
-
medium Risky intent
intent-wallet-secretsSKILL.md:37Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target# Required: wallet private key used to sign EIP-712 messages and send transactions
-
medium Risky intent
intent-wallet-secretsSKILL.md:233Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target| `WALLET_PRIVATE_KEY` | ✅ | Wallet private key used to sign EIP-712 messages and execute transactions (`0x` prefix) |
-
low Risky intent
intent-wallet-secretsscripts/config.py:53Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (quoted — discussed, not commanded)"Please set it to your wallet private key (0x... format)."
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:59High-entropy token-like string (may be an id, hash or a credential)uv run scripts/gstable-ai-payment.py get_link lnk_…tua
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:62High-entropy token-like string (may be an id, hash or a credential)uv run scripts/gstable-ai-payment.py get_link lnk_…pGh
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:68High-entropy token-like string (may be an id, hash or a credential)uv run scripts/gstable-ai-payment.py create_session lnk_…tua 137 USDC
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:74High-entropy token-like string (may be an id, hash or a credential) (placeholder value)uv run scripts/gstable-ai-payment.py pay lnk_…tua 137 USDC us…@….com
placeholder -
low Secrets in code
secret-high-entropy-tokenSKILL.md:132High-entropy token-like string (may be an id, hash or a credential) (placeholder value)uv run scripts/gstable-ai-payment.py pay lnk_…tua 137 USDC us…@….com
placeholder
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 58/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
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2124 tokens
- 100Running it twice. Mutating operations check current state
- low 12 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
- -218 emoji in the instructions: noise for the model
- -34 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 126: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.