strata
Skill0 starsChanged 4 months agoApache-2.0View on GitHub
Discover and use Strata's capability-gated market, Sonar quote, account, execution, market-making, and persistent order-command interfaces. Use when an agent needs live market data, exact trade economics, externally signed operations, Strand or Current liquidity, maker funding and monitoring, safe resting-order automation, dead-man cancellation, or order-stream latency certification.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- momori777/Artemistheir own version, first seen Oct 25, 2026
- SanStone3/agent-stratatheir own version, first seen Oct 8, 2026
- AhmedNazihX/Stratatheir own version, first seen Oct 2, 2026
- rx6ru/stratatheir own version, first seen Aug 27, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- momori777/Artemis★ 445same name
- AhmedNazihX/Strata★ 4same name
- SanStone3/agent-strata★ 2same name
- rx6ru/strata★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. 0 are common, 20 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
20
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use Strata's official interfaces to discover live capabilities, inspect markets, request Sonar quotes, and—when the external agent owner …
- Distinctive: line 14
Prefer the configured Strata MCP tools for discovery and interactive work.
- Very specific: line 15
Use npx -y @stratabook/sdk for terminal discovery, scripted action primitives, and non-trading certification.
- Distinctive: line 17
Use the TypeScript or Rust SDK for persistent market, account, maker, or order-command streams.
- Distinctive: line 20
Do not call undocumented HTTP paths or reconstruct private behavior.
- Distinctive: line 24
Read live capabilities before every objective.
- Distinctive: line 25
Read the executable action graph and follow only edges whose required live capabilities are enabled.
- Distinctive: line 35
Never silently convert a human token amount without confirmed token decimals.
- Distinctive: line 40
Treat preparation and submission as separate live capabilities.
- Distinctive: line 42
Keep all signing external to Strata.
- Distinctive: line 47
Prefer the official persistent order-command client for latency-sensitive place, cancel, cancel-all, replace, and batch operations when …
- Distinctive: line 50
Treat placement success as RPC broadcast only.
- Distinctive: line 52
Before leaving resting exposure unattended, arm an exact externally verified and pre-signed cancel-all ticket and maintain its SDK …
- Very specific: line 56
Run the non-trading order-slo certification before making latency claims.
- Distinctive: line 66
Read the wallet's maker status and reputation before changing liquidity.
- Very specific: line 67
Prefer strata_market_making_prepare for ordinary Strand or Current work.
- Very specific: line 71
Verify and externally sign only prepared.transaction_base64.
- Distinctive: line 75
Use the product-specific low-level tools only when the strategy deliberately controls every array and safety field.
- Distinctive: line 92
Treat expiry and minimum output as hard constraints.
- Distinctive: line 93
Treat a disabled capability, unavailable market, contract mismatch, or expired quote as a stop condition.
- Distinctive: line 96
Never request or accept a private key, keypair, seed phrase, session secret, or production credential in a prompt.
- Distinctive: line 98
Never claim chain completion from preparation, signing, or the immediate broadcast receipt.
- Distinctive: line 100
Never claim maker activation or collateral release from preparation or RPC broadcast.
- Distinctive: line 103
Read references/public-contract.md when exact field semantics, terminal commands, errors, or interface selection matter.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Strata
Use Strata's official interfaces to discover live capabilities, inspect markets, request Sonar quotes, and—when the external agent owner has configured signer authority—prepare and submit externally signed operations.
Choose an interface
- Prefer the configured Strata MCP tools for discovery and interactive work.
- Use
npx -y @stratabook/sdkfor terminal discovery, scripted action primitives, and non-trading certification. - Use the TypeScript or Rust SDK for persistent market, account, maker, or order-command streams.
Do not call undocumented HTTP paths or reconstruct private behavior.
Enter through discovery
- Read live capabilities before every objective.
- Read the executable action graph and follow only edges whose required live capabilities are enabled.
- List markets and select an opaque market ID marked ready.
- Resolve the exact side, atomic amount, tolerance, and owner-configured signer authority. Ask when an economically meaningful input is ambiguous.
- Request a fresh Sonar quote and verify its market, side, input, fees, minimum output, server time, and expiry.
- Report consumed input, expected and minimum output, fees by asset side, price impact, and remaining validity.
Never silently convert a human token amount without confirmed token decimals. Preserve every atomic amount as a base-10 string.
Execute when available
- Treat preparation and submission as separate live capabilities. Package support or an earlier session never enables an operation.
- Keep all signing external to Strata. Request canonical authorization bytes, have the owner-configured signer sign them, verify the prepared transaction, and submit with a stable idempotency key.
- For resting orders, select an explicit self-trade prevention policy. Never infer one and never accept a mode that permits a self-fill.
- Prefer the official persistent order-command client for latency-sensitive place, cancel, cancel-all, replace, and batch operations when WebSocket transport is advertised.
- Treat placement success as RPC broadcast only. Consume the pushed terminal status or recover it durably before claiming completion.
- Before leaving resting exposure unattended, arm an exact externally verified and pre-signed cancel-all ticket and maintain its SDK heartbeat. Lost heartbeats must fail closed into cancellation; disarm only through an explicit owner-authorized operation.
- Run the non-trading
order-slocertification before making latency claims. It uses an authenticated nonce echo that cannot prepare, sign, submit, or cancel an order. Require both the controlled-latency and saturated-capacity gates to pass. - Let the official SDK batch concurrent command and result frames. Agent code keeps calling the ordinary command methods; do not construct transport batches or infer shared results.
Run market making when available
- Read the wallet's maker status and reputation before changing liquidity.
- Prefer
strata_market_making_preparefor ordinary Strand or Current work. Pass the market label, product, maker public key, spread, decimal base size, duration, and any intentional level settings. Do not hand-build atoms or fixed arrays for this path. - Verify and externally sign only
prepared.transaction_base64. Pass the returnedpreparationTokenunchanged with the signed transaction tostrata_market_making_submit_and_wait. The token has no signing authority and keeps the continuation valid across stateless MCP requests and restarts. - Use the product-specific low-level tools only when the strategy deliberately controls every array and safety field. A Current follows Strata's live mark; do not invent a separate oracle publisher or publisher transaction.
- Initialize the market Vault when needed, activate the maker product, and deposit exact collateral through the public Vault tools. Treat collateral as locked while a control is live. Claim start, stop, expiry, or release only after chain-derived maker status confirms it.
- In TypeScript, prefer
marketMaking.start(...)/stop(...); in Rust, preferplatform_maker_start(...)/platform_maker_stop(...). Both keep signing external, verify exact transaction bytes, submit idempotently, and wait for chain-derived state.
Interpret safely
- Describe the response as one unified Sonar quote.
- Base explanations on the returned quote fields; do not invent a breakdown that is not present.
- Treat expiry and minimum output as hard constraints.
- Treat a disabled capability, unavailable market, contract mismatch, or expired quote as a stop condition.
- Recover any stream sequence gap from a fresh snapshot or durable status read.
- Never request or accept a private key, keypair, seed phrase, session secret, or production credential in a prompt.
- Never claim chain completion from preparation, signing, or the immediate broadcast receipt.
- Never claim maker activation or collateral release from preparation or RPC broadcast; reconcile the returned chain-derived maker status.
Read references/public-contract.md when exact field semantics, terminal commands, errors, or interface selection matter.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

