Skip to content

← Back to Skills

Quant · No market data required

Strategy rule specification

Make a trading idea explicit and find the gaps before execution or testing.

See what you will get

Turn an idea into rules you can check.

Synthetic teaching sample · not a real company / fund
Turn an idea into rules you can check.
ConditionTeaching ruleOrigin / status
Assets and weightsETF_A 60% / ETF_B 40%User idea
Rebalance / benchmarkMonth end / equal-weight buy and holdUser idea
Signal → executionAfter close → next valuation closeProposed; confirm first
Friction / cash return10 bps per side / 0Proposed; confirm first
Initial value / currency10,000 / synthetic SYNTH unitsProposed; confirm first

ETF_A and ETF_B are teaching identifiers. Set confirmed only after explicit acceptance, recording time and rule digest. Otherwise return needs-input.

Keep the records in your workspace

Rule card, cost assumptions and data requirements

strategy-card.mdstrategy.jsondata-requirements.mdconfirmation.md

Each run writes to a new reports/{run-id}/, preserving inputs and previous reports. Status distinguishes completed, needs-input and failed.

What to prepare

Your idea and asset scope. Missing frequency, weights, execution timing or costs become questions first.

File preparation & data definitions →

Start with this request

Use the strategy specification Skill to turn my idea into testable rules. Separate my decisions, your proposed defaults and unresolved questions. Specify signal and execution timing. Do not run a backtest yet.

First ask your host to inspect the method version, inputs, output location and dependencies in read-only mode. Downloading, discovering a Skill and completing its sample are separate steps.

Its limits

This step does not run a backtest. Suggested defaults require actual confirmation, and changed rules need confirmation again. Unsupported strategies receive a draft and limits.

No network retrieval, account connection or result upload by default. Model handling depends on your host and service settings; this is not a promise of fully offline processing.

Continue your work

Once rules are explicit and confirmed, test them against data.

Daily ETF validation →

Read the related case →