SKILLEMALL.ai

AB nika

Runs repeatable AI work as checked, budgeted workflow files.

sickn33/agentic-awesome-skills Hermes author: sickn33 MIT 1 file body ≈ 2 505 tokens Open the sourcegithub.com analyzed 2 d ago

Runs repeatable AI work as checked, budgeted workflow files.

As a process B 68/100 · Nearly there — weak spots: result and completion, when it triggers

ProcedureAI and agentsSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
79
Run on models
none yet
Process rating
B
68/100
Nearly there
When it triggers w 12
20
Result and completion w 14
40
Tools and files w 18
60
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: nika (sickn33/agentic-awesome-skills)

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

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "date_added"
    • note frontmatter-key unknown frontmatter key "source_repo"
    • note frontmatter-key unknown frontmatter key "source_type"
    • note frontmatter-key unknown frontmatter key "license_source"
    • note frontmatter-key unknown frontmatter key "prerequisites"

    Process rating: all ten parameters 68/100

    • 20When it triggers. No condition that starts the skill
    • 40Result and completion. Does not say what the result is
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 60Consistency. The Hermes dialect needs category and tags
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 38 steps
    • 100Failures and branches. 1 branches, has a failure section
    • 100Execution cost. Instruction body is 2505 tokens
    • 100Running it twice. No mutating operations
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low The response is described with custom markup (13 tags): a typed call is more reliable

    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 60: 120–800 characters recommended
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +4Structure: 16 headings
    • +3Step-by-step instructions: 38 items
    • +4Has examples (10 code blocks)
    • +1License stated

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