Safe Install Checklist
Core Workflow
- Identify source, version, publisher, install method, host, and intended use.
- Confirm the skill was reviewed for instructions, scripts, dependencies, secrets, data movement, and required permissions.
- Recommend least-privilege install options: pin version, copy manually, inspect before enabling, disable scripts, or run read-only first.
- Define approval gates for write access, network access, MCP scopes, customer data, production systems, and outbound messages.
- List post-install checks and re-review triggers.
- Conclude with approve, approve with changes, block, or defer.
Safety Rules
- Do not recommend installing unreviewed third-party skills into a privileged agent environment.
- Do not make GitHub CLI, Codex, or any one host the only safe path.
- Do not approve auto-updating skill sources for high-risk workflows without a re-review process.
Deliverable Shape
For safe install recommendations, provide:
- Source and version
- Intended host and install method
- Pre-install checks
- Required mitigations
- Least-privilege install path
- Approval gates
- Post-install checks
- Recommendation
References
- Read
references/safe-install-checklist.mdwhen producing install guidance or reviewing whether a skill is safe to enable.