stacks — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited stacks (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.
One home for the per-stack structure & build conventions of stacks that fall outside the pack's implicit default (the web stack — TS/Supabase/PWA — which every other skill already assumes). One skill, many stacks: each stack is a folder under references/, so breadth grows without adding skills or spending a trigger per stack.
references/<stack>/ files for its layering, build, tests, formatting and release flow.
eskills:stack-gotchas (it carries thediagnose-and-recover recipes).
references/<stack>/ holds the concrete, copy-ready conventions for that stack, each pattern traced to a real repo. Read the folder for the stack you're in.
| Stack | Folder | Status |
|---|---|---|
| Flipper Zero FAP (C) | references/flipper/ | architecture · build-and-test · formatting · release-please |
| Django | references/django/ | _planned_ |
| Flask | references/flask/ | _planned_ |
| FastAPI | references/fastapi/ | _planned_ |
Adding a stack = a new references/<stack>/ folder (and a row above). No new skill, no cap change — that's the point.
hygiene, branches/PRs live in `standards` (stack-agnostic).
A stack earns a folder only when it's genuinely outside that default (embedded, native mobile, a non-JS backend…).
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.