research-before-build — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited research-before-build (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 portable skill that pairs with the dep-scout MCP server. Its job: stop AI agents from reinventing wheels by always checking the right registry — crates.io (Rust), npm (JS/TS/frontend), PyPI (Python), pkg.go.dev (Go), Maven Central (Java/Kotlin) or NuGet (.NET) — for a mature, maintained package first.
When you are about to build a non-trivial piece of functionality:
find_packages with keywords describing thecapability plus the project's ecosystem (rust | npm | python | go | maven | nuget; js/ts/frontend → npm, py → python, golang → go, java/kotlin → maven, dotnet/csharp → nuget). Examples: {query:"async http client", ecosystem:"rust"}, {query:"react date picker", ecosystem:"frontend"}, {query:"json", ecosystem:"dotnet"}.
maintenance recency, version stability, and metadata completeness:
≥ 78 ✅ strongly recommended — reuse it.58–77 🟡 usable — resolve the listed warnings first.< 58 🟠/🔴 — compare alternatives or justify a from-scratch build.inspect_package with the exact name + ecosystemto confirm license, deprecation/yank status, and runtime/version requirements before depending on it.
find_mcp_serversto check the official registry for an existing one.
suitable exists and you are implementing it yourself.
Vue, Svelte, Angular…) all live on npm.
prefer concrete library names, or use inspect_package directly.
Most "new" features are solved problems. A maintained package carries fewer bugs, better security, and lower long-term cost than a hand-rolled reimplementation. The default should be reuse; building from scratch is the exception that needs a reason.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.