Skip to content
SkillScript-led2,160 tokens in use

signal-postmortem

Records 5-day and 20-day outcomes for trading signals, labels false positives and regime mismatches, and feeds weight and backlog suggestions back.

7,430 stars on the repository MIT Licensetradermonty/claude-trading-skills · skills/signal-postmortem

Skill label

measured from its files

What installing signal-postmortem costs

48tokens idle
2,160tokens in use
4,826tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Script-led

Script-ledMixedModel-led

Most of this skill is scripts, so it behaves much the same whichever model runs it.

This describes the skill's structure, how much of it is scripts. It does not say how well it works. Scripts: scripts/fmp_client.py, scripts/postmortem_analyzer.py, scripts/postmortem_fmp_client.py, scripts/postmortem_recorder.py.

Touches

shelldetectednetworkdetectedwrites filesdetectedcredentialsdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure23/25
  • Examples15/15
  • Output10/15
  • Size15/15
  • Resources8/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Good
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 33
  • Reaches the network−10

    does this on the machine, and the frontmatter does not say so

    scripts/fmp_client.py, line 32
  • Reads credentials−15

    does this on the machine, and the frontmatter does not say so

    scripts/fmp_client.py, line 155
  • Writes files−8

    does this on the machine, and the frontmatter does not say so

    scripts/postmortem_analyzer.py, line 506

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance52
  • Community68
  • Maturity36
  • Momentum40

Signal Postmortem compares the direction a signal predicted with the return that followed after 5 and 20 days. Each signal is classified as a true positive, false positive, missed opportunity or regime mismatch, and the record keeps the market regime at signal and exit.

Aggregated results can be turned into weight adjustment suggestions for edge-signal-aggregator and into skill improvement backlog entries. Exit prices come from the FMP historical price API when a key is set, or from values you enter by hand. The output is a review of past signals and not investment advice.

What You Get

  • One JSON postmortem record per signal with realized 5d and 20d returns and an outcome category
  • Summary statistics grouped by skill, ticker or month in a Markdown report
  • Weight adjustment suggestions for edge-signal-aggregator, held back until at least 20 signals exist
  • Skill improvement backlog entries in YAML for patterns such as false positive clusters

Common Use Cases

  • Reviewing a batch of signals that have reached their holding period
  • Recording a manual exit for one closed trade from a saved signal file
  • Finding which source skill produces the most false positives in a given regime

What Makes It Unique

It separates a failed signal from a regime change by storing the regime at signal and exit. It also skips and counts any signal that lacks observed entry and exit prices, so a missing price never turns into a neutral outcome.

Under The Hood

Python scripts read signal JSON files from a directory and write postmortem JSON, Markdown and YAML files to a reports folder. With an FMP API key taken from the environment or a command-line option, the recorder calls the FMP historical price endpoint over the network using the requests library; without a key it works offline from manually supplied exit prices. The SKILL.md also tells the model to run these scripts from the shell.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers