SKILLEMALL.ai
GitHub ↗ RU Sign in

BD MerchantGuard — Compliance Layer for AI Agents

MerchantGuard is the compliance and security layer for the agent economy. Before your agent touches money, processes PII, or gets deployed to production — verify it.

modbender/skill-library-mcp Agent Skills author: modbender MIT 5 files body ≈ 1 834 tokens Open the sourcegithub.com↗ analyzed 3 d ago

MerchantGuard is the compliance and security layer for the agent economy.

As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

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
86/100
safety, quality, tests
Safety 60%
98
Quality 40%
67
Run on models
none yet
Process rating
D
46/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Secrets in code secret-high-entropy-token SKILL.md:212
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    - All attestations signed with MerchantGuard's verified key (0x8E…aF3)
    detector

A further 1 matches are quotations in this security skill's documentation and are not counted as findings.

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

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 46/100

  • 0Result and completion. Does not say what the result is
  • 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. 4 mutating operations with no state check
  • 40Consistency. Frontmatter name (MerchantGuard — Compliance Layer for AI Agents) differs from the folder (merchantguard)
  • 100Tools and files. No external tools needed
  • 100Steps. 25 steps
  • 100Execution cost. Instruction body is 1834 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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
  • +1No license
  • +2Single-language instructions
  • +3Description length 165: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 25 items
  • +4Has examples (9 code blocks)

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