Open-source library adds 501 trading infrastructure skills for AI coding agents

The repository provides a structured way to inject quant-engineering expertise into AI agents. Each of the 501 skills is a self-contained module that encodes a production practice, such as order-placement idempotency or wash-trade detection, alongside the regulatory mandate it satisfies. This mapping lets an agent generate code that complies with SEC Rule 15c3-5 or MiFID II RTS 6 without the engineer having to recall every edge case those rules create. The cost is the time needed to integrate the library and verify that the agent’s output still matches the intended regulatory regime.

Unit tests back every skill, but the tests run against reference implementations, not live broker APIs. A skill that passes its tests may still fail in production if a broker’s API deviates from the documented behavior or if the exchange’s matching engine enforces additional constraints. The library’s "When NOT to Use" sections mitigate this by explicitly listing the scenarios each skill does not cover, but engineers must still review the agent’s output before deploying to paper or live accounts.

Regulatory coverage spans the US, EU, UK, Australia, India, Singapore, and ISDA OTC derivatives, yet the library does not provide legal or compliance advice. It encodes the engineering controls mandated by each regime, kill switches, pre-trade risk checks, order tagging, but does not certify that a system built with these skills will pass an audit. Engineers must still consult qualified professionals to ensure the final system meets jurisdiction-specific requirements.

The library is tool-agnostic: any AI agent that can read a SKILL.md file can consume it. This interoperability reduces lock-in but also means the agent’s ability to apply the skills correctly depends on the quality of its prompt and the context window it can retain. A skill that warns against blocking the WebSocket read loop during volatility spikes is useless if the agent’s context window is too small to keep the warning in scope while generating the callback code.

Community maintenance is both a strength and a limitation. The repository is open-source and Apache 2.0 licensed, so engineers can fork it to add broker-specific quirks or new regulatory regimes. However, the project’s disclaimer that it is not affiliated with any vendor or exchange means there is no formal support channel for production issues. Engineers adopting it must be prepared to debug and extend the skills themselves.