SKILLEMALL.ai
GitHub ↗ RU Sign in

AB design-it

Routes frontend design tasks to 48 specific UI styles. Triggers for websites, app screens, or UI components requesting a specific aesthetic.

sickn33/agentic-awesome-skills Hermes author: sickn33 MIT 1 file body ≈ 1 432 tokens Open the sourcegithub.com↗ analyzed 25 h ago

Routes frontend design tasks to 48 specific UI styles.

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

ProcedureDesigntype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code Hermes Agent
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
B
67/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: design-it (sickn33/agentic-awesome-skills)

How to improve

  1. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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 140 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "risk"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "source_type"
  • note frontmatter-key unknown frontmatter key "date_added"
  • note frontmatter-key unknown frontmatter key "tools"

Process rating: all ten parameters 67/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 60Failures and branches. 2 branches
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 110 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1432 tokens
  • 100Running it twice. No mutating operations

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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 140: enough signal without eating the budget
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 110 items
  • +4Has examples (0 code blocks)

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