issue-triage — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited issue-triage (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 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.
A good issue is half the fix. Whether filing or triaging, drive toward a crisp, reproducible statement of the problem.
a minimal, deterministic way to trigger it. If you can't reproduce it, say what you tried and what info is still needed — don't guess at a fix.
(version, OS, config), and the actual error/output (not a paraphrase).
existing issues first — link duplicates instead of forking the discussion.
how many users hit it. Be honest; not everything is P0.
and how to know it's fixed (the repro becomes the acceptance test).
its repro so it can't silently come back (see test-driven-development).
Red flag: "it's broken" with no repro, version, or expected behaviour — that's not yet an issue, it's a prompt to gather more.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.