Add postmortem skill - #2
Open
Multipixelone wants to merge 1 commit into
Open
Conversation
Introduce the `postmortem` marketplace skill: reconstruct an incident from the exports it leaves behind (chat channel export, pager timeline, fix PRs, and metric data) into a blameless postmortem with a minute-accurate timeline that cites its source on every entry, gaps marked instead of filled, trigger and root cause separated from contributing factors, handles replaced by roles so no individual is named, and action items that carry owners and dates. - skills/postmortem/: SKILL.md, scripts/timeline.py (collect/render/check; Python standard library only), three references, the postmortem template, and a complete worked example under assets/example/. - marketplace.json: catalog entry (python_uv tier with no runtime packages, no network at runtime, helper script reviewed). - README.md: Current Status bullet.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the
postmortemmarketplace skill — write a blameless incident postmortemfrom the exports an incident leaves behind (chat channel export, pager timeline,
fix PRs, metric data). Every timeline entry cites its source; gaps are marked
instead of filled; trigger, root cause, and contributing factors are kept
separate (an unestablished root cause stays unknown); handles are replaced by
roles so no individual is named; and action items carry an owning role and a
calendar date. A local linter flags blameful phrasing, speculation, leaked
names, uncited timeline rows, and vague action items before publication.
What's included
skills/postmortem/SKILL.mdand three references (timeline reconstruction,blameless writing, contributing factors).
skills/postmortem/scripts/timeline.py—collect/render/check,Python standard library only.
skills/postmortem/pyproject.toml— declares zero runtime dependencies.skills/postmortem/assets/postmortem-template.mdand a complete workedexample under
assets/example/(five raw exports through the finished doc).marketplace.jsoncatalog entry and a README Current Status bullet.Dependencies & safety
tier: python_uv,recipes: [](nothing to install),system_capabilities: [python, uv].has_helper_scripts: true,runs_install_script: false,network_at_runtime: false— runs entirely on local files, no network.Verification
collectregeneratesassets/example/timeline.jsonandrenderregeneratesassets/example/postmortem.mdidentically to the committed files;check --stricton the finished example reports 0 findings.scripts/validate_skills.py,check-jsonschemaagainst
schemas/marketplace.schema.json,markdownlint-cli2,typos,and
gitleaks.uv run --project … python scripts/timeline.pyform shown in SKILL.mdwas smoke-tested against the pyproject.
collect/checkwere exercised against malformed inputs (non-objectrecords, ambiguous compact timestamps, quoted multi-line CSV fields, and a
gap whose anchoring event is excluded) to confirm the tool reports problems
rather than crashing or silently dropping data.