v3.0.0501 skillsagentskills.ioApache-2.0
Every skill declares
where it stops.
501 playbooks for AI agents that write trading systems, each with a working reference implementation and a test suite. Every one names the situations it covers, the ones it does not, and the skill that takes over. That graph of handoffs is drawn behind you, from the library itself.
Skills
501
Domains
16
Handoffs
3,317
Reference implementations
501
- australian-securities-exchange-asx-apibinary-protocol-parsing-for-low-latency-feeds
- black-swan-playbook-for-halted-marketsexecution-algo-behavior-under-halted-instrument
- adversarial-robustness-of-trading-signalsbacktest-outlier-and-bad-tick-filtering
- algo-trading-disclosure-to-exchange-membershipkill-switch-and-drawdown-circuit-breakers
- corporate-action-event-calendar-integrationcorporate-action-adjusted-backtesting
- alpaca-paper-live-key-separationkill-switch-and-drawdown-circuit-breakers
- adaptive-execution-under-volatility-spikesbroker-api-idempotent-cancel-requests
- adaptive-batch-size-tuning-under-loadkill-switch-and-drawdown-circuit-breakers
- backtest-audit-trail-for-regulatory-reviewcentralized-secrets-management-vault-integration
- audit-logging-for-configuration-changesdata-lineage-tracking-for-audit-and-debugging
- cross-chain-address-reuse-privacy-riskcross-chain-bridge-risk-for-multi-chain-strategies
- american-vs-european-style-option-exercise-handlingcorporate-action-event-calendar-integration
- capital-efficiency-across-cross-margined-strategiesbroker-account-margin-call-handling
- adverse-selection-measurement-for-passive-ordersclock-skew-correction-for-tick-timestamps
- alternative-data-vendor-due-diligence-checklistalgorithmic-trading-firm-licensing-thresholds
- automated-tax-lot-reporting-pipelineexecution-realistic-simulation
- b3-brazil-exchange-api-integrationbinary-protocol-parsing-for-low-latency-feeds
- capital-preservation-mode-for-degraded-conditionsbroker-side-order-throttle-detection
- alternative-data-feature-integrationalternative-data-vendor-due-diligence-checklist
- annual-compliance-attestation-workflowkill-switch-and-drawdown-circuit-breakers
- cross-region-data-replication-lag-monitoringcost-monitoring-for-cloud-trading-infrastructure
- api-key-least-privilege-audit-toolcrypto-wallet-key-custody-security
- algo-parameter-defaults-by-instrument-liquidity-tierliquidity-adjusted-position-sizing
- backpressure-drop-degrade-policycapacity-planning-for-symbol-universe-growth
- backtest-database-schema-for-point-in-time-queriespoint-in-time-database-for-ml-training-data
- automated-rollback-triggers-on-anomaly-detectiondata-quality-monitoring-dashboard
- crypto-wallet-key-custody-securityapi-key-least-privilege-audit-tool
- binary-options-regulatory-and-risk-considerationsasic-market-integrity-rules-automated-trading
- capital-reallocation-based-on-live-performancekill-switch-and-drawdown-circuit-breakers
- clock-drift-monitoring-alerting-thresholdsclock-skew-correction-for-tick-timestamps
- app-download-and-usage-data-for-consumer-companiesalternative-data-feature-integration
- capital-gains-vs-business-income-classificationbest-execution-record-keeping-global
Why a library and not a prompt
Code that reads
as correct.
None of these are syntax errors, and none of them look wrong in review. They are the assumptions a trading system punishes. Each one is owned by a skill.
01
Broker Integration
The request timed out, so the order failed. Retry it.
A timeout means unknown, never failed. Reconcile against the broker's order book before any retry, or the position doubles.
order-placement-idempotency02
Backtesting Methodology
Use the bar's close to decide whether to enter on that bar.
The close is not knowable until the bar completes. A backtest that reads it is predicting the present.
lookahead-bias-elimination03
Risk Management
Check the drawdown limit at the top of the strategy function.
A limit inside the function it constrains can be skipped by the same bug it exists to catch. It needs veto power from outside.
kill-switch-and-drawdown-circuit-breakers04
Real-Time Architecture
On reconnect, resubscribe to every symbol.
The server may still hold the old subscriptions. Reconcile what is actually subscribed, or every tick arrives twice.
websocket-subscription-reconciliation-after-reconnect
Sixteen domains
By the part of
the system.
Domains describe where a skill sits in a trading system, not what asset class it trades. A skill about reconnect handling belongs to real-time architecture whether the feed carries equities or perpetual futures.
All sixteen, with the graph- 01Global Market IntegrationExchanges and venues worldwide44 / 501
- 02Risk ManagementKill switches and exposure limits39 / 501
- 03Financial MLLeakage-free features and models38 / 501
- 04Regulatory ComplianceSEC, FINRA, MiFID II, FCA, SEBI38 / 501
- 05Data ManagementCalendars, timezones, symbology37 / 501
- 06Broker IntegrationAuth, tokens, idempotent orders36 / 501
- 07Execution AlgorithmsTWAP, VWAP, POV, routing32 / 501
- 08Real-Time ArchitectureTick pipelines and backpressure31 / 501
- 09Backtesting MethodologyLookahead, walk-forward, realism31 / 501
- 10Deployment & OpsSupervision, promotion, chaos30 / 501
- 11Crypto Custody & SecurityKeys, wallets, withdrawals29 / 501
- 12Multi-Asset DerivativesOptions, futures, swaps28 / 501
- 13Portfolio & Multi-StrategyAllocation across strategies28 / 501
- 14Microstructure & LatencyColocation, clocks, tick-to-trade24 / 501
- 15Quant Research & Alt DataSignals from non-market data20 / 501
- 16Tax, Accounting & ReportingLots, elections, reconciliation16 / 501
Every skill, the same shape
Seven sections.
501 times.
The structure is not a convention contributors are asked to follow. A validator in CI rejects a skill missing any heading, any file, or naming a skill that does not exist.
- 01When to Use
- The trigger, stated as a situation. Every description opens with “Use when…”, so an agent matches on the symptom in front of it rather than the subject it guesses.
- 02When NOT to Use
- Where the skill stops. Each excluded case names the skill that owns it. This one section is why the library is a graph, and why a near-miss match is handed on instead of applied.
- 03Prerequisites
- What must already be true before the workflow is safe: a broker field that echoes back, a durable ledger, a clock you trust.
- 04Workflow
- The procedure, in order. The reference implementation in scripts/ follows it step for step, so the prose and the code cannot disagree without a test noticing.
- 05Common Pitfalls
- The named failure modes: the ones that pass review and fail in production. Would following this skill have prevented a real incident is the bar for inclusion.
- 06Verification
- A command you can run. Every skill quotes its own test suite, and the sign-off checklist in assets/ is derived from this section.
- 07Related Skills
- Neighbours in the graph, each with the reason it is adjacent. Every slug named here must exist, or the build that validates the library fails.
- Six files, machine-enforced
SKILL.md
references/standards.md
references/workflows.md
scripts/<helper>.py
scripts/test_<helper>.py
assets/checklist.md
The scale
2.0M words.
Read one at a time.
About 0.8 million words of SKILL.md and another 1.2 million in references and checklists, beside 521,000 lines of Python. No context window holds it, and none needs to. An agent reads the index, opens one document, and reads its boundary before anything else.
Get started
Clone it. Point
your agent at it.
The library needs no runtime and no service. It is Markdown and standalone Python, read by any tool that understands a SKILL.md. The repository ships instruction files for each of these:
- Claude Code
- GitHub Copilot
- Codex CLI
- Cursor
- Gemini CLI
- Aider
- Cline
- Windsurf
- Continue
git clone https://github.com/HimanshuJ16/Algo-Trading-Skills.gitpip install -r requirements-dev.txtpython tools/validate_skills.pypython tools/run_all_tests.py