菜单
Internal 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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
| name | mushanghai-canon |
| description | Internal 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. |
| when_to_use | Loaded only by other muShanghai skills via prerequisite reads to programmatic context. Do not invoke this skill directly from a user message. |
| allowed-tools | Read |
| disable-model-invocation | true |
Valid for: May 2026 cycle. Update dates, leads, and tracks before any later reuse.
Do not invoke this skill on user input. This is a read-only canon. Other muShanghai skills load these references directly.
When another muShanghai skill says "load canon," that skill should read one or more of:
references/two-cohorts.md - the two parallel cohort framingreferences/three-tracks.md - Decoding TCM / Lifestyle / Proof of Livingreferences/proof-of-living.md - Proof of Living track spec and Build in Public parent frameworkreferences/may-2026-calendar.md - full key-date tablereferences/four-musts.md - Problem / Monitoring / Intervention / Deliverablesreferences/safety.md - what NOT to paste, consent, high-risk escalationreferences/canonical-sources.md - pointers to repo ROLE.md filesREADME.md and the three */ROLE.md files in the repo root are the canonical truth. The files in this skill's references/ are compact excerpts. If they diverge, the repo docs win.