<skill name; MUST equal the parent folder name of SKILL.md; lowercase-hyphenated> — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited <skill name; MUST equal the parent folder name of SKILL.md; lowercase-hyphenated> (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
[ONLY FOR TEMPLATE EXECUTOR: imperative bullet points, shorter lines, distinguish references to repository files vs instructions; skill/subagent names will be in context already, so just reference it. the rest of instruction folder files: rules/templates/workflows/assets/subfolders of skill/etc must be loaded via the typed aliases (USE SKILL/FLOW, INVOKE SUBAGENT, APPLY PHASE, READ|APPLY RULE|TEMPLATE|SKILL FILE, LIST) to be used]
<[the_skill_name]>
<role>
[Optional, Define role with specialization of the agent executing this skill, use expressive language, seniority, brilliant and short]
</role>
<when_to_use_skill>
[KEEP THIS VERY SHORT. Define a problem and retrospectively introspectively validation proof that this prompt actually solves the problem, explain the scenarios, conditions, or situations where this skill should be used]
</when_to_use_skill>
<core_concepts>
[Optional, KEEP THIS VERY SHORT, Describe the fundamental concepts, principles, definitions and explanations required to properly execute the skill]
</core_concepts>
<process>
[Optional, KEEP THIS VERY SHORT, Every line is an ACTION (imperative verb) or a GATE (condition), No explaining what the agent already knows how to do, Define contracts/structures ONCE, DRY, No vague qualifiers, No patronizing, No tautology, No filler words]
</process>
<validation_checklist>
[Optional, KEEP THIS VERY SHORT, do NOT repeat the rest of the prompt, it must not just restate the same: prompt tells what to do, instead it should be proof-oriented — observable evidence that the output is correct, proof that work was done correctly]
...
</validation_checklist>
<best_practices>
[Optional, KEEP THIS VERY SHORT, do NOT repeat, List recommended practices, tips, and guidelines for effectively using this skill]
...
</best_practices>
<pitfalls>
[Optional section, KEEP THIS VERY SHORT, do NOT repeat, provide unexpected mistakes, edge cases, caveats, unusual, errors, gotchas, traps, non-obvious patterns or issues to take into account or avoid]
</pitfalls>
<resources>
[Optional, List helpful resources, references, or related materials, do not duplicate]
...
</resources>
<templates>
[Optional, Define what this skill produces and provide templates or examples of the output format]
</templates>
</[the_skill_name]>
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.