SKILLEMALL.ai

CB qmd

Hybrid local search over notes, docs, and transcripts.

Not recommendedcritical or high security findings
NousResearch/hermes-agent Hermes author: NousResearch MIT 1 file body ≈ 3 143 tokens Open the sourcegithub.com analyzed 2 d ago

Hybrid local search over notes, docs, and transcripts.

As a process B 66/100 · Nearly there — weak spots: when it triggers, running it twice, progress reporting

ProcedureGitHubAI and agentstype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
C
72/100
safety, quality, tests
Safety 60%
64
Quality 40%
83
Run on models
none yet
Process rating
B
66/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
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

  • high Dangerous commands cmd-persistence SKILL.md:274
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    cat > ~/Library/LaunchAgents/com.qmd.daemon.plist << 'EOF'
  • high Dangerous commands cmd-persistence SKILL.md:301
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load ~/Library/LaunchAgents/com.qmd.daemon.plist

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

Against the Agent Skills spec

  • note edit-residue the text marks something as outdated (lines 187): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 66/100

  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 60Consistency. The Hermes dialect needs category and tags
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 26 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Execution cost. Instruction body is 3143 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)
  • +3Description length 54: 120–800 characters recommended
  • -2localhost URLs: will not work for another user
  • +2Single-language instructions
  • +4Structure: 40 headings
  • +3Step-by-step instructions: 26 items
  • +3Output format is stated explicitly
  • +4Has examples (24 code blocks)
  • +1License stated

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