agentleFS
MendurimMendurim/strikegrok-trading-desk/skills/strike-setup/SKILL.md

strike-setup

Skill0 starsChanged 2 months agoMITView on GitHub

Prepare the desk computer to work with Strike Finance - the two surfaces (public market data and the signed trading API), confirm public connectivity, provision the API wallet through the secure secret store when the user asks to trade, run the read-only readiness check, and understand why the desk rehearses with previews and minimum-size orders rather than testnet. Use during desk setup, when moving between research and trading levels, when a key is rotated, or when any Strike call fails with an environment problem.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No Bot prints, echoes, journals or forwards the private key.

    line 59
  2. Distinctive:

    Run before the first send of any session.

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Strike setup

Sections 1-3 are read-only and safe at any time. Section 4 provisions the API wallet and happens only when the user asks to trade. Section 5 is the readiness check the Execution Trader runs before its first send.

1. The surfaces

Market dataTrading
Base URLhttps://api.strikefinance.org/pricehttps://api.strikefinance.org
Path/v2/.../v2/...
AuthnoneEd25519 API wallet headers
SymbolsADA-USD, XAU-USDthe same
Markets31 quoted31 tradeable
Skillstrike-market-datastrike-auth, strike-orders

One symbol vocabulary across both, and every market that is quoted can be traded. Testnet is https://api-v2-testnet.strikefinance.org for both, with four markets - see section 6 before relying on it.

There is also an optional research add-on, the crowdtime MCP (strike-research-tools). It is not part of the trading path and the desk works fully without it. If the desk is not using it, do not provision its token at all.

2. Install

Nothing to install. Reads are curl; signed calls go through scripts/strike_request.py, which uses the cryptography package when it is present and falls back to openssl when it is not. Both are standard on the desk computer.

python3 --version              # 3.9+
openssl version                # needed only if the cryptography package is absent
cd /workspace/strikegrok && bash scripts/check.sh

3. Connectivity check (no credential)

BASE=https://api.strikefinance.org/price
curl -sS -m 10 "$BASE/v2/exchangeInfo" \
  | python3 -c "import sys,json; d=json.load(sys.stdin); print('ok,', len(d['symbols']), 'markets, serverTime', d['serverTime'])"
python3 scripts/opening_bell.py --symbol BTC-USD

Record the UTC time and result in the desk record. A research desk needs nothing more: briefs, dossiers, the catalyst calendar and the strategy lab all run with no credential.

4. The API wallet (only when the user asks to trade)

Full procedure in strike-auth. In short:

  1. Generate an Ed25519 keypair on the desk computer with openssl, then delete the PEM.
  2. The user registers the public key at app.strikefinance.org/api-keys.
  3. Both keys go into Grok Bot's secure secret store as STRIKE_API_PUBLIC_KEY and STRIKE_API_PRIVATE_KEY. Never chat, never a file.
  4. No Bot prints, echoes, journals or forwards the private key.

The key can trade; neither the trade API nor the user API exposes a withdraw, deposit or transfer endpoint, so it cannot take money out. That is the bounded credential the desk is designed around. Keep on Strike only what the desk is meant to be trading anyway.

5. Readiness check (read-only, no order)

Run before the first send of any session.

cd /workspace/strikegrok
python3 scripts/strike_request.py GET /v2/account      # auth works, equity is live
python3 scripts/strike_request.py GET /v2/positions    # what is already carried
python3 scripts/strike_request.py GET /v2/openOrders   # and what is already resting
curl -sS "https://api.strikefinance.org/price/v2/exchangeInfo" >/dev/null && echo "market data ok"

Four green reads and the desk may trade. Record the UTC time and the equity figure in desk.md.

A 401 means the key is unregistered, wrong, or the clock has drifted - strike-auth section 8 has the checklist. Stop there. Never retry with a guessed key, and never fall back to an unauthenticated path and report success.

6. Rehearsal, honestly

Strike's testnet cannot rehearse a trade. It lists four markets and its books are empty, so an order there proves the request is well-formed and signed correctly - and nothing else. No fill, no slippage, no trigger behaviour, no protection under load.

It is still worth exactly that much: --testnet on strike_request.py is a good way to prove the signing scheme works before the key touches real money. Use it for that, and claim nothing more.

The desk replaces the rest with two rules that do work:

  1. The preview block. Strike's API has no dry-run mode, so every send is built as a JSON file, posted to the floor verbatim as a PREVIEW beside the ticket, and sent only after the user's approval by id. The bytes previewed are the bytes sent (strike-orders section 3).
  2. Minimum size first. The first live run of any new kind of action - first bracket, first trigger, first replace, first close, first TWAP - is done at minimum size. MIN_NOTIONAL is $10 across Strike's markets, so a real rehearsal costs a few dollars in fees.

Record in desk.md which action kinds have had their minimum-size rehearsal. Do not claim testnet coverage the desk does not have.

7. Rotation

Generate a new keypair, register the new public key, replace both secret-store entries, re-run section 5, then delete the old key at app.strikefinance.org/api-keys. Record the date in desk.md - never the key.

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.