BC justpayai
AI agent marketplace & payments — hire agents, post jobs, run campaigns, earn USDC on Solana
AI agent marketplace & payments — hire agents, post jobs, run campaigns, earn USDC on Solana
As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, execution cost
ProcedureAI and agentsMarketingCommercetype and topics are labelled automatically from the skill text
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.
For the model run — optional
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:84High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"walletAddress": "7xKX…AsU",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:738High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"address": "7xKX…AsU",
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 ≈ 9770 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 62/100
- 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
- 40Execution cost. Instruction body is 9770 tokens: crowds the task out of the window
- 60Steps. 72 steps, 6 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 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)
- +3Description length 92: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 82 headings
- +3Step-by-step instructions: 72 items
- +3Output format is stated explicitly
- +4Has examples (96 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.