agentleFS
alsk1992alsk1992/strata-agent-skills/skills/strata/SKILL.md

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

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. momori777/Artemis★ 445same name
    2. AhmedNazihX/Strata★ 4same name
    3. SanStone3/agent-strata★ 2same name
    4. 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
  1. Distinctive:

    Use Strata's official interfaces to discover live capabilities, inspect markets, request Sonar quotes, and—when the external agent owner …

    line 8
  2. Distinctive:

    Prefer the configured Strata MCP tools for discovery and interactive work.

    line 14
  3. Very specific:

    Use npx -y @stratabook/sdk for terminal discovery, scripted action primitives, and non-trading certification.

    line 15
  4. Distinctive:

    Use the TypeScript or Rust SDK for persistent market, account, maker, or order-command streams.

    line 17
  5. Distinctive:

    Do not call undocumented HTTP paths or reconstruct private behavior.

    line 20
  6. Distinctive:

    Read live capabilities before every objective.

    line 24
  7. Distinctive:

    Read the executable action graph and follow only edges whose required live capabilities are enabled.

    line 25
  8. Distinctive:

    Never silently convert a human token amount without confirmed token decimals.

    line 35
  9. Distinctive:

    Treat preparation and submission as separate live capabilities.

    line 40
  10. Distinctive:

    Keep all signing external to Strata.

    line 42
  11. Distinctive:

    Prefer the official persistent order-command client for latency-sensitive place, cancel, cancel-all, replace, and batch operations when …

    line 47
  12. Distinctive:

    Treat placement success as RPC broadcast only.

    line 50
  13. Distinctive:

    Before leaving resting exposure unattended, arm an exact externally verified and pre-signed cancel-all ticket and maintain its SDK …

    line 52
  14. Very specific:

    Run the non-trading order-slo certification before making latency claims.

    line 56
  15. Distinctive:

    Read the wallet's maker status and reputation before changing liquidity.

    line 66
  16. Very specific:

    Prefer strata_market_making_prepare for ordinary Strand or Current work.

    line 67
  17. Very specific:

    Verify and externally sign only prepared.transaction_base64.

    line 71
  18. Distinctive:

    Use the product-specific low-level tools only when the strategy deliberately controls every array and safety field.

    line 75
  19. Distinctive:

    Treat expiry and minimum output as hard constraints.

    line 92
  20. Distinctive:

    Treat a disabled capability, unavailable market, contract mismatch, or expired quote as a stop condition.

    line 93
  21. Distinctive:

    Never request or accept a private key, keypair, seed phrase, session secret, or production credential in a prompt.

    line 96
  22. Distinctive:

    Never claim chain completion from preparation, signing, or the immediate broadcast receipt.

    line 98
  23. Distinctive:

    Never claim maker activation or collateral release from preparation or RPC broadcast.

    line 100
  24. Distinctive:

    Read references/public-contract.md when exact field semantics, terminal commands, errors, or interface selection matter.

    line 103

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Prefer the configured Strata MCP tools for discovery and interactive work.
  2. Use npx -y @stratabook/sdk for terminal discovery, scripted action primitives, and non-trading certification.
  3. 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

  1. Read live capabilities before every objective.
  2. Read the executable action graph and follow only edges whose required live capabilities are enabled.
  3. List markets and select an opaque market ID marked ready.
  4. Resolve the exact side, atomic amount, tolerance, and owner-configured signer authority. Ask when an economically meaningful input is ambiguous.
  5. Request a fresh Sonar quote and verify its market, side, input, fees, minimum output, server time, and expiry.
  6. 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-slo certification 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_prepare for 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 returned preparationToken unchanged with the signed transaction to strata_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, prefer platform_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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.