SKILLEMALL.ai

CC triage-validation

Finding validation before writing any report

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

Finding validation before writing any report

As a process C 51/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

AnalyzerSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
C
85/100
safety, quality, tests
Safety 60%
96
Quality 40%
69
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
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: triage-validation (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 · 4

✓ No critical or high findings

Medium and low: 4
  • low Risky intent intent-offensive-security SKILL.md:68
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - **High**: Mass PII exfil, privilege escalation, internal SSRF with data, stored XSS all users
  • low Risky intent intent-offensive-security SKILL.md:200
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
    [ ] Google: "TARGET_NAME ENDPOINT_NAME bug bounty"
    detector
  • low Risky intent intent-offensive-security SKILL.md:221
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    CORS credentials cannot be read with a literal Access-Control-Allow-Origin wildcard and credentials mode under normal browser enforcement; demonstrate actual origin/header/client conditions. A takeove
  • low Concealment en-hide-from-user SKILL.md:327
    Instruction to hide actions from the user (negated — the text forbids it)
    The retraction template in the RETRACTION DISCIPLINE section above is the canonical format. Don't silently delete — append a retraction appendix to the engagement report instead.
    negated

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5527 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"

Process rating: all ten parameters 51/100

  • 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
  • 30Running it twice. 11 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 70Execution cost. Instruction body is 5527 tokens
  • 100Steps. 49 steps
  • 100Consistency. Name and required fields are in place
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 13 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)
  • +3Description length 44: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 31 headings
  • +3Step-by-step instructions: 49 items
  • +4Has examples (9 code blocks)
  • +1License stated

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