event-debrief SKILL.md skillA
event-debrief from samber/dev-event-organizer-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add samber/dev-event-organizer-skills/event-debrief@v1.1.0Pins v1.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- samber/dev-event-organizer-skills
- Path
skills/event-debrief/SKILL.md- Versions recorded
- 4
- Latest version
- v1.1.0, committed Oct 12, 2026
- First version recorded
- Aug 26, 2026
- Size
- 28,622 bytes
- Repository stars
- 4
- License
- MIT
Run the organizing team's own internal retrospective on one finished edition of a technical event - the blameless frame, the reconstructed timeline, what went well split from what went poorly, what fired reconciled against the risk register, budget plan and run of show, team-health findings, and dated lessons-learned entries each carrying an owner and a due date. Use whenever asked to run a post-event debrief, a post-mortem or a retrospective after a conference, meetup or hackathon, review an…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Event Debrief You run the organizing team's retrospective on one finished edition: the meeting, the reconstruction, the findings, and the log that reaches next edition's plan. Internal-facing only - nothing here reaches an attendee, a speaker or a sponsor. **Run it every edition, unconditionally.** The SRE incident-postmortem lineage this skill borrows from gates a postmortem on a severity threshold (SEV1/SEV2, an outage over fifteen minutes); that gate does not transfer. A quiet edition where nothing broke still gets a debrief - the goal is improving a recurring asset, not containing an incident. "It went fine, let's skip it" is the failure this rule exists to prevent. Five things arrive already decided. Read them, reconcile against them, never reopen them: | Sibling | Owns | You do | | ----------------------- | --------------------------------------------- | ----------------------------------------------------------------------------------------- | …
Read the whole file at its exact version.
How to install
mdr add samber/dev-event-organizer-skills/event-debrief@sha256:889bbf72607626d0The line at the top of this page pins the label v1.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ndjj7mblwwpswy7e)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 26, 2026 and Oct 12, 2026, about one every 16 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-10-12 | 7368d8a | 28,622 B | A | view · diff |
| v1.0.0 | 2026-09-13 | c1678c6 | 27,054 B | A | view · diff |
| v1.0.0 | 2026-08-26 | e7902c1 | 26,075 B | A | view · diff |
| v1.0.0 | 2026-08-26 | 8bd47d7 | 26,076 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (28622 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
samber/dev-event-organizer-skills · 4 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ndjj7mblwwpswy7e GET https://markdownregistry.com/api/v1/resolve?ref=samber/dev-event-organizer-skills/event-debrief GET https://markdownregistry.com/api/v1/blob/889bbf72607626d0107912a019f79292445e0043ea53c0cc18272495b67105e2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.