skillify — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited skillify (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
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 procedure you repeat is a procedure worth recording once. The third time you walk the same path, pave it — write it down as a skill so the path exists for everyone after you.
Capture it when all of these hold:
Skip it when any of these apply:
Pull the pattern apart into three buckets:
Keep the frontmatter to just two keys. The description does the heavy lifting: it is how the skill gets matched later, so write it in the third person and state both what the skill does and when to reach for it (and when not to).
---
name: kebab-case-name
description: One to a few sentences, third person, describing what the skill does and the
situations that call for it, plus what it is not for. No first person.
---
# Skill Name
A short framing line — the principle behind the skill.
## When it applies
- Conditions that should trigger it
- Conditions that should rule it out
## Procedure
### 1. First action
Concrete, do-this instructions.
### 2. Next action
...
### N. Confirm it worked
How to tell the procedure succeeded.
## Guidance
A handful of rules worth remembering..aim-agents/skills/<skill-name>/SKILL.mdThe folder name and the name field must match exactly, both in lowercase-hyphen form.
name and description, both accurate.| Style | Shape | Examples |
|---|---|---|
| Action | verb-noun | verify-changes, simplify-code |
| Subject area | domain-aspect | database-design, api-patterns |
| Around a tool | tool-patterns | tailwind-patterns |
Conventions: lowercase-hyphen only, two or three words, plainly descriptive rather than witty, and no abbreviations unless they are universally understood.
| Check | What "good" looks like |
|---|---|
| Not a duplicate | A search of the skills directory turns up nothing equivalent |
| Portable | Useful beyond the project it was born in |
| Complete | Has framing, applicability, a procedure, and a success check |
| Frontmatter | Exactly name and description, both correct |
| Self-contained | Readable and actionable with zero outside context |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.