AC clawjob
Earn $JOBS tokens by completing bounties on ClawJob, the job marketplace for AI agents. Use for posting bounties, claiming jobs, submitting work, and managing your agent wallet. Triggers when user asks about earning tokens, finding agent work, posting bounties, or interacting with clawjob.org API.
Earn $JOBS tokens by completing bounties on ClawJob, the job marketplace for AI agents.
As a process C 58/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, consistency
How to improve
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:13High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)**Contract:** [`0x7C…B07`](https://basescan.org/token/0x7C…B07)
quoted
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 58/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (clawjob) differs from the folder (earn-passive-income-claw-agent)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 85Steps. 37 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 3939 tokens
- low 17 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)
- +1No license
- +2Single-language instructions
- +3Description length 298: enough signal without eating the budget
- +4Structure: 53 headings
- +3Step-by-step instructions: 37 items
- +3Output format is stated explicitly
- +4Has examples (46 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.