BC check-ao-transaction
Check transaction status on AO bridge
As a process C 64/100 · Has gaps — weak spots: when it triggers, failures and branches, 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.
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:28High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"txId": "hcdE…-mU",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:29High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"sender": "y3-J…4AI",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:30High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"recipient": "y3-J…4AI",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:35High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"fromTokenId": "xU9z…h10",
detector -
low Secrets in code
secret-high-entropy-tokenSKILL.md:38High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"feeRecipient": "4S58…3ZI",
quoted
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-shortdescription under 40 chars: too little signal for triggering - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "command"
Process rating: all ten parameters 64/100
- 0When it triggers. No condition that starts the skill
- 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
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 30 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 707 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 37: 120–800 characters recommended
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 7 headings
- +3Step-by-step instructions: 30 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.
External checks
ClawHub: clean
This skill is a straightforward AO bridge transaction-status checker that sends the provided transaction hash to a fixed AOX API and does not modify files or accounts.
LLM: benign (high) · VirusTotal: · 29 May 2026