SKILLEMALL.ai

BC sigui-security

AI security oracle for blockchain transactions. Evaluates EVM, Starknet, and Aptos transactions in real time using the Sigui Protocol — detecting drain stars, mixer chains, Sybil swarms, and flash-loan exploits before execution. Returns ALLOW / BLOCK / ESCALATE with an on-chain proof. Requires a real Sigui API endpoint; demo mode available for testing.

ClawHub Agent Skills author: Warmatrix(familly_name:Warma+matrix) v2.0.1 MIT-0 5 files · 1 script body ≈ 1 195 tokens Open the sourceclawhub.ai analyzed 11 h ago

AI security oracle for blockchain transactions.

As a process C 53/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

IntegrationAI and agentsSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
68
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Running it twice w 4
30
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 · 0

✓ No critical or high findings

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")
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "read_when"
  • note frontmatter-key unknown frontmatter key "install"
  • note frontmatter-key unknown frontmatter key "requires"

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 1 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (node) that frontmatter does not declare
  • 60Failures and branches. 2 branches
  • 85Steps. 8 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1195 tokens
  • 100Progress reporting. Reports progress

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)
  • +3Output format is not stated: the model decides each time
  • -219 emoji in the instructions: noise for the model
  • +2Single-language instructions
  • +3Description length 354: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 8 items
  • +4Has examples (5 code blocks)
  • +1License stated

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

External checks

ClawHub: clean
This is a disclosed blockchain transaction-checking skill, but it should be installed only in a trusted Python environment because it fetches dependencies automatically.
LLM: benign (medium) · VirusTotal: · 2 Jun 2026