project-core-dev — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited project-core-dev (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.
This is a composable overlay, not a standalone workflow. Use alongside the repo's principle skill (e.g. coding-guidance-cpp) for normal feature work and bug fixes in repo-owned code.
The task is a feature, bug fix, or refactor in repo-owned code that needs a standard build-test-format-analyze validation pass.
Vendored dependency changes (use project-vendor-boundary), release/packaging work (use project-release-maintainer), config/test-focused work (use project-config-and-tests), or environment diagnosis (use project-platform-diagnose).
Run the repo's equivalents of these steps before finishing:
--help or --version on the main binary)justifies it
change, state the exact gap and the narrowest next command that would close it
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.