Borrowing it
Nothing to install: this file belongs to silver2dream/ai-workflow-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/silver2dream/ai-workflow-kit/main/.ai/skills/post-mortem/SKILL.mdgit clone --depth 1 https://github.com/silver2dream/ai-workflow-kitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/silver2dream/ai-workflow-kit/post-mortem)<a href="https://agentmods.dev/skills/silver2dream/ai-workflow-kit/post-mortem"><img src="https://agentmods.dev/badge/skills/silver2dream/ai-workflow-kit/post-mortem/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/silver2dream/ai-workflow-kit/post-mortem"><img src="https://agentmods.dev/badge/skills/silver2dream/ai-workflow-kit/post-mortem.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00526 |
| Opus 5.5 | $0.00000 | $0.00210 |
| Sonnet 5.5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
post-mortem scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Mortem Skill
Structured failure analysis workflow for diagnosing and learning from workflow failures, build breaks, and operational incidents.
Overview
This skill provides a systematic approach to failure analysis when something goes wrong in the AWK workflow pipeline. It walks through evidence collection, root cause identification, impact assessment, and actionable remediation -- producing a structured report that can be referenced for future prevention.
When to Use
Use this skill when:
- A Worker dispatch fails or times out
- A PR is rejected due to unexpected errors
- CI/CD pipeline breaks
awkit kickoffencounters unrecoverable errors- Any workflow step produces unexpected results
- User invokes
/post-mortem
Workflow
Phase 1: Analyze Failure
Read phases/analyze-failure.md
Walk through the structured failure analysis:
- Collect failure context (trace files, logs, error messages)
- Identify root cause (categorize: config, code, environment, external)
- Determine blast radius (what was affected)
- Generate remediation steps
- Create prevention measures
- Output structured report
Critical Rules
- DO NOT modify any files during analysis -- this is a read-only diagnostic skill
- Collect evidence first -- never jump to conclusions without supporting data
- Categorize accurately -- misclassification leads to wrong remediation
- Be specific in remediation -- vague advice is not actionable
- Always produce the structured report -- even if root cause is uncertain
Integration with AWK Workflow
This skill is used after a failure has occurred. It does not interfere with active workflows.
- Safe to run while
awkit kickoffis active (read-only) - Results can inform new issues created via
/create-issues - Prevention measures may lead to config or rule updates
Self-Check
On each phase entry, output:
[POST-MORTEM] <timestamp> | <phase> | loaded: <filename>
Quick Reference
| Phase | Action | File |
|---|---|---|
| 1. Analyze Failure | Full structured failure analysis | phases/analyze-failure.md |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 67 lines · 0 tokens per session scan A b1ae3c8e8591
post-mortem is a skill published in the GitHub repository silver2dream/ai-workflow-kit (2 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 526 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ci-triage
Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.
otter-rules-engine
This skill should be used when the user asks to "add a rule", "create a ruleset", "add a fact", "create a custom operator", "add a rules-engine action", "make behavior conditional at runtime", or when authoring or debugging anything in an Otter @o3r/rules-engine workspace. Guides the fact/operator/action/ruleset…
playwright-e2e-testing
This skill should be used when the user asks to "create an E2E test", "write a Playwright scenario", "add a Playwright test", "generate e2e tests", "create actions and checks", "write playwright checks", "add scenario for feature", or when modifying, reviewing, or debugging Playwright E2E test files in the workspace.
universal-live-check
Universal live-check framework for coding agents. Executes incremental, deterministic validation across all software domains (CLI, backend, frontend, mobile, embedded, libs). Change-type-aware (feat, fix, hotfix, refactor, migrate, docs). Triggers whenever an agent needs to validate code quality, run linting, perform…
bug-fix-protocol
8-step disciplined bug-fix protocol that treats every production bug as two failures — the code defect itself and the testing system that allowed it through. Use when fixing a production bug, investigating a regression, writing a post-mortem, or auditing a missed defect. Triggers on "fix this bug", "production bug"…
kirby-debugging-and-tracing
Diagnoses Kirby rendering/runtime issues using MCP runtime rendering, dump traces, and template/snippet/controller indexes. Use when outputs are wrong, errors occur, or tracing execution paths is required.