signal-postmortem

Computes realized trading outcomes and classifies them by regime context from signal JSON files.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/dnkrow/skill --skill signal-postmortem-dnkrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signal-postmortem
Source: https://github.com/dnkrow/skill/tree/main/claude-global/signal-postmortem
Command: npx skills add https://github.com/dnkrow/skill --skill signal-postmortem-dnkrow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you measure how well generated trading signals performed after the holding period so you can identify false positives, missed opportunities, and regime mismatches instead of guessing why results happened.

Core Features & Use Cases

  • Outcome recording: Creates post-trade JSON records that include realized 5-day/20-day returns, exit details, and outcome category (true positive, false positive, missed opportunity, regime mismatch, neutral).
  • Automated classification with regime context: Classifies outcomes using predicted direction, realized return thresholds, and regime-at-signal vs regime-at-exit to separate skill errors from market moves.
  • Feedback loop for calibration and improvement: Generates weight-adjustment JSON for downstream edge-signal-aggregator calibration and produces YAML backlog entries for targeted skill improvements.

Quick Start

Use the skill to record outcomes for a batch of matured signals by running the postmortem recorder on your aggregated signals JSON file and writing the results into the reports directory.

Frequently Asked Questions about signal-postmortem

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate post-trade signal performance against market regimes?

Automated post-trade analysis classifies realized trading outcomes into categories like true positive, false positive, missed opportunity, and regime mismatch. It compares predicted signal direction against realized return thresholds across fixed holding periods to distinguish skill errors from market regime shifts.

How do I automate post-trade analysis for a batch of matured signals?

You run the postmortem recorder on an aggregated signals JSON file containing fields like signal_id, ticker, signal_date, and predicted_direction. The script processes batch outcomes and writes classified post-trade JSON records with realized returns and exit details into your reports directory.

What JSON input fields are required for signal postmortem evaluation?

Signal postmortem evaluation requires input JSON fields including signal_id, ticker, signal_date, predicted_direction, source_skill, and entry_price. These fields allow the recorder to compute realized 5-day and 20-day returns and classify outcomes against regime context for each matured signal.

Does the post-trade signal evaluator require Python 3.9 and external price data?

Post-trade signal evaluation requires Python 3.9 or higher and uses the requests library for optional FMP price fetching. You can supply entry prices directly in the input signal JSON or enable automated price retrieval for computing realized holding period returns.

Can post-trade signal classification generate feedback for weight calibration?

Post-trade signal classification generates weight-adjustment JSON for downstream edge-signal-aggregator calibration and produces YAML backlog entries for targeted skill improvements. This feedback loop turns realized outcome categories into actionable calibration data for refining future signal generation.