Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add nthnclrk/enablement-skills --skill discovery-and-demo-structuregit clone --depth 1 https://github.com/nthnclrk/enablement-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/nthnclrk/enablement-skills/discovery-and-demo-structure)<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/discovery-and-demo-structure"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/discovery-and-demo-structure/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/discovery-and-demo-structure"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/discovery-and-demo-structure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00084 | $0.00741 |
| Opus 5 | $0.00042 | $0.00370 |
| Sonnet 5 | $0.00017 | $0.00148 |
| Haiku 4.5 | $0.00008 | $0.00074 |
Grade A, and why
discovery-and-demo-structure scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovery and demo structure
Demo only after a buying signal. If the flow shows product before it knows what "good" looks like for this buyer, rewrite it.
This skill designs the meeting architecture. For spoken lines inside an existing structure, use talk-track-builder.
Gated. "You said late handoffs hit the Friday ship. If I show the missed-window alert and the owner assignment, does that test the thing you would actually need to believe?"
Dump. "Let me start with the platform overview, then walk you through all six modules."
If there is no credible decision this meeting can produce, propose one before you build the path.
Confirm Inputs First
Ask only for what changes the flow:
- Meeting type: discovery, demo, or combined
- Who is in the room, time available, and the decision this meeting is for
- What is already known versus hypothesized
- Approved capabilities, proof, and demo-environment limits
Do not invent buyer commitments, metrics, or product claims.
Read The Right Reference
Read references/discovery-demo-framework.md for topic patterns, demo-gating rules, and meeting modes. Skip it if you are only tightening an existing guide.
Default Workflow
- Name the decision. What the buyer should be able to decide next, and what the seller must learn or prove. Done when that sentence is specific.
- Separate knowns from hypotheses. Each consequential unknown becomes a question, not a fact in the script.
- Build an adaptive path. For each topic: why it matters, an opening, what to listen for, if/then branches. Prioritize. This is not a list that must be completed in order.
- Plan stakeholder coverage. What each role can confirm, what needs someone else, where views may conflict.
- Gate the demo. Each block maps to an expressed outcome, criterion, or risk. Use only verified capabilities. Include the stop condition.
- Write the transition. Restate what you heard. Ask permission to show the matching path.
- Design the close. Recap confirmed outcomes and open questions. Ask for a next step. Do not write a proposed action as if the buyer already agreed.
- Name the few fields to capture after the call.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 71 lines · 84 tokens per session scan A 593ec36aa73a
discovery-and-demo-structure is a skill published in the GitHub repository nthnclrk/enablement-skills (13 stars, last pushed 23d ago), licensed MIT. It adds 84 tokens to every session and 741 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…