Polyclaw
chainstacklabs/polyclaw
Trade on Polymarket via split + CLOB execution. An agent skill from chainstacklabs/polyclaw.
This skill should be used when analyzing weekly price charts for stocks, stock indices, cryptocurrencies, or forex pairs.
$ npx skills add tradermonty/claude-trading-skills --skill technical-analyst -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tradermonty/claude-trading-skills technical-analyst --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tradermonty/claude-trading-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/technical-analyst .claude/skills/technical-analyst && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "technical-analyst" agent skill from https://github.com/tradermonty/claude-trading-skills/tree/main/skills/technical-analyst into .claude/skills/technical-analyst/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-analyst", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tradermonty/claude-trading-skills/tree/main/skills/technical-analystType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tradermonty/claude-trading-skills --skill technical-analyst -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tradermonty/claude-trading-skills technical-analyst --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tradermonty/claude-trading-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/technical-analyst .agents/skills/technical-analyst && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "technical-analyst" agent skill from https://github.com/tradermonty/claude-trading-skills/tree/main/skills/technical-analyst into .agents/skills/technical-analyst/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-analyst", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tradermonty/claude-trading-skills --skill technical-analyst -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tradermonty/claude-trading-skills technical-analyst --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tradermonty/claude-trading-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/technical-analyst .cursor/skills/technical-analyst && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "technical-analyst" agent skill from https://github.com/tradermonty/claude-trading-skills/tree/main/skills/technical-analyst into .cursor/skills/technical-analyst/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-analyst", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tradermonty/claude-trading-skills.git --path skills/technical-analyst--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tradermonty/claude-trading-skills --skill technical-analyst -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tradermonty/claude-trading-skills technical-analyst --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tradermonty/claude-trading-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/technical-analyst .gemini/skills/technical-analyst && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "technical-analyst" agent skill from https://github.com/tradermonty/claude-trading-skills/tree/main/skills/technical-analyst into .gemini/skills/technical-analyst/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-analyst", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tradermonty/claude-trading-skills technical-analystInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tradermonty/claude-trading-skills --skill technical-analyst -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tradermonty/claude-trading-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/technical-analyst .github/skills/technical-analyst && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "technical-analyst" agent skill from https://github.com/tradermonty/claude-trading-skills/tree/main/skills/technical-analyst into .github/skills/technical-analyst/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-analyst", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tradermonty/claude-trading-skills --skill technical-analyst -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tradermonty/claude-trading-skills technical-analyst --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tradermonty/claude-trading-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/technical-analyst .opencode/skills/technical-analyst && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "technical-analyst" agent skill from https://github.com/tradermonty/claude-trading-skills/tree/main/skills/technical-analyst into .opencode/skills/technical-analyst/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-analyst", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
technical-analystThis skill should be used when analyzing weekly price charts for stocks, stock indices, cryptocurrencies, or forex pairs.
Technical Analyst is an agent skill from tradermonty/claude-trading-skills. This skill should be used when analyzing weekly price charts for stocks, stock indices, cryptocurrencies, or forex pairs. Use this skill when the user provides chart images and requests technical analysis, trend identification, support/resistance levels, scenario planning, or probability assessments based purely on chart data without consideration of news or fundamental factors.
Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts, reference files and assets (for example `assets/analysis_template.md`, `references/contrarian-confirmation-checklist.md` and `references/technical_analysis_framework.md`).
It sits in Business, Finance & HR, covering Crypto and DeFi analysis. The repository describes itself as: Claude Code skills for equity investors and traders — market analysis, technical charting, economic calendars, screeners, and trading strategy development. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit eab8d5c. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 5 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Technical Analyst loads about 4.6k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 100 tokens; SKILL.md has 1,829 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from tradermonty/claude-trading-skills at commit eab8d5c, republished under its MIT licence (© tradermonty). 1,829 words, ~4,591 tokens.
.claude/skills/technical-analyst/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.This skill enables comprehensive technical analysis of weekly price charts. Analyze chart images to identify trends, support and resistance levels, moving average relationships, volume patterns, and develop probabilistic scenarios for future price movement. All analysis is conducted objectively using only chart data, without influence from news, fundamentals, or market sentiment.
This skill generates markdown analysis reports saved to the reports/ directory:
[SYMBOL]_technical_analysis_[YYYY-MM-DD].mdWhen the user provides one or more weekly chart images for analysis:
Before beginning analysis, read the comprehensive technical analysis methodology:
Read: references/technical_analysis_framework.mdThis reference contains detailed guidance on:
For each chart image, conduct a systematic analysis following this sequence:
For each analyzed chart, create 2-4 distinct scenarios for future price movement:
Each scenario must include:
Adjust probabilities based on strength of supporting technical factors. Ensure probabilities are realistic and sum to 100%.
For each chart analyzed, create a comprehensive markdown report using the template structure:
Read and use as template: assets/analysis_template.mdThe report must include all sections:
File Naming Convention: Save each analysis as [SYMBOL]_technical_analysis_[YYYY-MM-DD].md
Example: SPY_technical_analysis_2025-11-02.md
If multiple charts are provided:
Do not batch analyses. Complete and save each report before moving to the next chart.
Example 1: Single Chart Analysis
User: "Please analyze this weekly chart of the S&P 500"
[Provides chart image]
Analyst:
1. Confirms receipt of chart image
2. Reads technical_analysis_framework.md for methodology
3. Conducts systematic analysis (trend, S/R, MA, volume, patterns)
4. Develops 3 scenarios with probabilities (e.g., 55% bullish continuation, 30% consolidation, 15% reversal)
5. Generates comprehensive analysis report using template
6. Saves as SPY_technical_analysis_2025-11-02.mdExample 2: Multiple Chart Analysis
User: "Analyze these three charts: Bitcoin, Ethereum, and Nasdaq"
[Provides 3 chart images]
Analyst:
1. Confirms receipt of 3 charts
2. Reads technical_analysis_framework.md
3. Analyzes Bitcoin chart completely → Generates report → Saves as BTC_technical_analysis_2025-11-02.md
4. Analyzes Ethereum chart completely → Generates report → Saves as ETH_technical_analysis_2025-11-02.md
5. Analyzes Nasdaq chart completely → Generates report → Saves as NDX_technical_analysis_2025-11-02.md
6. Notifies user that all three analyses are completeExample 3: Focused Analysis Request
User: "I'm particularly interested in whether this stock will break above resistance. Analyze the chart."
[Provides chart image]
Analyst:
1. Conducts full systematic analysis
2. Pays special attention to resistance levels and breakout probability
3. Develops scenarios with emphasis on breakout vs. rejection possibilities
4. Assigns probabilities based on volume, trend strength, and proximity to resistance
5. Generates complete report with focused scenario analysisThis is an ADDITIVE mode, separate from the pure chart-analysis workflow
above. It activates only on an explicit contrarian-confirmation request —
typically after cot-contrarian-detector (step 1) has flagged a market
crowded and, optionally, news-reaction-failure-analyzer (step 2) has
shown it failed to react to favorable news. A plain "analyze this chart"
request still runs the original workflow (Steps 1-6 above) unchanged.
Confirm whether the WEEKLY chart is showing price-action evidence that a
crowded market is reversing: a weekly key reversal, an intraweek failed
extreme, or a confirmed-then-rejected failed breakout — vetoed by a
continuation check (a new closing extreme in the crowd's direction more
recent than any signal found). See
references/contrarian-confirmation-checklist.md for the full,
word-for-word methodology shared by both chart mode and script mode.
CROWDED_LONG or CROWDED_SHORT — from the user,
or from a prior cot-contrarian-detector report.scripts/check_weekly_price_action.py
when no chart is supplied, or when an auditable, deterministic result is
wanted instead of (or alongside) a visual read.week_of is the FAILURE week, never the breakout
week.stop_reference — the nearest
swing high when fading a crowded LONG, the nearest swing low when
fading a crowded SHORT.Every comparison is a STRICT inequality; window truncation is
per-evaluated-week, not per-run. Full definitions, the direction-mirror
table, worked examples, and the confidence-HIGH rule are in
references/contrarian-confirmation-checklist.md — read it before
producing a chart-mode verdict, so chart and script judge identically.
symbol: BT
direction: CROWDED_LONG
mode: data # "chart" for a Claude chart-image read
verdict: CONFIRMED | NOT_CONFIRMED | INSUFFICIENT_DATA
confidence: HIGH | MEDIUM | LOW # LOW reserved, never emitted in v1
verdict_reason: key_reversal | failed_extreme | failed_breakout |
continuation_intact | no_reversal_evidence |
insufficient_weekly_bars | no_price_source | ...
checks:
weekly_key_reversal:
{ triggered, week_of, swing_window_weeks_used,
extreme_window_weeks_used, is_full_window_extreme, detail }
failed_extreme: { triggered, attempted_level, week_of, window_weeks_used, detail }
failed_breakout: { triggered, breakout_level, week_of, window_weeks_used, detail }
continuation: { new_closing_extreme_with_crowd, week_of, window_weeks_used }
swing_levels:
nearest_swing_high: { price, week_of, fallback }
nearest_swing_low: { price, week_of, fallback }
stop_reference: 0.0
weekly_bars_used: 52
last_completed_week: 2026-07-06
handoff: # consumed by contrarian-setup-gate (#241)
price_action: { verdict, confidence, stop_reference, report_path }
run_context:
{
price_symbol,
price_source,
proxy_used,
as_of,
lookbacks,
recency,
min_weeks,
detector_json,
detector_age_days,
schema_version,
}Invariant: checks (and swing_levels) is null whenever
verdict: INSUFFICIENT_DATA — regardless of the specific reason
(no_price_source, insufficient_weekly_bars, a detector-json refusal,
...). A downstream consumer can check verdict alone before deciding
whether checks.* is safe to read, without branching on
verdict_reason.
File naming: ta_confirmation_<SYMBOL>_<as-of>.json and
ta_confirmation_<SYMBOL>_<as-of>.md, saved to reports/.
Chart images remain the PRIMARY input, consistent with this skill's identity. Run the script instead of (or alongside) a chart read when no chart is supplied, or when an auditable, deterministic result is preferred:
python3 skills/technical-analyst/scripts/check_weekly_price_action.py \
--symbol BT --direction CROWDED_LONG --as-of 2026-07-15 \
--output-dir reports/Or resolve direction from a cot-contrarian-detector report directly:
python3 skills/technical-analyst/scripts/check_weekly_price_action.py \
--symbol BT --detector-json reports/cot_crowding_2026-07-12.json \
--as-of 2026-07-15 --output-dir reports/The script fetches weekly-resampled OHLC via a documented futures-to-ETF
fallback chain (see the module docstring in
scripts/check_weekly_price_action.py), truncates daily bars to --as-of
BEFORE resampling (no lookahead), and fails closed to
INSUFFICIENT_DATA — never a crash — on an unreadable (missing file),
syntactically invalid, stale, or structurally malformed --detector-json,
too little price history (--min-weeks, default 30), or no usable price
source.
If both chart mode and script mode produce a result for the same
symbol/direction and their verdicts DISAGREE, the final verdict is
NOT_CONFIRMED (verdict_reason: mode_disagreement), with both
sub-results attached for review — never silently prefer one mode. If one
mode is INSUFFICIENT_DATA and the other is a clean verdict, the clean
verdict stands.
position-sizer / futures-position-sizer, not this mode.INSUFFICIENT_DATA never advances the pipeline — fail-closed on
every degraded input, always exits 0 with a report written.references/contrarian-confirmation-checklist.md.This skill includes the following bundled resources:
Comprehensive methodology for technical analysis including:
Usage: Read this file before conducting analysis to ensure systematic, objective approach.
Structured template for technical analysis reports with all required sections.
Usage: Use this template structure for every analysis report. Copy the format and populate with specific findings for each chart.
Full methodology for Contrarian Confirmation Mode (Shapiro Step 3): direction convention, window/truncation rules, the 3 signal checks + continuation veto, swing-level (fractal pivot) rules, verdict synthesis, confidence rules, the output contract, a chart-mode walkthrough, and the conservative disagreement rule.
Usage: Read this file before producing a Contrarian Confirmation Mode
verdict — chart mode and scripts/check_weekly_price_action.py must judge
identically, so the same strict definitions apply to both.
Data-driven fallback CLI for Contrarian Confirmation Mode. Fetches
weekly-resampled OHLC (documented futures-to-ETF fallback chain,
--as-of information cutoff applied before resampling), runs the 3
signal checks + continuation veto + swing-level detection, and writes
ta_confirmation_<SYMBOL>_<as-of>.json/.md to reports/.
Usage: Run when no chart image is supplied, or when an auditable, deterministic result is wanted. See the Contrarian Confirmation Mode section above for invocation examples.
© tradermonty, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 9 other files (scripts, references, assets) in skills/technical-analyst of tradermonty/claude-trading-skills.
Open the folder on GitHubat commit eab8d5c
We found 8 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 5 other GitHub owners. This page covers the copy in tradermonty/claude-trading-skills, which our catalogue first saw on October 7, 2026.
Technical Analyst next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Technical Analyst this skilltradermonty/claude-trading-skills | 3k | 5 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Polyclawchainstacklabs/polyclaw | 360 | 1 repos | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Longbridge Researchhelsome/folio | 269 | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Stock Analysis24mlight/StockClaw | 101 | 2 repos | ~2k | Automated safety check: Notes | MIT | |
| Swapper Depositswapperfinance/swapper-toolkit | 852 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Okx Cex Earnokx/agent-skills | 186 | 2 repos | ~3.3k | Automated safety check: Pass | MIT |
chainstacklabs/polyclaw
Trade on Polymarket via split + CLOB execution. An agent skill from chainstacklabs/polyclaw.
helsome/folio
Institution ratings, consensus price targets, EPS/revenue forecasts, finance calendar, shareholder data, fund holders, insider trades (SEC Form 4), short interest, industry rankings, peer group…
24mlight/StockClaw
Analyze stocks and cryptocurrencies using Yahoo Finance data.
swapperfinance/swapper-toolkit
Deposit and bridge funds into a wallet or protocol using Swapper Finance.
okx/agent-skills
Manages OKX Simple Earn (flexible savings/lending), Flash Earn, On-chain Earn (staking/DeFi), Dual Investment (DCD/双币赢), and AutoEarn (自动赚币) via the okx CLI.
dex-original/okx-agent-trade-kit
A skill your agent uses when the user asks for: price of any asset, ticker, order book, candles, OHLCV, funding rate, open interest, OI change scanner, market screener (top movers, high-volume…
tradermonty/claude-trading-skills
Track investment theses across their lifecycle — from screening idea to closed position with postmortem.
tradermonty/claude-trading-skills
Detect and analyze trending market themes across sectors. An agent skill from tradermonty/claude-trading-skills.
tradermonty/claude-trading-skills
Critically review strategy drafts from edge-strategy-designer for edge plausibility, overfitting risk, sample size adequacy, and execution realism.
tradermonty/claude-trading-skills
This skill should be used when analyzing sector rotation patterns and market cycle positioning.
tradermonty/claude-trading-skills
Druckenmiller Strategy Synthesizer - Integrates 8 upstream skill outputs (Market Breadth, Uptrend Analysis, Market Top, Macro Regime, FTD Detector, VCP Screener, Theme Detector, CANSLIM Screener)…
tradermonty/claude-trading-skills
Comprehensive US stock analysis including fundamental analysis (financial metrics, business quality, valuation), technical analysis (indicators, chart patterns, support/resistance), stock…
Categories
This skill should be used when analyzing weekly price charts for stocks, stock indices, cryptocurrencies, or forex pairs. Technical Analyst is an agent skill from tradermonty/claude-trading-skills. This skill should be used when analyzing weekly price charts for stocks, stock indices, cryptocurrencies, or forex pairs.
Technical Analyst fits situations like: the user provides chart images and requests technical analysis; trend identification; support/resistance levels; scenario planning.
Run `npx skills add tradermonty/claude-trading-skills --skill technical-analyst -a claude-code`. Or copy the skill folder (skills/technical-analyst in tradermonty/claude-trading-skills) into .claude/skills/technical-analyst in your project. Claude Code loads it when a task matches its description.
Run `npx skills add tradermonty/claude-trading-skills --skill technical-analyst -a codex`. Or copy the skill folder (skills/technical-analyst in tradermonty/claude-trading-skills) into .agents/skills/technical-analyst in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tradermonty/claude-trading-skills --skill technical-analyst -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/technical-analyst, .gemini/skills/technical-analyst, .github/skills/technical-analyst and .opencode/skills/technical-analyst in your project.
Going by SKILL.md and its folder, Technical Analyst needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Technical Analyst is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.6k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.5k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Technical Analyst: Polyclaw (chainstacklabs/polyclaw, 360 stars), Longbridge Research (helsome/folio, 269 stars), Stock Analysis (24mlight/StockClaw, 101 stars) and Swapper Deposit (swapperfinance/swapper-toolkit, 852 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
tradermonty (a GitHub user) maintains it in tradermonty/claude-trading-skills, which has 2,960 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on October 5, 2026.
Source: tradermonty/claude-trading-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.