SKILLEMALL.ai
GitHub ↗ RU Sign in

DF github-code-review

Comprehensive GitHub code review with AI-powered swarm coordination

ruvnet/wifi-densepose Hermes author: ruvnet MIT 1 file body ≈ 6 366 tokens Open the sourcegithub.com↗ analyzed 7 h ago

Comprehensive GitHub code review with AI-powered swarm coordination

As a process F 33/100 · No process to follow — References files that are not bundled: link

AnalyzerGitHubAI and agentsData and analyticstype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
D
77/100
safety, quality, tests
Safety 60%
100
Quality 40%
43
Run on models
none yet
Process rating
F
33/100
No process to follow
References files that are not bundled: link
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
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.
  2. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
  3. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  4. The text references files that are not there: add them or drop the references.
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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning description-long-hermes description is 67 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
  • warning body-long SKILL.md body ≈ 6366 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: link
  • note frontmatter-key unknown frontmatter key "requires"
  • note frontmatter-key unknown frontmatter key "capabilities"

Process rating: all ten parameters 33/100

Will not run. References files that are not bundled: link
  • 0Tools and files. 1 referenced file(s) missing: link
  • 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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 70Execution cost. Instruction body is 6366 tokens
  • 100Steps. 60 steps
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 21 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 67: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -237 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +4Structure: 71 headings
  • +3Step-by-step instructions: 60 items
  • +4Has examples (50 code blocks)

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