SKILLEMALL.ai

CB eas-simulator

Curated upstream guidance for Eas Simulator; use when the workflow matches the user goal.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 5 files body ≈ 6 214 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Curated upstream guidance for Eas Simulator; use when the workflow matches the user goal.

As a process B 73/100 · Nearly there — weak spots: result and completion

ProcedureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
68
Run on models
none yet
Process rating
B
73/100
Nearly there
Result and completion w 14
0
When it triggers w 12
50
Inputs and preconditions w 11
70
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: eas-simulator (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: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 6214 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "source_repo"
  • note frontmatter-key unknown frontmatter key "source_type"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "date_added"
  • note frontmatter-key unknown frontmatter key "risk"
  • note edit-residue the text marks something as outdated (lines 64): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 73/100

  • 0Result and completion. Does not say what the result is
  • 50When it triggers. No condition that starts the skill
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 6214 tokens
  • 85Steps. 46 steps, 1 vague phrases
  • 100Tools and files. Tools declared in frontmatter
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 17 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (11 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 89: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • +2Single-language instructions
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 46 items
  • +4Has examples (7 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)
  • +1License stated

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