SKILLEMALL.ai
RU Sign in

BD oss-forensics

GitHub supply-chain forensics: recovery, IOCs, reporting.

NousResearch/hermes-agent Hermes author: NousResearch MIT 8 files body ≈ 4 778 tokens Open the sourcegithub.com↗ analyzed 20 h ago

GitHub supply-chain forensics: recovery, IOCs, reporting.

As a process D 49/100 · Unfinished process — weak spots: result and completion, failures and branches, running it twice

IntegrationGitHubGoogle CloudSecuritytype 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
49/100
Unfinished process
Result and completion w 14
0
Failures and branches w 10
0
Running it twice w 4
30
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Risky intent intent-offensive-security references/evidence-types.md:31
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    | `IP_ADDRESS` | A C2 server or attacker IP | `192.0.2.1` |

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

Against the Agent Skills spec

  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "toolsets"
  • note edit-residue the text marks something as outdated (lines 219, 234): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 49/100

  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 30Running it twice. 40 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
  • 60Consistency. The Hermes dialect needs category and tags
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 4778 tokens
  • 85Steps. 110 steps, 2 vague phrases
  • 100Progress reporting. Reports progress
  • low 13 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 57: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 110 items
  • +4Has examples (7 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)
  • +3All 1 scripts are documented
  • +1License stated

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