skill-supply-chain-audit

# Skill Supply Chain Audit Treat the target as untrusted. Produce an evidence-backed disposition without executing package code by default. ## Inputs Collect or state: - Target path, archive, repository snapshot, or exact version/commit. - Claimed purpose, publisher, source URL, license, and expected capabilities. - Intended runtime, available tools, requested permissions, and data sensitivity. - Known-good baseline or prior version when this is an update. - User constraints for network access, sandboxing, and dynamic testing. If provenance or version is unknown, record it as unknown; do not infer trust from popularity. ## Output contract Return: 1. Scope, target hash/version, provenance, method, and audit limitations. 2. A disposition: `approve`, `approve-with-constraints`, `quarantine`, or `reject`. 3. A behavior inventory covering instructions, executables, dependencies, endpoints, credentials, filesystem reach, and persistence. 4. Findings with stable IDs, severity, confidence, exact evidence, exploit preconditions, impact, and remediation. 5. Required permission constraints and a verification plan. 6. Residual risks and unanswered questions. Label each claim `observed`, `inferred`, or `unknown`. A clean heuristic scan is not proof of safety. ## Workflow ### 1. Establish a safe inspection boundary - Work read-only on a copy or immutable snapshot. - Do not import modules, run setup hooks, install dependencies, render active content, open embedded links, or invo...