SKILLEMALL.ai

AB runaway-guard

Cost-safety discipline for paid AI / inference APIs: treat $-cost as a third complexity dimension alongside time and space. Forces a written per-run $-cap, per-day $-cap, max-iterations bound, concurrency limit, and a matching provider-dashboard hard cap BEFORE any call site is written.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 1 file body ≈ 5 549 tokens Open the sourcegithub.com analyzed 2 d ago

Cost-safety discipline for paid AI / inference APIs: treat $-cost as a third complexity dimension alongside time and space.

As a process B 67/100 · Nearly there — weak spots: when it triggers, inputs and preconditions

ProcedureOperations and projectsAI 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%
75
Run on models
none yet
Process rating
B
67/100
Nearly there
Inputs and preconditions w 11
0
When it triggers w 12
20
Failures and branches w 10
50
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: runaway-guard (sickn33/agentic-awesome-skills)

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 body-long SKILL.md body ≈ 5549 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "risk"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "source_repo"
  • note frontmatter-key unknown frontmatter key "source_type"
  • note frontmatter-key unknown frontmatter key "date_added"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "license_source"

Process rating: all ten parameters 67/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 5549 tokens
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 93 steps
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low 15 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)
  • +2Single-language instructions
  • +3Description length 287: enough signal without eating the budget
  • +4Structure: 22 headings
  • +3Step-by-step instructions: 93 items
  • +3Output format is stated explicitly
  • +4Has examples (4 code blocks)
  • +1License stated

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