SKILLEMALL.ai
GitHub ↗ RU Sign in

AC pretext

Build creative browser demos with DOM-free text layout.

NousResearch/hermes-agent Hermes author: NousResearch MIT 4 files body ≈ 3 374 tokens Open the sourcegithub.com↗ analyzed 29 h ago

Build creative browser demos with DOM-free text layout.

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

GeneratorGitHubDesignMedia and videotype 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%
83
Run on models
none yet
Process rating
C
55/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: 4. 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 55/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
    • 30Running it twice. 1 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
    • 60Consistency. The Hermes dialect needs category and tags
    • 100Steps. 69 steps
    • 100When it triggers. States when to use and when not to
    • 100Execution cost. Instruction body is 3374 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • 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
    • +3Description length 55: 120–800 characters recommended
    • +3Output format is not stated: the model decides each time
    • -5TODO / placeholder text left in the skill
    • -2localhost URLs: will not work for another user
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +4Structure: 15 headings
    • +3Step-by-step instructions: 69 items
    • +4Has examples (5 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)
    • +1License stated

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