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 thin project overlay, not a standalone implementation workflow. Use it with matching implementation guidance only when repository-specific checks or gaps remain unclear. Omit it when another selected skill plus repo context already supplies exact commands and reporting obligations.
The task is a routine repo-owned change whose completion path is not yet concrete.
Use project-config-and-tests, project-platform-diagnose, project-release-maintainer, or project-vendor-boundary when that specialized concern leads. Do not use this skill to restate a generic validation checklist.
contributor docs, and presets. Identify authoritative commands and mandatory gates; do not invent a second workflow.
broad checks merely because they exist.
do not install tools, start services, or mutate the environment just to close a checklist.
would close each material gap without implying it passed.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.