trader-memory-core

Track investment thesis lifecycles with YAML persistence and schema validation.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/pasie15/claude-trading-skills-marketplace --skill trader-memory-core-pasie15
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trader-memory-core
Source: https://github.com/pasie15/claude-trading-skills-marketplace/tree/main/plugins/trading-strategy-tools/skills/trader-memory-core
Command: npx skills add https://github.com/pasie15/claude-trading-skills-marketplace --skill trader-memory-core-pasie15

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill consolidates fragmented screening outputs, analysis, and position records into a single persistent thesis object so traders can track what they thought, what happened, and what they learned across time and conversations.

Core Features & Use Cases

  • Persistent thesis objects: Register single-ticker candidates from screeners and preserve raw provenance, classification, and evidence in YAML state files.
  • Lifecycle management & validation: Enforce forward-only transitions (IDEA → ENTRY_READY → ACTIVE → CLOSED), index for fast queries, and JSON Schema validation to ensure data integrity.
  • Review, sizing, and postmortem analytics: Attach position-sizer output, schedule and list review-due items, compute outcome statistics and optional MAE/MFE metrics for postmortems; useful for audit trails and performance analysis.
  • Real-world example: Ingest a kanchi dividend screener output, transition a candidate to ENTRY_READY after manual review, open a position with attached sizing, then close it and generate a postmortem with P&L and lessons learned.

Quick Start

Register a screened candidate by ingesting the screener JSON into the thesis store, attach position sizing when ready, and run the postmortem after closing the position.

Frequently Asked Questions about trader-memory-core

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

FAQPage Schema
How do I track investment theses from screening through to postmortem?

Track investment theses by registering screener outputs as persistent YAML state files, enforcing lifecycle transitions from IDEA to CLOSED, and generating postmortems with P&L and lessons learned. This consolidates fragmented analysis into a single auditable thesis object.

What is MAE/MFE computation and when do I need it for trade journals?

MAE/MFE computation calculates Maximum Adverse Excursion and Maximum Favorable Excursion metrics using external price data. You need it during postmortem generation to analyze position outcome statistics and evaluate trade performance beyond simple P&L.

How do I manage position sizing and lifecycle status transitions for systematic trading?

Manage position sizing by attaching position-sizer output to thesis objects, and enforce forward-only lifecycle transitions (IDEA → ENTRY_READY → ACTIVE → CLOSED) with JSON Schema validation. This ensures data integrity and prevents invalid status rollbacks.

Can I ingest screener JSON outputs directly into a trade journal for thesis tracking?

Yes, you can ingest screener JSON outputs directly into the thesis store to register single-ticker candidates. This preserves raw provenance, classification, and evidence within persistent YAML state files for subsequent review and position attachment.

Does this trade journal approach work for single-ticker systematic trading workflows?

Yes, it is designed specifically for single-ticker systematic trading workflows. It handles screener ingestion, status transitions, review scheduling, and outcome reports with lightweight index queries and atomic file writes for reliable state persistence.

What are the limitations of YAML-based thesis state persistence for trade tracking?

YAML-based thesis state persistence relies on atomic file writes and lightweight index queries without a centralized database. It is optimized for single-ticker systematic workflows and may not scale efficiently for high-frequency multi-asset portfolio management without external indexing.