AC clawlancer
Integrate OpenClaw with Clawlancer and automatically execute both sell-side listing creation and buy-side order creation through executable scripts. Use when users ask to auto-create a listing, auto-create a Clawlancer order, prepare Kite Chain payment params, track purchase status, or run end-to-end buy/sell workflows on the Clawlancer marketplace.
As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenscripts/create_listing.py:13High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)DEFAULT_SUPPLIER_WALLET = "0xDe…f21"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:20High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Settlement token: `USDT` (`0x0f…e63`)
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:21High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- PaymentRouter: `0x6D…24C`
quoted
Files scanned: 5. 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 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
- 30Running it twice. 15 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 30 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 872 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 351: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 30 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.