agentleFS
Sign inStart free
YichengYang-EthanYichengYang-Ethan/oracle3/.claude/skills/pm-live-trade-ops/SKILL.md

pm-live-trade-ops

Skill466 starsChanged 34 days agoApache-2.0View on GitHub

Run live trading only with explicit user authorization, under strict risk and emergency controls.

  • Reads credentials

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Use this skill only when the user explicitly asks for live trading and paper validation is complete.

    line 8
  2. Distinctive:

    Never start live trading without explicit user approval.

    line 45
  3. Distinctive:

    Never skip paper trading and go straight to live.

    line 46
  4. Distinctive:

    Every live run keeps an auditable record: time, parameters, state snapshots and every intervention.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

PM Live Trade Ops

Use this skill only when the user explicitly asks for live trading and paper validation is complete.

Gates

  • strategy validate passes.
  • The latest backtest or auto-tune results are acceptable.
  • Recent paper runs behaved stably.
  • The user has explicitly approved starting live trading.

Start commands

  1. Polymarket
  • oracle3 live run --exchange polymarket --wallet-private-key "$POLYMARKET_PRIVATE_KEY" --strategy-ref <strategy_ref> --strategy-kwargs-json '<json>' --json
  1. Kalshi
  • oracle3 live run --exchange kalshi --kalshi-api-key-id "$KALSHI_API_KEY_ID" --kalshi-private-key-path "$KALSHI_PRIVATE_KEY_PATH" --strategy-ref <strategy_ref> --strategy-kwargs-json '<json>' --json

Run control

  • oracle3 trade status --json
  • oracle3 trade state --json
  • oracle3 trade pause --json
  • oracle3 trade resume --json
  • oracle3 trade killswitch --on --json
  • oracle3 trade stop --json

Emergency order

  1. pause first.
  2. Assess positions and open orders.
  3. If needed, killswitch --on.
  4. Finally, stop.

Hard rules

  • Never start live trading without explicit user approval.
  • Never skip paper trading and go straight to live.
  • Every live run keeps an auditable record: time, parameters, state snapshots and every intervention.
  • The MCP server (oracle3-mcp) has no live-trading tools; live trading is only available through this CLI.

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.

Check your setup, free