| name | performance |
| description | Use this skill to turn dry technical material into a polished demo, narrative walkthrough, or audience-aware presentation without dumbing it down. It focuses on pacing, reveal order, and memorable framing so the work lands in the room. |
| version | 1.0.0 |
| author | Wizards of the Ghosts |
| license | CC0-1.0 |
| compatibility | Hermes Agent skills system |
| metadata | {"hermes":{"tags":["skill","shipping-now","metaphorical","messaging-and-coordination","messaging","coordination","handoffs","rhetoric"]}} |
Performance
Stage technical substance so an audience can see why it matters.
What This Skill Does
Use this skill to turn dry technical material into a polished demo, narrative walkthrough, or audience-aware presentation without dumbing it down. It focuses on pacing, reveal order, and memorable framing so the work lands in the room.
In this grimoire, Performance is treated as a metaphorical skill with a shipping-now delivery profile.
Canonical reference input: Performance (skill).
When To Use
- You are turning docs, metrics, or a prototype into a demo, talk, launch note, or README.
- The content is sound, but the audience needs a stronger narrative arc to stay with it.
- You need polish, pacing, and audience energy rather than more raw detail.
Prerequisites
- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.
Procedure
- Restate the target, the success condition, and any no-touch boundaries before taking action.
- Identify the audience, medium, and the moment that should land hardest.
- Structure the material into a clear arc with reveals, evidence, and transitions that keep attention.
- Return a presentation-ready draft plus speaker, demo, or pacing notes.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A polished presentation, demo script, or narrative draft.
- A section order or story arc for the material.
- Notes on pacing, visuals, and likely audience questions.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- Do not hide critical caveats or uncertainty for the sake of applause.
- Keep polish in service of comprehension, not hype detached from evidence.
Verification
- Check that the result includes every deliverable promised above.
- Check that confirmed facts, assumptions, and inferences are visibly separated.
- Check that the metaphor still maps cleanly to a real operational mechanism.
Example Invocation
/performance turn this technical material into a polished presentation that will land with the intended audience
