BC check-transaction
Check transaction status on Hymatrix bridge
As a process C 62/100 · Has gaps — weak spots: when it triggers, failures and branches, consistency
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)"TokenId": "0syT…rsc",
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)"WrappedTokenId": "SX8L…WCo",
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)"txId": "gXZ8…z_w",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:31High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"sender": "0x57…DEA",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:32High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"recipient": "XWDO…Z9k",
quoted
Files scanned: 3. 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 "command"
Process rating: all ten parameters 62/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (check-transaction) differs from the folder (check-hymx-transaction)
- 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. 19 steps
- 100Execution cost. Instruction body is 592 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 43: 120–800 characters recommended
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 5 headings
- +3Step-by-step instructions: 19 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.
External checks
ClawHub: clean
This skill appears to do the advertised job: it sends a user-provided transaction hash to a Hymatrix bridge status API and returns the result.
LLM: benign (high) · VirusTotal: · 29 May 2026