SKILLEMALL.ai

BD supply-chain-advisory

Audits dependency supply chains for bad versions, lockfile drift, and artifact integrity. Use when adding deps, handling incidents, or releasing a plugin.

athola/claude-night-market Hermes author: athola 4 files body ≈ 921 tokens Open the sourcegithub.com analyzed 3 h ago

Audits dependency supply chains for bad versions, lockfile drift, and artifact integrity.

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

AnalyzerInfrastructureSecurityAI and agentstype 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
43/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. 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 Risky intent intent-offensive-security modules/incident-response.md:35
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    3. **SSH keys**: lateral movement risk

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

Against the Agent Skills spec

  • warning description-long-hermes description is 154 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 "provides"
  • note frontmatter-key unknown frontmatter key "usage_patterns"
  • note frontmatter-key unknown frontmatter key "complexity"
  • note frontmatter-key unknown frontmatter key "model_hint"
  • note frontmatter-key unknown frontmatter key "estimated_tokens"
  • note frontmatter-key unknown frontmatter key "progressive_loading"
  • note frontmatter-key unknown frontmatter key "modules"
  • note frontmatter-key unknown frontmatter key "role"

Process rating: all ten parameters 43/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. 3 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 100Steps. 21 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 921 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
  • +1No license
  • +2Single-language instructions
  • +3Description length 154: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 21 items
  • +4Has examples (2 code blocks)

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