A rollout checklist you can actually use
Here's the whole chapter, turned into a checklist for the moment you actually deploy a skill to a team. Run it top to bottom each time.
1. Is this worth a skill? Recurring, standardized, done by several people, costly to get wrong. If it doesn't fit, leave it as a prompt.
2. Where did the skill come from? Built in-house, from a reputable source, or untrusted. If untrusted, it gets a full audit by someone who can read what it does, or it doesn't get deployed.
3. Does it respect its guardrails? Drafts not verdicts, assists not decides, a human approves the consequential moves. An HR or legal or payments skill that crosses this line fails here.
4. Has it been evaluated? Three to five representative test cases, expected results checked. It passes on real examples before it goes live, not after.
5. Who owns it? One named person is accountable for this skill: keeping it current, re-evaluating it, retiring it when it's stale.
6. How is it deployed? Admin provisioning for a company standard, direct sharing for a small group, the directory for opt-in. Match the deployment to how the skill should spread.
7. When is it reviewed again? A date. Skills drift. Put the next review on the calendar now.
Seven questions. None of them slow you down much, and together they're the difference between skills that quietly make your team better and skills that quietly make your team wrong. Print this. Use it every time a skill is about to reach more than one person.
A rollout checklist you can actually use
Here's the whole chapter, turned into a checklist for the moment you actually deploy a skill to a team. Run it top to bottom each time.
1. Is this worth a skill? Recurring, standardized, done by several people, costly to get wrong. If it doesn't fit, leave it as a prompt.
2. Where did the skill come from? Built in-house, from a reputable source, or untrusted. If untrusted, it gets a full audit by someone who can read what it does, or it doesn't get deployed.
3. Does it respect its guardrails? Drafts not verdicts, assists not decides, a human approves the consequential moves. An HR or legal or payments skill that crosses this line fails here.
4. Has it been evaluated? Three to five representative test cases, expected results checked. It passes on real examples before it goes live, not after.
5. Who owns it? One named person is accountable for this skill: keeping it current, re-evaluating it, retiring it when it's stale.
6. How is it deployed? Admin provisioning for a company standard, direct sharing for a small group, the directory for opt-in. Match the deployment to how the skill should spread.
7. When is it reviewed again? A date. Skills drift. Put the next review on the calendar now.
Seven questions. None of them slow you down much, and together they're the difference between skills that quietly make your team better and skills that quietly make your team wrong. Print this. Use it every time a skill is about to reach more than one person.