ai-demo-assistant
Builds a scenario-driven content pack for a Microsoft 365 Copilot customer demo. From a customer name, line of business, and target personas, it proposes demo scenarios for operator approval, then generates fictional Word/PowerPoint/Excel example files plus an AI Demo Delivery Plan (persona roster with tenant-account mapping, email and Teams chat scripts, calendar meetings with agendas, a meeting transcript, and app-tagged Copilot prompt workflows grounded in the generated content). After approval it can OPTIONALLY seed the Office files into a customer-named OneDrive folder and optionally post the Teams chat scripts live; email, calendar, and recordings are drafted for manual loading. Use when the user asks to "set up a Copilot demo", "build demo content for a customer", "seed a demo tenant", "create a demo delivery plan", "fill a demo tenant with realistic content", or "generate demo scenarios and sample files". Do NOT use for sending real email, booking real calendar events, or produ
microsoft · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add microsoft/cat-agent-skills --skill ai-demo-assistant技能说明
name: ai-demo-assistant description: | Builds a scenario-driven content pack for a Microsoft 365 Copilot customer demo. From a customer name, line of business, and target personas, it proposes demo scenarios for operator approval, then generates fictional Word/PowerPoint/Excel example files plus an AI Demo Delivery Plan (persona roster with tenant-account mapping, email and Teams chat scripts, calendar meetings with agendas, a meeting transcript, and app-tagged Copilot prompt workflows grounded in the generated content). After approval it can OPTIONALLY seed the Office files into a customer-named OneDrive folder and optionally post the Teams chat scripts live; email, calendar, and recordings are drafted for manual loading. Use when the user asks to "set up a Copilot demo", "build demo content for a customer", "seed a demo tenant", "create a demo delivery plan", "fill a demo tenant with realistic content", or "generate demo scenarios and sample files". Do NOT use for sending real email, booking real calendar events, or production-tenant data. cowork: category: productivity icon: Rocket
AI Demo Assistant
Turns a customer name + line of business + target personas into a polished, scenario-driven content pack for a Microsoft 365 Copilot demo: example files plus a written delivery/provisioning plan. After operator approval, it can optionally seed the generated Office files into a customer-named OneDrive folder and optionally post the Teams chat scripts live — both gated on explicit confirmation. Everything else (email threads, calendar invites, meeting transcripts) is drafted for a human to load.
What can and can't be auto-seeded
| Asset | Auto-seed? | How |
|---|---|---|
| Word / PowerPoint / Excel files | Yes | Create a customer-named OneDrive folder and upload the files (Phase 3). |
| Teams chat messages | Optional, with constraints | Posts live via Graph; see Phase 4 caveats (timestamped now; one account posts only as itself). |
| Email threads | No | Drafted as scripts for manual paste/seed. Do not auto-send. |
| Calendar meetings | No | Drafted as scripts with agendas for manual creation. Do not auto-book. |
| Meeting recordings / transcripts | No — not possible via any API | Generate a transcript/script; to get a real recording, a person reads it aloud in a recorded Teams meeting. See Phase 4. |
The hard limits exist because Graph has no endpoint to backdate messages or to inject a recording/transcript — those are produced only by a live recorded meeting. Never claim a recording was seeded.
When NOT to Use
- Sending real email, booking real calendar events, or writing to a production tenant. This skill targets demo tenants and the operator's own OneDrive with fictional content only.
- Real customer data or PII. All generated content is fictional dummy data.
- Generic single-file asks ("make a deck", "write an email") with no demo framing — use the docx/pptx/xlsx skills directly.
Inputs (collect before building)
| Input | Required | Example |
|---|---|---|
| Customer name | Yes | "Contoso Manufacturing" |
| Line of business (LOB) | Yes | "Field Service Operations" |
| Target personas / roles | Yes | "Service Dispatcher, Field Tech, Ops Director" |
| Segment / size | Optional (default: Enterprise) | "SMB", "Public Sector" |
| Region / language / tone | Optional (default: US English, professional) | "UK English, formal" |
| # of scenarios | Optional (default: propose 3–5) | "4" |
| Demo tenant domain | Optional (default: placeholder {tenant-domain}) | "M365x84272.onmicrosoft.com" |
| OneDrive seeding target | Optional (default: operator's own OneDrive) | "seed to my OneDrive" / a specific account |
| Teams seeding | Optional (default: scripts only, no live post) | "post the chats too" |
If customer, LOB, or personas are missing, ask one concise question to fill the gaps. Do not over-interview — reasonable defaults cover everything else. Seeding target and Teams seeding are only needed at Phase 3/4; don't block the build on them.
Workflow
Phase 1 — Propose scenarios (confirmation gate)
- From the LOB + personas, infer 3–5 realistic, high-impact Copilot scenarios that map to a day-in-the-life of the named personas. Each scenario should show Copilot saving time across Outlook, Teams, and Office.
- Present the proposed scenarios as a short numbered list — each with a one-line title, the persona it serves, and the Copilot "wow moment" it demonstrates.
- Stop and ask the operator to approve, edit, or swap scenarios before building anything. Do not generate files until scenarios are confirmed.
- Pre-approval exception: if the operator supplied their own scenario list (or explicitly said "just build it") in the initial request, treat that as approval — restate the scenario set in one line and proceed to Phase 2. The gate exists to prevent wasted builds, not to force a redundant round trip.
Phase 2 — Build the content pack (after approval)
For the approved scenario set, generate every asset below. Use the customer name,
LOB, and personas throughout so content feels native. Save all deliverables to
the standard output directory for the current environment (the designated
output/ folder).
Before generating any Office file, read the relevant skill's SKILL.md (docx / pptx / xlsx) and follow it — these skills encode the validation and rendering steps that keep files from arriving corrupted or ugly.
Persona roster (build first — everything else references it).
Create a small cast of fictional characters: name, title, which scenarios they
appear in, and a mapping column for the demo tenant account the operator will
use to seed as them (use real demo-tenant aliases if the operator provided a
tenant domain, otherwise {firstname}@{tenant-domain} placeholders the operator
can find-and-replace). Reuse this exact cast — same spe