Talk Groetzinger Skills Everywhere
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.
Install
$ agentstack add skill-jscraik-agent-skills-talk-groetzinger-skills-everywhere ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Skills Everywhere
Skills are reusable context assets; they work best when discoverable, owned, maintained, and reviewed.
Read Order
- Use
outline.mdfor the talk thesis, concept map, and safe application boundaries. - Use
quote.mdwhen the answer needs a short supporting excerpt. - Use
transcript.mdonly to confirm what remained after safety redaction. - 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:
- Identify the relevant concept from
outline.md. - Answer in 2-5 sentences.
- Add one short excerpt from
quote.mdonly if it strengthens the answer. - State when the bundle does not cover a requested detail.
When applying the talk to the user's work:
- Name each repeated workflow the team wants to encode.
- Write natural trigger phrases for each skill.
- Assign an owner and review cadence.
- Define examples that prove the skill works.
- 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:
- Key concepts:
- Practical takeaway:
Design Artifact
- Goal:
- Boundaries:
- Review points:
- Evidence:
- Open questions:
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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jscraik
- Source: jscraik/Agent-Skills
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.