Install Governance

Install Governance

Skill installation is a small supply-chain decision. The curator should treat it as reviewable and reversible.

Default Policy

• Do not silently install unknown third-party skills.
• Show candidates, scores, and risks before installing.
• Install only the selected skill folder when possible.
• Do not bulk-install large awesome lists.
• Preserve a timestamped backup if a destination already exists.
• After install, read the installed SKILL.md and verify it still matches the current task.

Candidate Presentation

Before installation, present:

Field	Example
Repository	owner/repo
Skill path	path/to/skill
Why it matches	Task fit and expected reuse
Repository signals	Stars, forks, update date, license
Score and tier	Strict, relaxed, exploratory
Safety notes	Risks and unknowns
Install target	Codex, Claude Code, or both

Post-Install Behavior

When the user approves installing a skill, treat that approval as intent to use the skill for the current task unless the user explicitly asked only to install it.

After successful install:

1. Read the installed SKILL.md.
2. Confirm name, description, and body match the task.
3. Apply it to the user's original task if safe.
4. Print future invocation syntax.

Invocation examples:

Codex: $skill-name ...
Claude Code: /skill-name ...

When Not to Invoke

Do not invoke a newly installed skill if it proves mismatched, unsafe, overbroad, or impossible to use in the current environment. Explain the reason and suggest disable, quarantine, or removal.