BB slopwork
Solana-powered task marketplace with multisig escrow payments - post tasks, bid on work, escrow funds, and release payments via 2/3 multisig
Solana-powered task marketplace with multisig escrow payments - post tasks, bid on work, escrow funds, and release payments via 2/3 multisig
As a process B 66/100 · Nearly there — weak spots: when it triggers, consistency, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Exfiltration
read-dotenvREADME.md:21Reads a .env filecp .env.example .env # configure DATABASE_URL, SOLANA_RPC_URL, etc.
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:148High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"systemWalletAddress": "3ARu…Ptc",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:149High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"arbiterWalletAddress": "3ARu…Ptc",
quoted
Files scanned: 2. 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") - warning
body-longSKILL.md body ≈ 7519 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 66/100
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 42 mutating operations with no state check
- 40Consistency. Frontmatter name (slopwork) differs from the folder (slopwork-marketplace)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 7519 tokens
- 100Steps. 61 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Progress reporting. Reports progress
- low 22 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)
- +2Single-language instructions
- +3Description length 140: enough signal without eating the budget
- +4Structure: 50 headings
- +3Step-by-step instructions: 61 items
- +3Output format is stated explicitly
- +4Has examples (20 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.