skill-registry-composition-and-feature-gating-492722 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited skill-registry-composition-and-feature-gating-492722 (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.
Domain: command-surfaces Trigger: Use when a coding agent assembles skills or prompt commands from multiple sources and optional features can enable, disable, or delay some of them. Source Pattern: Distilled from reviewed command-surface, registry-bootstrap, and dynamic-skill loading implementations.
Assemble the registry in explicit phases instead of letting sources merge opportunistically. Start from the always-on local surface, then layer bundled skills, project-local skills, plugin-provided entries, and remote or MCP-discovered skills in a stable order. Apply feature gates before importing or materializing each optional phase so disabled sources do not cost startup time or leak partial entries into the merged view. After composition, dedupe by canonical command identity and memoize the final snapshot so listing, search, and execution all see the same result.
If a terminal coding agent loads built-in skills, project-local skills, and MCP-discovered prompt tools, first collect the always-on built-ins, then project-local skills, then gated remote sources. Dedupe the combined list, cache that snapshot, and feed the same snapshot to help menus, slash-command discovery, and command execution.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.