SkillAgentSearch skills...

weekly-performance-digest

Generate a weekly performance summary from closed trader-memory-core theses — win rate, expectancy, profit factor, R-multiple, MAE/MFE, and win/loss pattern analysis by source skill, exit reason, thesis type, sector, and mechanism. No API required; pure local calculation.

Install / Use

npx skills add tradermonty/claude-trading-skills --skill weekly-performance-digest

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

88/100

Category

Marketing

Supported Platforms

Universal

Our assessment of weekly-performance-digest

weekly-performance-digest scores 88/100 on our quality scale, 313th of 642 Marketing skills we index (top 49%).

Its SKILL.md is 5.6 KB long, well organised into 15 sections with 2 code examples: a solid amount of guidance for an agent.

With 2,885 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so weekly-performance-digest is actively maintained.
  • Our last check on 2026-11-01 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

weekly-performance-digest compared with similar skills

All 4 of these similar skills score higher than weekly-performance-digest; compare them before choosing.

SkillScoreStarsUpdatedFormat
weekly-performance-digest (this skill)by tradermonty882.9k53d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server
crawl4aiby unclecode10087.4k3d agoMCP Server

Frequently asked questions

How do I install weekly-performance-digest?
Run npx skills add tradermonty/claude-trading-skills --skill weekly-performance-digest. The install tabs above show the steps for each supported agent.
Which AI agents does weekly-performance-digest work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is weekly-performance-digest safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is weekly-performance-digest still maintained?
The repository was last updated about 2 months ago, so weekly-performance-digest is actively maintained.

name: weekly-performance-digest description: Generate a weekly performance summary from closed trader-memory-core theses — win rate, expectancy, profit factor, R-multiple, MAE/MFE, and win/loss pattern analysis by source skill, exit reason, thesis type, sector, and mechanism. No API required; pure local calculation.

Weekly Performance Digest

Overview

Weekly Performance Digest aggregates the trades you closed during a week into a single performance report. It reads CLOSED theses tracked by trader-memory-core (state/theses/th_*.yaml), computes headline metrics (win rate, expectancy, profit factor, R-multiple, MAE/MFE), breaks results down across several pattern dimensions (source skill, exit reason, thesis type, sector, mechanism tag, screening grade), and surfaces the week's biggest winners, losers, and lessons. Output is a JSON record plus a human-readable Markdown report. Pure calculation — no API key required.

When to Use

  • At the end of a trading week to review aggregate realized performance
  • To measure win rate and expectancy across all closed positions
  • To see which source skills, exit reasons, sectors, or mechanisms drove wins vs losses
  • To feed a month-end review (combine four weekly digests) or a postmortem
  • For a quick "what worked / what didn't" snapshot grounded in real closed trades

When Not to Use

  • For a single-trade deep review — use trade-performance-coach
  • For signal-level true/false-positive classification — use signal-postmortem
  • For buy/sell recommendations or position sizing — this skill is descriptive only

Prerequisites

  • Python 3.9+ with PyYAML (already a repo dependency)
  • A trader-memory-core state directory of thesis YAML files (state/theses/)
  • No API key required

Workflow

Step 1: Run the digest for a week

python3 skills/weekly-performance-digest/scripts/generate_weekly_digest.py \
  --state-dir state/theses \
  --from-date 2026-06-13 --to-date 2026-06-20 \
  --output-dir reports/ -v

Defaults: --state-dir state/theses, --from-date = 7 days before --to-date, --to-date = today, --output-dir reports/. With no date flags it digests the trailing 7 days.

Step 2: Read the report

The run writes reports/weekly_digest_<to-date>.json and reports/weekly_digest_<to-date>.md. Review the Markdown for the executive summary, metrics table, pattern breakdowns, and top winners/losers; consume the JSON downstream.

Step 3 (optional): Feed downstream

Combine several weekly JSON digests for a monthly review, or pass the JSON to a postmortem/coach step. The skill is descriptive — act on its findings via your normal review process.

How It Works

  • Trade selection. A trade counts in a week if its exit.actual_date falls in [from-date, to-date] and status == CLOSED.
  • Win/loss. outcome.pnl_dollars > 0 is a winner, < 0 a loser, == 0 breakeven; win_rate = winners / total_trades.
  • R-multiple. pnl_dollars / ((entry.actual_price − exit.stop_loss) × position.shares). (Stop-loss is read from exit.stop_loss, per the real thesis schema.)
  • Double-counting safeguard. A CLOSED thesis's outcome.pnl_dollars is the cumulative realized P&L across all trims plus the final leg. Headline metrics use that cumulative value over CLOSED theses only. The separate partial_trims block scans status_history[] of PARTIALLY_CLOSED theses only (still open) and is reported for information — it is never added into the headline totals/win-rate. A position trimmed in week 1 then closed in week 2 therefore shows as a partial trim in week 1 and inside week 2's CLOSED headline; that is intended, not a duplicate.

Output Format

JSON (weekly_digest_<to-date>.json)

{
  "schema_version": "1.0",
  "report_type": "weekly_performance_digest",
  "period": {"from": "2026-06-13", "to": "2026-06-20"},
  "generated_at": "2026-06-20T21:39:07Z",
  "summary": {
    "total_trades": 2, "winners": 1, "losers": 1, "breakeven": 0,
    "win_rate": 0.5, "expectancy": 25.0, "profit_factor": 2.0,
    "total_realized_pnl": 50.0, "total_realized_pnl_pct": 4.17
  },
  "metrics": {
    "avg_winner": 100.0, "avg_loser": -50.0,
    "largest_winner": 100.0, "largest_loser": -50.0,
    "avg_holding_days_winners": 9.0, "avg_holding_days_losers": 6.0,
    "r_multiple_avg": 0.25, "r_multiple_stdev": 1.06,
    "avg_mae_pct": -3.75, "avg_mfe_pct": 4.5
  },
  "pattern_analysis": {
    "by_source_skill": {"...": {"wins": 1, "losses": 0, "total": 1, "win_rate": 1.0}},
    "by_exit_reason": {}, "by_thesis_type": {}, "by_sector": {},
    "by_mechanism_tag": {}, "by_screening_grade": {}
  },
  "partial_trims": {"count": 0, "total_realized_pnl": 0.0, "trims": []},
  "lessons": {"top_wins": [], "top_losses": [], "process_improvements": []}
}

Markdown (weekly_digest_<to-date>.md)

Sections: # Weekly Performance Digest, ## Executive Summary, ## Performance Metrics, ## Pattern Analysis, ## Lessons Learned (### Top Winners / ### Top Losers / ### Process Improvements).

An empty week still produces a valid report with zeroed metrics (exit code 0).

Resources

  • scripts/generate_weekly_digest.py — digest generator (JSON + Markdown)
  • references/weekly-digest-metrics.md — metric formulas and interpretation

Key Principles

  1. Closed trades only for headline numbers — cumulative outcome.*, keyed on exit date.
  2. No double-counting — partial trims are informational and excluded from totals.
  3. Pattern attribution — every win/loss is attributed across multiple dimensions.
  4. Descriptive, not prescriptive — the digest reports; you decide.

Related Skills

View on GitHub
GitHub Stars2.9k
CategoryMarketing
Updated1mo ago
Forks655

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions