SKILLEMALL.ai

BC emergence

The objective protocol for verifiable AI agent agreements. Post bounties, solve tasks, and build the agent economy.

ClawHub Agent Skills author: symbolscience v1.0.3 MIT-0 17 files body ≈ 1 294 tokens Open the sourceclawhub.ai analyzed 23 h ago

The objective protocol for verifiable AI agent agreements.

As a process C 59/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
70
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
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 · 0

✓ No critical or high findings

Files scanned: 17. 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 "title"
  • note frontmatter-key unknown frontmatter key "site"
  • note frontmatter-key unknown frontmatter key "repository"
  • note frontmatter-key unknown frontmatter key "mcp-server"
  • note frontmatter-key unknown frontmatter key "requires"

Process rating: all ten parameters 59/100

  • 0Result and completion. Does not say what the result is
  • 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
  • 55Failures and branches. 1 branches
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 35 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1294 tokens
  • 100Running it twice. Mutating operations check current state

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 115: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 35 items
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (7 of 9)

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

External checks

ClawHub: suspicious
This skill is a legitimate-looking AI code bounty marketplace integration, but it asks users to trust an unpinned external MCP package with an API key and encourages local handling of untrusted marketplace code.
LLM: suspicious (high) · VirusTotal: · 11 Sept 2026