SKILLEMALL.ai

CD hunt-aspnet

Hunt ASP.NET-specific surface

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

Hunt ASP.NET-specific surface

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches

ProcedureSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
C
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
61
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
When it triggers w 12
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: hunt-aspnet (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 description-short description under 40 chars: too little signal for triggering
  • warning body-long SKILL.md body ≈ 5606 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 "license_source"
  • note frontmatter-key unknown frontmatter key "sources"
  • note frontmatter-key unknown frontmatter key "report_count"
  • note edit-residue the text marks something as outdated (lines 66, 67, 68): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 49/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 0Failures and branches. Linear process with no failure handling
  • 30Running it twice. 2 mutating operations with no state check
  • 60Tools and files. Uses tools (web, node) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 5606 tokens
  • 100Steps. 65 steps
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • low 12 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (7 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 29: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 65 items
  • +4Has examples (10 code blocks)
  • +1License stated

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