write-an-event-recap
Turn an event record into an accurate recap with outcomes, resources, and next steps. Use when participants, sponsors, leaders, or the public need a durable summary after an event.
来源信息
- 仓库
- protosphinx/sphinxstack
- 最近来源活动
- 2026年7月29日 13:55
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 3
- Forks
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
2 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- write-an-event-recap
- category
- write
- description
- Turn an event record into an accurate recap with outcomes, resources, and next steps. Use when participants, sponsors, leaders, or the public need a durable summary after an event.
# write-an-event-recap
## Procedure
1. Confirm audience, purpose, publication channel, approvals, and available evidence.
2. Verify event name, date, attendance definition, speakers, sessions, commitments, and results.
3. Lead with what happened and why it matters rather than promotional adjectives.
4. Summarize key ideas, decisions, questions, resources, and next actions with source attribution.
5. Distinguish attendance, satisfaction, reach, output, outcome, and anecdote.
6. Add accessible recordings, transcripts, slides, links, image descriptions, and contact paths where approved.
7. Check quotes, names, photographs, consent, confidentiality, sponsor acknowledgement, and unresolved claims.
8. Publish the approved version and record later corrections.
## Guardrails
- Do not invent quotes, consensus, impact, attendance, or commitments.
- Never publish sensitive participant, incident, commercial, or access information without permission.
- Do not treat promotional reach as proof of participant outcome.
## Done
- A recap draft traces factual claims, quotes, outcomes, and actions to evidence
- Consent, attribution, access, links, and sponsor requirements are checked
- Publication approval and correction route are recorded
在 GitHub 查看