Slide 14
Skill Layer
Explain reusable skills as practical capability units.
Source markdown
This page is generated from the canonical slide file in the repository and the supporting references listed below.
Key points
- Skills are scoped recipes with clear entry points.
- Registry-driven skills support phased rollout and parity checks.
- Skills bridge policy documents and execution behaviour.
Speaker notes
- Use one example skill from `lightspeed-github-ops`.
- Explain why skills reduce prompt drift and tribal knowledge.
Accessibility notes
- Keep layout simple: title + 3 bullets + one visual zone.
- Use minimal visuals (one icon, one screenshot, or one simple diagram only).
- Avoid dense process diagrams, nested callouts, and complex animation.
- Keep on-slide text short (roughly 25-40 words total where possible).
- Use high contrast and consistent spacing; prioritise readability over decoration.
References
`skills/README.md` Reference used in this slide `skills/SKILL_REGISTRY.json` Reference used in this slide `plugins/lightspeed-github-ops/skills/lightspeed-pr-review/SKILL.md` Reference used in this slide `plugins/lightspeed-github-ops/skills/lightspeed-label-governance/SKILL.md` Reference used in this slide