SKILLEMALL.ai

AF skill-priority-setup

Scans installed skills, suggests L0-L3 priority tiers, and auto-configures skill injection policy. Use when: setting up skill priorities, optimizing token budget, or migrating to tiered skill architecture.

modbender/skill-library-mcp Agent Skills author: modbender MIT 6 files body ≈ 995 tokens Open the sourcegithub.com analyzed 3 d ago

Scans installed skills, suggests L0-L3 priority tiers, and auto-configures skill injection policy.

As a process F 38/100 · Will not run — References files that are not bundled: ../SKILL_PRIORITY_POLICY.md

ProcedureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
74
Run on models
none yet
Process rating
F
38/100
Will not run
References files that are not bundled: ../SKILL_PRIORITY_POLICY.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../SKILL_PRIORITY_POLICY.md
  • note frontmatter-key unknown frontmatter key "clawhub"

Process rating: all ten parameters 38/100

Will not run. References files that are not bundled: ../SKILL_PRIORITY_POLICY.md
  • 0Tools and files. 1 referenced file(s) missing: ../SKILL_PRIORITY_POLICY.md
  • 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
  • 50Failures and branches. 0 branches, has a failure section
  • 85Steps. 40 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 995 tokens
  • 100Running it twice. Mutating operations check current state
  • 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
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -32 of 3 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 205: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 40 items
  • +4Has examples (3 code blocks)

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