SKILLEMALL.ai

BD writing-rules

Creates behavioral rules in markdown to block dangerous commands or restrict AI behavior. Use when adding safety guardrails or preventing specific commands.

athola/claude-night-market Hermes author: athola 1 file body ≈ 1 243 tokens Open the sourcegithub.com analyzed 3 h ago

Creates behavioral rules in markdown to block dangerous commands or restrict AI behavior.

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

GeneratorSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
99
Quality 40%
75
Run on models
none yet
Process rating
D
48/100
Unfinished process
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. 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-privilege SKILL.md:141
    Privilege escalation / world-writable permissions (documentation of a security skill)
    chmod\s+777       → chmod 777
    security skill

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

Against the Agent Skills spec

  • warning description-long-hermes description is 156 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "alwaysApply"
  • note frontmatter-key unknown frontmatter key "dependencies"
  • note frontmatter-key unknown frontmatter key "estimated_tokens"
  • note frontmatter-key unknown frontmatter key "complexity"
  • note frontmatter-key unknown frontmatter key "model_hint"
  • note frontmatter-key unknown frontmatter key "provides"
  • note frontmatter-key unknown frontmatter key "usage_patterns"

Process rating: all ten parameters 48/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
  • 30Running it twice. 2 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 100Steps. 35 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1243 tokens
  • low 12 top-level sections: this looks like several domains in one skill

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 156: enough signal without eating the budget
  • +4Structure: 26 headings
  • +3Step-by-step instructions: 35 items
  • +4Has examples (10 code blocks)

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