api-design — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited api-design (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.
An API (a function, module, endpoint, or library surface) is a contract others depend on. Design the smallest, clearest one that does the job.
well and the obvious call is the correct one, the design is good.
illegal states unrepresentable; require the essential args, default the rest. The easy path should be the safe path.
name is a future maintenance promise. Fewer, well-named entry points beat many overlapping ones.
the surrounding code so callers can predict it.
Decide how errors surface (exception vs result) and be uniform.
over breaking signatures. If you must break, version it and migrate (see database-migrations / breaking-change discipline).
surface you'll maintain forever. Add them when a real caller needs them.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.