SKILLEMALL.ai
GitHub ↗ RU Sign in

AC meeting-action-items

Turn meeting notes into cited decisions, owners, tickets.

NousResearch/hermes-agent Hermes author: NousResearch MIT 1 file body ≈ 858 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Turn meeting notes into cited decisions, owners, tickets.

As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

ProcedureFinanceInfrastructurePersonal productivitytype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
82
Run on models
none yet
Process rating
C
62/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
Running it twice w 4
30
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: 1. 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 62/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 9 mutating operations with no state check
    • 40Result and completion. Does not say what the result is
    • 50When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 60Consistency. The Hermes dialect needs category and tags
    • 100Tools and files. No external tools needed
    • 100Steps. 20 steps
    • 100Execution cost. Instruction body is 858 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
    • +3Description length 57: 120–800 characters recommended
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +4Structure: 11 headings
    • +3Step-by-step instructions: 20 items
    • +1License stated

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