SKILLEMALL.ai

BC agent-guardrails

Stop AI agents from secretly bypassing your rules. Mechanical enforcement with git hooks, secret detection, deployment verification, and import registries. Born from real production incidents: server crashes, token leaks, code rewrites. Works with Claude Code, Clawdbot, Cursor. Install once, enforce forever.

ClawHub Hermes author: olmmlo-cmd v1.0.0 24 files · 7 scripts body ≈ 1 290 tokens Open the sourceclawhub.ai analyzed 2 d ago

Stop AI agents from secretly bypassing your rules.

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

ProcedureSoftware developmentAI and agentsQuality controltype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
99
Quality 40%
71
Run on models
none yet
Process rating
C
51/100
Has gaps
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

The same skill appears in 1 more place: ClawHub

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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 Dangerous commands cmd-cron-mention references/deployment-verification-guide.md:221
    Mentions editing / listing crontab (documentation of a security skill)
    crontab -l | grep notify
    security skill

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

Against the Agent Skills spec

  • warning description-long-hermes description is 309 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • note frontmatter-key unknown frontmatter key "keywords"
  • note frontmatter-key unknown frontmatter key "repository"
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "bugs"
  • note frontmatter-key unknown frontmatter key "requirements"
  • note frontmatter-key unknown frontmatter key "pricing"

Process rating: all ten parameters 51/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. 36 mutating operations with no state check
  • 100Tools and files. No external tools needed
  • 100Steps. 17 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1290 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)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 309: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 17 items
  • +4Has examples (5 code blocks)
  • +4Reference files are cited in the instructions (5 of 5)
  • +3All 6 scripts are documented
  • +1License stated

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

External checks

ClawHub: suspicious
This guardrails skill is mostly purpose-aligned, but it installs persistent Git hooks and can expose secret values in logs, so it should be reviewed before use.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026