decision-deck
Skill1 starsChanged 3 months agoNo licenceView on GitHub
会上讲的汇报 deck：把一份已经立住的方案、调研结论或成果，压成一句判断、三件事、一个决策动作，\n做成一页一观点的 deck，配口语讲稿和读秒。覆盖脑暴会、方向会、评审会、季度会、CEO 同步这类\n有人站着讲、会议室要产出决策或讨论的场合。它只管\"会上十分钟怎么讲\"：内容对不对归 proposal-playbook，\n异步发出去的单张图归 mexc-infographic。来源：2026-10-19 E 哥公开的汇报标准，他点名表扬的三份材料的拆解，\n以及 2026-10-21 到 10-23 广场规划 deck 十一版迭代里被打回和被认可的原话。\n\n触发时机（宁可多触发也不要漏触发）：\n- 用户说\"做个 PPT / deck / 汇报页 / 幻灯片\"、\"讲十分钟\"、\"脑暴会 / 脑爆会\"、\"过会要讲\"、\"会上同步\"、\"给马哥讲\"、\"给 E 哥讲\"\n- 用户说\"按 E 哥的标准\"、\"像 Hedy 那份\"、\"一页一个观点\"、\"只讲三件事\"、\"用问题开场\"、\"要有反差\"、\"有主线有逻辑有观点\"\n- 用户说\"老板不看字\"、\"视觉化呈现\"、\"主线要贯穿\"、\"格局要打开\"、\"灰色小字去掉\"、\"价值没体现出来\"、\"有点空\"\n- 用户说\"把这份方案 / 调研 / 文档 / 一图流压成汇报\"、\"讲稿\"、\"口播\"、\"读秒\"、\"排练\"、\"弹药页\"\n- 用户给了方案、调研报告、一图流或数据，并提到要在会上讲、要汇报、要分享\n- 用户说\"竞品调研给领导看\"、\"调研结论怎么呈现\"、\"这次分享怎么做\"\n\n不要用于：发群里让人自己看的图（mexc-infographic）、飞书文档（lark-docx-authoring / proposal-playbook）、\n周会文档一行一条（group-sync-messenger）、PRD 评审（prd-authoring-kit）、成果数据的口径和归因（okr-report 出内容，\n本 skill 只管讲法）、可交互产品演示（showcase-demo）、产品广告片（ai-demo-video-workflow）\n
1 other project uses a version of this.
Adopted by
Most recently taken up by
- jbouder/skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- jbouder/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository43 other files it gives its agents.
- alpha-labSkill
- binance-trader-scraperSkill
- chrome-cdpSkill
- codex-auditSkill
- comparison-dashboardSkill
- data-request-kitSkill
- demo-video-kitSkill
- dev-plannerSkill
- dify-workflow-architectSkill
- docsSkill
- docxSkill
- ealy-pitchSkill
- ego-messengerSkill
- exec-proposalSkill
- friction-playbookSkill
- git-cleanupSkill
- google-workspaceSkill
- group-sync-messengerSkill
- import-memorySkill
- jira-card-kitSkill
- lark-docx-authoringSkill
- mexc-daily-insightSkill
- mexc-infographicSkill
- morningSkill
- okr-reportSkill
- pdfSkill
- pm-interview-prepSkill
- polymarket-execution-auditSkill
- pptxSkill
- prd-authoring-kitSkill
- prd-kit-releaseSkill
- prd-reviewerSkill
- prd-writerSkill
- proposal-deckSkill
- proposal-playbookSkill
- pvp-team-designerSkill
- quant-code-reviewSkill
- session-memorySkill
- showcase-demoSkill
- skill-creatorSkill
- user-research-reportSkill
- video-makingSkill
- xlsxSkill
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.