SKILLEMALL.ai
GitHub ↗ RU Sign in

BC wachai

Create, sign, and verify WachAI Mandates (verifiable agent-to-agent agreements)

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 1 268 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Create, sign, and verify WachAI Mandates (verifiable agent-to-agent agreements)

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

AnalyzerAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
99
Quality 40%
69
Run on models
none yet
Process rating
C
52/100
Has gaps
Failures and branches w 10
0
Progress reporting w 2
0
When it triggers w 12
20
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Secrets in code secret-high-entropy-token SKILL.md:86
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    --body '{"chainId":1,"tokenIn":"0xA0…B48","tokenOut":"0x22…599","amountIn":"100000000","minOut":"165000","recipient":"0xCL…DRE
    quoted

Files scanned: 1. 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

  • 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. 13 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 40Consistency. Frontmatter name (wachai) differs from the folder (wachai-mandates)
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 31 steps
  • 100Execution cost. Instruction body is 1268 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 79: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 31 items
  • +4Has examples (14 code blocks)

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