菜单
muShanghai Demo Day preparation skill for Experiment Leaders preparing a 5-minute presentation for BioBloom Demo Day May 22 at OpenFlow Bazaar or Longevity Month Demo Day June 5. Use when shaping a demo narrative, backup plan, visual anchor, and rehearsal checklist.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | mushanghai-demo-prep |
| description | muShanghai Demo Day preparation skill for Experiment Leaders preparing a 5-minute presentation for BioBloom Demo Day May 22 at OpenFlow Bazaar or Longevity Month Demo Day June 5. Use when shaping a demo narrative, backup plan, visual anchor, and rehearsal checklist. |
| when_to_use | Trigger phrases: 'prep my demo', '5-minute demo', 'demo day prep', 'plan B for demo', 'rehearse my demo', 'OpenFlow Bazaar demo', 'June 5 demo'. Do not trigger for proposal drafting or daily logging — use mushanghai-experiment-leader or mushanghai-participant-log instead. |
| allowed-tools | Read Write |
Valid for: May 2026 cycle. Use for BioBloom Demo Day on May 22 at OpenFlow Bazaar and Longevity Month Demo Day on June 5.
Prerequisite: Before doing anything else, read
../mushanghai-canon/references/safety.mdand../mushanghai-canon/references/four-musts.md. If they conflict with the repo role files, the role files win.
Before any other content or question, surface this banner:
Before we start, do NOT paste:
- Identifiable health data (HRV with timestamps + location, blood labs, body weight, sleep records)
- Real names of other participants
- Other people's data without their explicit consent
- Details of medical conditions, pregnancy, or current medication
muShanghai skills help you plan, log, and reflect. They do not provide medical advice. All experiments are for education, exploration, and self-observation only - not diagnosis or treatment. High-risk interventions (anything beyond lifestyle, breath, movement, or off-the-shelf wearables) require Track Leader approval AND escalation to the Month organizer.
If the user pasted anything from the never-paste list, stop and ask them to redact before continuing.
Goal: prepare a tight, reproducible 5-minute Demo Day presentation and write it to experiments/<track>/<seed-name>-demo.md.
First collect: experiment name, track, cohort, Experiment Leader display name, seed name, demo date, and source data or artifact links. Then show the proposed output path and filled content for confirmation before writing.
Use assets/demo-outline.md as the output template. Walk the user through exactly these steps:
assets/rehearsal-checklist.md and walk every item. Do not mark an item ready unless the user confirms it.After step 5, present the complete markdown draft and ask: "Write this to experiments/<track>/<seed-name>-demo.md?" Write only after confirmation.
../mushanghai-canon/references/proof-of-living.md.../mushanghai-canon/references/safety.md../mushanghai-canon/references/four-musts.md../mushanghai-canon/references/may-2026-calendar.md../mushanghai-canon/references/two-cohorts.md../mushanghai-canon/references/proof-of-living.mdInternal canon for the muShanghai Longevity Month 2026 program. Holds two-cohort framing, three tracks, May 2026 calendar, Four Musts, and safety policy. Loaded by other mushanghai-* skills as a prerequisite read. Never invoked directly by a user; not user-callable.
muShanghai Longevity Month 2026 experiment workflow. Use when a user needs proposal bootstrap, Track Leader review, approved-proposal participant SOP, consent + disclaimer document, or mid-experiment status handoff. Routes five modes: (A) Proposal Bootstrap, (B) TL Review, (C) SOP, (D) Consent, (E) Mid-experiment Status. Supports Longevity Month and BioBloom with unified May 19 proposal deadline.
muShanghai Longevity Month 2026 onboarding bootstrap. Use when a user is new to the program (typically the May 12 AI-Empowered Onboarding session) and needs to: (1) confirm Claude Code is installed, (2) install the obra/superpowers + mattpocock/skills skill packs, (2.5) install Tavily + Firecrawl web-search MCP servers for live evidence research, (3) run brainstorming or grill-me to surface their seed hypothesis and pick a cohort + track, (4) hand off to mushanghai-experiment-leader to draft their proposal.
Participant-facing muShanghai Longevity Month 2026 logging and BioBloom Recruitment Night guidance. Use when a participant says: log my day, today's log, daily reflection, join a BioBloom project, Recruitment Night, evaluate a pitch, or asks how to reflect on their own protocol experience. Not for proposal drafting or Track Leader review.
muShanghai post-experiment retrospective skill for Experiment Leaders after Demo Day: BioBloom retros start after May 22; Longevity Month retros start after June 5. Use for end-of-experiment summary, reproduction notes, what worked, what did not work, and next seed hypothesis.
muShanghai Track Leader operations skill. Use when a Track Leader needs to: (1) define track scope + core questions, (2) lock the track's tech stack (wearables, logging tools), (3) do on-the-spot BioBloom pitch triage at Recruitment Night (May 17), (4) run daily 🟢🟡🔴 traffic-light check-ins during the run window, (5) synthesize the track at end-of-cycle. Routes between five modes.