Skip to content
Skills Library
Marketing & content · Analysis

post-mortem

/post-mortem

Write a post-mortem for one post (breakout, flop or new best) with wins and losses at the same depth. Used by the learn.post-mortem job and when the user asks why a post did well or badly.

Repository
attentionos ↗
Licence
MIT
Last repository change
22.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Write a post-mortem for one post (breakout, flop or new best) with wins and losses at the same depth. Used by the learn.post-mortem job and when the user asks why a post did well or badly.

Original author description

Write a post-mortem for one post (breakout, flop or new best) with wins and losses at the same depth. Used by the learn.post-mortem job and when the user asks why a post did well or badly.

How it works

  1. Gather
  2. Write
  3. Rules
Original SKILL.md headings · 43 lines, 451 words
SKILL.md preview
---
name: post-mortem
description: Write a post-mortem for one post (breakout, flop or new best) with wins and losses at the same depth. Used by the learn.post-mortem job and when the user asks why a post did well or badly.
---

# Post-mortem

Every breakout (2x or more the account's normal), every flop (under 0.6x, or a skip rate of 70% or more) and every new best gets a post-mortem. Wins get the same scrutiny as losses: a win you can't explain can't be repeated.

## Gather

1. `learn_get_post_context`: numbers over time (1h → 30d), `x` against the account's normal, the rate family (send rate, follows per 1k views, engagement), velocity (first-day views vs usual), 3-second hold and retention curve when known, the code-computed "why" lines, the plan behind the post (lane, angle, hook pattern, format, CTA), and the script.
2. `learn_get_feature_stats`: how the post's lane, hook pattern and format usually perform. A breakout in a lane that always does well is less surprising than one in a weak lane.
3. Read `brand/lessons.md` so you don't restate a rule that already exists.

## Write

Save with `learn_save_post_mortem`. `bodyMd` has exactly these sections:

```
## What happened
The numbers in one paragraph: x, views, send rate, follows per 1k, skip rate or 3-second hold if known, and how fast it moved (velocity, 1h vs 24h).
Then the first 3 seconds: the opening frame, any on-screen text and the first spoken line (from the script), with timestamps where you have them.

## Why we think it happened
2–4 specific reasons tied to choices in the plan or script (the hook's first line, the format, the topic, the CTA, the posting slot).
Mark each as "likely" or "possible". One post is a data point, not proof.

## What to repeat
Concrete choices to reuse, phrased so the Strategist or Copywriter can act on them.

## What to change
Concrete choices to drop or test differently. For a win, what would make the next one better.
For a miss, also say where in the process it slipped through (plan, script, edit, schedule) and the next action
(for example: repost as a trial reel in the winning format, or rewrite the hook against the last winner's opening).
```

`lessons`: 1–3 short rules in plain language ("Lead proof posts with the number in the first line"). They are proposed for `brand/lessons.md`; the user approves them.

## Rules

- Only numbers returned by the tools. If something wasn't measured, say "not measured".
- If the feature stats say GAP for a choice, say the evidence is thin instead of drawing a conclusion.
- Never blame the audience or the algorithm. Explain what we can control.
- Judge the opening against the account's recent winners, not gut feel: compare its first 3 seconds with the best post's.
- Rank causes from most to least likely. Fewer than 5 posts behind a pattern is a hunch, not a finding: say so.

Versions

RepositoryScoreLicence
This page · evanbaker315/attentionos100MIT
digital-stoic-org/agent-skills100MIT
alirezarezvani/claude-skills100MIT
borghei/Claude-Skills100MIT
rileyhilliard/claude-essentials100MIT
hanamizuki/solopreneur100MIT
bestagentkits/agency-skills100MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version b5402406cf87 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100im-audit
    Post-mortem on what the user has already posted - which reels actually worked, why, and what to stop making. Use when the user pastes their Instagram insights or past posts and asks "what's working", "why did this flop", "read my analytics", "audit my content", or wants to know what to do more of.
  • 100ig-audit
    Post-mortem on what the user has already posted - which reels actually worked, why, and what to stop making. Use when the user pastes their Instagram insights or past posts and asks "what's working", "why did this flop", "read my analytics", "audit my content", or wants to know what to do more of.
  • 100ig-audit
    Post-mortem on what the user has already posted - which reels actually worked, why, and what to stop making. Use when the user pastes their Instagram insights or past posts and asks "what's working", "why did this flop", "read my analytics", "audit my content", or wants to know what to do more of.
  • 100li-audit
    Post-mortem on what the user has already published - which posts actually worked, why, and what to stop doing. Use when the user pastes their LinkedIn analytics or past posts and asks "what's working", "why did this flop", "read my analytics", "audit my content", or wants to…
  • 100ig-audit
    Post-mortem on what the user has already posted - which reels actually worked, why, and what to stop making. Use when the user pastes their Instagram insights or past posts, or has PostZen connected, and asks "what's working", "why did this flop", "read my analytics", "audit my…
  • 100why-did-this-post-flop
    Diagnose why one Twitter/X or LinkedIn post underperformed: not seen, seen and skipped, or read and ignored. Use when someone asks why a post did badly or got no engagement.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.