cc-skill:swarmtrade-postmortem

Claude Code skill · anthropic · active

last 30 days

0 calls

0 of 30 days active

explain like I am new to this

what it does

Creates a transparent, technically detailed post-mortem document about a SwarmTrade incident, failure, or release. It follows a strict structure that builds credibility by being honest about what broke, why, and what you're doing about it.

who it is for

Founders and builders in fintech or trading who want to build trust with technical audiences by showing they can admit and learn from mistakes.

when it fires

When you mention writing a post-mortem, incident writeup, release notes, retrospective, or ask what went wrong with a SwarmTrade system or release.

say something like

"Write a post-mortem for the cache layer that crashed last Tuesday"
"Create release notes for the new broker integration that had backtest drift"
"What went wrong with our cost spike last week? Help me write it up"

what you might get back

A structured document titled 'Cache TTL Off-by-One Error' dated 2026-04-22, marked as Medium severity and resolved. The TL;DR explains the issue in 2 sentences. The 'What broke and why' section identifies the specific off-by-one bug in milliseconds. 'What we did about it' lists the exact code fix and deployment steps. 'What we learned' includes 4 concrete bullets about testing gaps. 'What's changing' commits to new unit tests for boundary conditions.

how to know it worked

The output includes all mandatory sections in order, avoids marketing language and empty phrases, includes specific technical details with timestamps or numbers, and shows real judgment in explaining both what changed and what you decided not to change.

is this skill working for me

never used

cloud runs

0 deployments

local fires

Claude Code (optional)

posts published

from drafts

attributed

$0.00

signups + revenue

Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/swarmtrade-postmortem/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when writing public post-mortems, release notes, incident writeups, or technical retrospectives for SwarmTrade. Triggers on "post-mortem", "writeup", "SwarmTrade release", "release notes", "incident", "retro", or "what went wrong". Pro

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/swarmtrade-postmortem/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity

never used

2026-04-03today

cost model

unitincluded

capabilities

{
  "source": "global",
  "description": "Use this skill when writing public post-mortems, release notes, incident writeups, or technical retrospectives for SwarmTrade. Triggers on \"post-mortem\", \"writeup\", \"SwarmTrade release\", \"release notes\", \"incident\", \"retro\", or \"what went wrong\". Produces fintwit-credible technical documents that build trust by being transparent about failures."
}

how it gets called

{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/swarmtrade-postmortem/SKILL.md"
}

This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.