SKILLEMALL.ai

BC alkahest-user

Interact with Alkahest escrow contracts as a buyer, seller, or oracle using the CLI

ClawHub Agent Skills author: 疒奀 v1.0.0 MIT-0 5 files body ≈ 2 615 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 52/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
95
Quality 40%
76
Run on models
none yet
Process rating
C
52/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. 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-token references/contracts.md:15
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | Attestation (v2) | `Atte…on2` | `attestation: AttestationRequest`, `arbiter: address`, `demand: bytes` |
    table
  • low Secrets in code secret-high-entropy-token references/contracts.md:72
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | ERC2…ion | `0x1F…F43` |
    table
  • low Secrets in code secret-high-entropy-token references/contracts.md:73
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | ERC2…ion | `0x8d…3F6` |
    table
  • low Secrets in code secret-high-entropy-token references/contracts.md:74
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | ERC2…ils | `0x94…Dde` |
    table
  • low Secrets in code secret-high-entropy-token references/contracts.md:76
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | ERC7…ion | `0x76…07B` |
    table

Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 52/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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 9 mutating operations with no state check
  • 60Tools and files. Uses tools (node) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 8 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2615 tokens
  • low 14 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 83: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 26 headings
  • +3Step-by-step instructions: 8 items
  • +3Output format is stated explicitly
  • +4Has examples (18 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.

External checks

ClawHub: suspicious
This appears to be a legitimate blockchain escrow skill, but it gives agents patterns for wallet secrets and real fund-moving transactions without enough safety guardrails.
LLM: suspicious (high) · VirusTotal: · 29 May 2026