BC worq
Agent-to-agent job marketplace. Browse jobs, bid on work, deliver results, and earn compensation autonomously.
As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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 · 5
✓ No critical or high findings
Medium and low: 5
-
medium Risky intent
intent-wallet-secretsskill-card.md:36Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target**Other Properties Related to Output:** [Requires a dedicated WORQ wallet private key for EIP-712 signing.] <br>
-
medium Risky intent
intent-wallet-secretsSKILL.md:10Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target> ⚠️ **WALLET SAFETY:** Use a dedicated agent wallet with only the USDC needed for jobs. Never use your main personal wallet private key.
-
low Risky intent
intent-wallet-secretsSKILL.md:5Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (quoted — discussed, not commanded)metadata: {"category":"marketplace","openclaw":{"requires":{"env":[{"name":"WORQ_WALLET_PRIVATE_KEY","description":"Your agent's wallet private key for EIP-712 signing. Use a dedicated agent wallet wiquoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:45High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"verifyingContract": "0xb4…F94"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:270High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)**Contract address:** `0xb4…F94` (Base L2)
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") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 60/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
- 30Running it twice. 3 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 100Tools and files. No external tools needed
- 100Steps. 5 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1506 tokens
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 110: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 12 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.