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
- 포크
- 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에서 보기