SKILLEMALL.ai
GitHub ↗ RU Sign in

AC subagent-driven-development

Execute plans via delegate_task subagents (2-stage review).

NousResearch/hermes-agent Hermes author: NousResearch MIT 3 files body ≈ 2 568 tokens Open the sourcegithub.com↗ analyzed 31 h ago

Execute plans via delegatetask subagents (2-stage review).

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerSoftware developmentSecurityPersonal productivitytype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
81
Run on models
none yet
Process rating
C
51/100
Has gaps
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

    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: 3. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 51/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. 7 mutating operations with no state check
    • 55Failures and branches. 1 branches
    • 60Consistency. The Hermes dialect needs category and tags
    • 85Steps. 55 steps, 1 vague phrases
    • 100Tools and files. No external tools needed
    • 100Execution cost. Instruction body is 2568 tokens
    • low 11 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 59: 120–800 characters recommended
    • +3Output format is not stated: the model decides each time
    • -5TODO / placeholder text left in the skill
    • +2Single-language instructions
    • +4Structure: 27 headings
    • +3Step-by-step instructions: 55 items
    • +4Has examples (9 code blocks)
    • +4Reference files are cited in the instructions (2 of 2)
    • +1License stated

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