Agent skill · AI & Agents

signal-postmortem

Record and analyze post-trade outcomes for signals generated by edge pipeline and other skills. Track false positives, missed opportunities, and regime mismatches. Feed results back to edge-signal-aggregator weights and skill improvement backlog.

BaggaT236github.com/BaggaT236GitHub ↗
claude-codeships scriptsMIT
Install
npx skills add BaggaT236/AI-Trading-Skills --skill signal-postmortem --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 8
SKILL.md size: 7 KB
Bundled scripts: yes
Path: skills/signal-postmortem/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 118
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Signal Postmortem ## Overview Signal Postmortem records and analyzes the outcomes of trading signals generated by the edge pipeline, screeners, and other skills. It compares predicted edge direction against 5-day and 20-day realized returns, categorizes outcomes (true positive, false positive, missed opportunity, regime mismatch), and generates feedback for edge-signal-aggregator weight adjustments and skill improvement backlog entries. ## When to Use - After a trade has been closed and you want to record the outcome - When reviewing a batch of signals that have reached their holding period (5 or 20 days) - To identify systematic false positive patterns from specific skills - To generate feedback for edge-signal-aggregator weight calibration - When building a skill improvement backlog from decision quality metrics - For periodic (weekly/monthly) signal quality audits ## Prerequisites - Python 3.9+ - FMP API key (optional, for fetching realized returns if not provided manually) - Standard library + `requests` for API calls - Input: signal records in JSON format (from edge-signal-aggregator or screener outputs) ### API Key Setup (Optional) If you want to automatically fetch price d

What's inside
Steps it walks through
  1. Overview
  2. When to Use
  3. Prerequisites
  4. API Key Setup (Optional)
  5. Workflow
  6. Step 1: Prepare Signal Records
  7. Step 2: Record Outcomes
  8. Step 3: Classify Outcomes
  9. Step 4: Generate Feedback Files
  10. Step 5: Review Summary Statistics
  11. Output Format
  12. Postmortem Record (JSON)
  13. Weight Feedback (JSON)
  14. Skill Improvement Backlog Entry (YAML)
Ships with 7 files
  • references/feedback-integration.md
  • references/outcome-classification.md
  • scripts/postmortem_analyzer.py
  • scripts/postmortem_recorder.py
  • scripts/tests/conftest.py
  • scripts/tests/test_postmortem_analyzer.py
  • scripts/tests/test_postmortem_recorder.py
Commands it runs
export FMP_API_KEY=your_api_key_here
python3 skills/signal-postmortem/scripts/postmortem_recorder.py \
Generate weight adjustment suggestions for edge-signal-aggregator
python3 skills/signal-postmortem/scripts/postmortem_analyzer.py \
Generate skill improvement backlog entries
More from AI-Trading-Skills
All skills →
About this skill
What does the signal-postmortem skill do?

Record and analyze post-trade outcomes for signals generated by edge pipeline and other skills. Track false positives, missed opportunities, and regime mismatches. Feed results back to edge-signal-aggregator weights and skill improvement backlog.

How do I install it?

Run `npx skills add BaggaT236/AI-Trading-Skills --skill signal-postmortem --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From BaggaT236/AI-Trading-Skills, a repository with 118 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going