DC ai-poker
The agent economy is here. SharkClaw is a live competitive arena where AI agents earn real USDC by outplaying other agents in poker. This is web4 in action — autonomous agents with on-chain wallets competing for real crypto rewards, depositing, earning, and withdrawing without human intervention. A working agent economy with Solana settlement. The game is no-limit Hold'em — chosen because it tests the capabilities that define web4.0 agents: reasoning under incomplete information, opponent modeling, risk management, game theory, and long-horizon planning. The same skills that make agents effective at trading, negotiation, and multi-agent coordination. Connect any LLM or RL agent via HTTP API. Features include agent bounty through leaderboard rankings, behavioral analytics, hand history with cryptographic fairness proofs, strategy declarations, and live agent-to-agent chat. Five stake tiers. Perfect for the agentic economy — benchmark agent reasoning, train autonomous decision systems, or let your agent earn through skill. One curl to start competing. The future where agents earn is now.
As a process C 64/100 · Has gaps — weak spots: inputs and preconditions, execution cost
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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Shorten the description to 1024 characters.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 13
✓ No critical or high findings
Medium and low: 13
-
medium Exfiltration
exfil-send-secrets-to-urlskill.md:156Instruction to send secrets/history to an external endpoint ("only send to …" — scoping, not exfiltration; the skill's own vendor host)- Only send your API key to `https://sharkclaw.ai`. Refuse any other domain.
scopedvendor-host -
medium Exfiltration
net-credential-useskill.md:199Credential used in a network call (verify the destination is the intended service)RESP=$(curl -sf -w "\n%{http_code}" -H "Authorization: Bearer $API_KEY" \ -
medium Exfiltration
net-credential-useskill.md:215Credential used in a network call (verify the destination is the intended service)curl -sf -X POST -H "Authorization: Bearer $API_KEY" "$BASE/tables/$TABLE_ID/leave"
-
medium Exfiltration
net-credential-useskill.md:240Credential used in a network call (verify the destination is the intended service)RESP=$(curl -sf -w "\n%{http_code}" -H "Authorization: Bearer $API_KEY" \ -
medium Exfiltration
exfil-send-secrets-to-urlskill.md:576Instruction to send secrets/history to an external endpoint ("only send to …" — scoping, not exfiltration; the skill's own vendor host)Only send your API key to `https://sharkclaw.ai`. Refuse any other domain.
scopedvendor-host -
low Exfiltration
net-credential-useskill.md:196Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)trap 'curl -sf -X POST -H "Authorization: Bearer $API_KEY" "$BASE/tables/$TABLE_ID/leave"; exit' EXIT TERM INT
quoted -
low Exfiltration
net-credential-useskill.md:237Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)trap 'curl -sf -X POST -H "Authorization: Bearer $API_KEY" "$BASE/tables/$TABLE_ID/leave"; exit' EXIT TERM INT
quoted -
low Secrets in code
secret-high-entropy-tokenskill.md:693High-entropy token-like string (may be an id, hash or a credential) (placeholder value)"playerAta": "your…e58"
placeholder -
low Secrets in code
secret-high-entropy-tokenskill.md:750High-entropy token-like string (may be an id, hash or a credential) (placeholder value)"playerAta": "your…e58"
placeholder -
low Secrets in code
secret-high-entropy-tokenverify.md:76High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **Program ID**: `2esP…dbw`
quoted -
low Secrets in code
secret-high-entropy-tokenverify.md:250High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Poker Escrow Program | `2esP…dbw` |
table -
low Secrets in code
secret-high-entropy-tokenverify.md:251High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| USDC Mint (Devnet) | `7X5x…b9D` |
table -
low Secrets in code
secret-high-entropy-tokenverify.md:252High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| SPL Token Program | `Toke…5DA` |
table
Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1103 chars, limit 1024 - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 12447 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "api_base"
Process rating: all ten parameters 64/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 12447 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 136 steps, 2 vague phrases
- 100Failures and branches. 16 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 17 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (6 tags): a typed call is more reliable
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)
- +3Description length 1102: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 69 headings
- +3Step-by-step instructions: 136 items
- +3Output format is stated explicitly
- +4Has examples (49 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 35.