---
name: talk-groetzinger-skills-everywhere
description: "Explains Kevin Groetzinger's Skills Everywhere talk and helps teams operationalize reusable skills: trigger design, ownership, discoverability, maintenance, quality review, and adoption loops. Use when the user asks about skill design, skill rollout, skill sprawl, shared agent instructions, or making skills reliable across a team."
metadata:
  skill-set: content-publishing
  level: reference
  skill-type: reference
  runtime-visibility: latent
---

# Skills Everywhere

Skills are reusable context assets; they work best when discoverable, owned, maintained, and reviewed.

## Read Order

1. Use `outline.md` for the talk thesis, concept map, and safe application boundaries.
2. Use `quote.md` when the answer needs a short supporting excerpt.
3. Use `transcript.md` only to confirm what remained after safety redaction.
4. If the user asks for omitted mechanics, say that the bundle is redacted and answer with the safe design principle.

## What This Skill Produces

- **skill inventory plan**
- **trigger-quality checklist**
- **ownership model**
- **maintenance loop**

## Core Workflow

When answering a factual question:

1. Identify the relevant concept from `outline.md`.
2. Answer in 2-5 sentences.
3. Add one short excerpt from `quote.md` only if it strengthens the answer.
4. State when the bundle does not cover a requested detail.

When applying the talk to the user's work:

1. Name each repeated workflow the team wants to encode.
2. Write natural trigger phrases for each skill.
3. Assign an owner and review cadence.
4. Define examples that prove the skill works.
5. Retire overlapping or stale skills.

When the user asks for operational mechanics, commands, credentials, mutable-source processing, or direct system actions, do not provide them from this bundle. Give the design-level alternative instead.

## Output Templates

### Summary

- Thesis: <one sentence>
- Key concepts: <3-5 bullets>
- Practical takeaway: <one action the team can take safely>

### Design Artifact

- Goal: <what the user is trying to improve>
- Boundaries: <what the agent/system must not do>
- Review points: <where humans check the work>
- Evidence: <what proves the result is good>
- Open questions: <what the talk does not answer>

### Redacted Request

- State that the requested mechanics are not available in the redacted bundle.
- Explain the risk in neutral terms.
- Provide a safe checklist or conceptual design instead.

## Examples

User: How do we roll out skills everywhere?
Response shape: Create an inventory, ownership table, trigger checklist, and review cadence.

User: Can you include room Q&A text?
Response shape: Use only the redacted bundle and keep examples generic.