# Adaptable Skill examples

Read when the customer asks which Skill templates are available or wants to create one. These are ATTACHIES: eleven complete Skill examples shipped as adaptable templates, not registered/installed Skills or native Pi prompt templates. A user-specific Skill created from one is a PRIVATE, not a Workbench publication asset. The bundled authoring method is an INTERNAL; the separately offered Writing for Agents example is an ATTACHIE for creating the customer's own Skill.

| Example | Use |
| --- | --- |
| [User-facing orchestrator](templates/user-facing-orchestrator/SKILL.md) | Lead collaboration, decisions and bounded delegation using the customer's chosen behavioral archetype. |
| [Coding](templates/coding-skill/SKILL.md) | An explicitly commissioned coding workflow with Planning, Direct and selected execution techniques. |
| [Herdr workflow](templates/herdr-workflow/SKILL.md) | Coordinate authorized native Herdr work while preserving user panes and ownership. |
| [Intercom protocol](templates/intercom-protocol/SKILL.md) | Keep session-to-session exchanges bounded, quiet and tied to a specific purpose. |
| [KISS](templates/kiss/SKILL.md) | Choose the simplest complete and truthful approach to planning and decisions. |
| [Grill-Me](templates/grill-me/SKILL.md) | Resolve material decisions through research and a documented, dependency-aware Grill. |
| [Step-by-Step](templates/step-by-step/SKILL.md) | Keep iterative conversation focused on one current unit. |
| [Natural Writing](templates/natural-writing/SKILL.md) | Revise human-facing prose without changing its meaning or evidence. |
| [Writing for Agents](templates/writing-for-agents/SKILL.md) | Matt Pocock's complete original writing method, with a separate native Pi mechanics reference. |
| [Evidence review](templates/evidence-review.md) | Read-only review of supplied technical material, separating supported findings from uncertainty. |
| [Decision brief](templates/decision-brief.md) | A concise, source-grounded recommendation when choosing a technical approach. |

Read the chosen example before describing its actual content. For the nine directory-based examples, also read the [adaptation guide](templates/ADAPTATION.md) and the chosen directory's `CUSTOMIZE.md` when present. Inspect actual tools and configured sources first; ask only material missing choices. A user-facing archetype is the customer's choice, not a supplied personality. If a required capability is absent, explain the gap and offer relevant extension research; installation or activation still needs its actual grant. There is no mandatory questionnaire.

Keep supporting files and selected sibling relationships intact, or resolve their pointers to the customer's actual existing sources. Do not create duplicate owners or promise tools from template text. The [source note](templates/SOURCE.md) records the delivered snapshot and license boundaries.

To create the customer's own Skill, follow [Skill authoring](skill-authoring.md). Adapt the name/description/trigger, inputs, relevant procedure, completion/output and concrete access/tool limits to the confirmed need. Select an actually configured native destination with the customer. A new directory with its real `SKILL.md` becomes the customer's responsible original only after the creation grant; use the shared native archive gate before any existing-original overwrite. Native Pi owns resource inclusion/loading.

Report the created path and observed discovery/loading state. Copying an example is not installation, activation or proof of model behavior; reload and functional checks need their actual authorization. Do not install these examples merely because Workbench offered them.