I asked Q how to set up my Builder instead of telling it what to set
In the previous article Q built 201 breakout custom blocks for me in three and a half minutes. This is what I did with them the same day, and the …
Přejít k obsahu | Přejít k hlavnímu menu | Přejít k vyhledávání
A StrategyQuant strategy is never conjured whole. The platform assembles it from parts you supply, then searches the combinations for something that works. Those parts stack in a fixed order — and I have built an AI skill for each layer of the stack, four in all. Together they make up the SQX Authoring Toolkit (the sqx-lab plugin). You describe the part you want in plain English; the matching skill authors a real, import-ready artifact, checked against your own installation. This is a practical guide to what the four skills do and how you build with them.
We have reached a strange moment. Any AI can now produce something that reads like a trading strategy — a confident paragraph, a plausible rule, a block of code that sounds right. Almost none of it survives contact with a real engine. That gap — between output that looks correct and output that actually runs — is the whole problem, and it is exactly what this workflow is built to close.
Nothing here rests on the AI’s word. Every artifact is authored to be accepted by StrategyQuant itself, and the workflow ends where it should: in an actual AlgoWizard Build on real data. The platform — its parser, its builder, its backtesting engine — has the final say, not the model. A strategy either imports, builds and backtests, or it does not; there is no room for a plausible-looking answer that quietly fails.
That is the beautiful part of doing this today. Generation has become cheap; verification is everything. An AI that can generate a thousand strategies is a liability. One whose every output is answerable to a real backtesting engine is a tool you can actually trust — and it is why, in my own pipeline, the next step is an oracle that loads each artifact into a live StrategyQuant and lets the engine confirm it before I ever rely on it.
Everything in StrategyQuant is built from four kinds of part, each composed from the one before it:
Authoring each layer by hand is expert, click-heavy work that assumes deep knowledge of the platform. Each skill automates one layer — and because they compose in the same order, a single idea can travel from one rule all the way to a running build project without your writing a line of XML.
| Layer | Skill | What it authors |
|---|---|---|
| Block | sqx-custom-block | A single trading rule — a signal, a filter, or a price level. |
| Group | sqx-random-group | A pool of blocks or atoms the builder samples one item from. |
| Template | sqx-strategy-template | A buildable .sqx strategy that wires groups into a shape. |
| Project | sqx-strategy-project | A runnable project.cfx that builds templates on real data. |
One principle underpins all of them, and it is the reason they are trustworthy: every skill is install-derived. Before it authors anything, it reads your StrategyQuant installation and builds a catalog of exactly what your build can do — the native indicators, your exported custom blocks, and even indicators you have only coded in the editor. It then builds strictly from that catalog. It cannot reach for an indicator you do not have, so nothing it produces is a “phantom” that fails on import.
All four skills follow one disciplined workflow. Learn it once and it applies to blocks, groups, templates and projects alike.
A custom block is the atomic unit of a StrategyQuant strategy: a single, reusable piece of logic you drop into AlgoWizard. The skill authors both kinds. A Condition block is a true/false rule — a signal or a filter. A Price-level block returns a price — a stop, a target, a band, or a breakout reference.
You describe — “long when RSI(14) crosses above 30, and short the mirror.”
You get — a validated Condition block whose RSI period (2–50) and oversold level are exposed as optimizable parameters, together with its short-side mirror, paired automatically, as import-ready XML.
Import: AlgoWizard → Custom Blocks → Import.
A random group is a menu the builder draws one item from — per strategy, per slot. It overrides the global Building-Blocks settings for that single slot: instead of the builder choosing from everything, it samples one item from a set you curated. Groups come in two types. A Condition group pools boolean rules; a Value group pools prices or levels. A template binds a group to one of its holes by the group’s unique identifier.
You describe — “group my breakout trigger blocks into one pool.”
You get — a validated Condition group that re-exports your breakout blocks by reference — the exact menu the builder will sample from — as import-ready XML.
Import: AlgoWizard → Random / Block groups → Import.
A strategy template is a StrategyQuant strategy with some of its sub-expressions left as typed holes that the builder fills and varies. This is the most delicate layer, because a strategy’s validity is not guaranteed by its structure alone — engine exclusions, magic-number wiring and the signal-variable protocol all live outside the schema, and only an actual Build proves a strategy sound. So the skill does not hand-write strategy XML. It transplants your chosen groups into a build-confirmed skeleton and varies only the holes, staying strictly inside proven territory.
You describe — “breakouts only in the trend direction, entered on a stop at the prior-period high.”
You get — a .sqx template that wires a trend filter, a breakout trigger and a stop-price pool into a proven shape, with the short side mirrored automatically and the full exit stack already in place.
Import: AlgoWizard → import the .sqx → run a Build.
A project file carries everything a build needs: the data feed, the symbol and timeframe, and the entire exit and acceptance stack. That is far too much to regenerate safely, so this skill clones a project you already trust and swaps in one build task per template — each task with its own results databank.
You describe — “clone my EURUSD H1 base and wire these three templates as tasks, over 2015–2020.”
You get — a ready-to-run project — three build tasks, each writing to its own databank, inheriting your base’s data and settings with the new date window applied — deployed into your install.
Use: deploy into the install → open the project → run a Build.
Because the skills compose, a single idea can travel all four layers in one sitting, each output feeding the next:
Every step is validated before the next, and every atom is one your install actually has — so the whole chain imports and builds.
The four skills above are what I have released — the authoring layer. Two things sit on top of them that I am actively building, and I want to be clear that neither is released yet.
The skills validate everything for import, but in my own work I go one step further. I load each artifact into a running StrategyQuant over its REST interface, so the platform itself confirms the artifact is real before I trust it — a LOAD PASS from StrategyQuant is worth more than any self-check. I am building this oracle into a strategy plugin that authors and verifies whole strategies end to end. It runs privately today; it is not something you can download yet.
Above that sits a factory. It takes a market hypothesis, has these skills author the template and its groups, uses the oracle to confirm they load, then generates and judges an entire population of strategies on out-of-sample statistics — the Deflated Sharpe Ratio and the Probability of Backtest Overfitting — and returns a verdict: graduate, revise, or kill. It is in active development.
The four skills ship together as the SQX Authoring Toolkit — the sqx-lab plugin. If you would like to put them to work on your own StrategyQuant install, or you are curious where the oracle and the factory are heading, get in touch.
In the previous article Q built 201 breakout custom blocks for me in three and a half minutes. This is what I did with them the same day, and the …
Q, the AI assistant in StrategyQuant X, searched the web for breakout ideas and turned them into 201 custom blocks, the entry conditions and price levels that strategies are built …

What if you could control StrategyQuant X simply by talking to an AI agent? With the introduction of MCP (Model Context Protocol), we’re taking another step toward a new era …
1. Can I ask by asking it to convert my powerlanguage strategy which I copy and paste onto it then ask it to create SQ strategy?
2. Can I upload research paper in pdf file that I think have an edge for it to read and later to create SQ strategy?