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

pm-paper-trade-ops

Skill466 starsChanged 34 days agoApache-2.0View on GitHub

Run, monitor, intervene in and archive paper trading after a strategy has passed backtesting.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user asks to run paper trading or to check live behavior without real money.

    line 8
  2. Very specific:

    Add --monitor for the live terminal view.

    line 20
  3. Distinctive:

    Never use live credentials during paper trading.

    line 39
  4. Distinctive:

    Every run must be replayable from its configuration (strategy ref, kwargs, duration, exchange).

    line 40

≈ “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 Paper Trade Ops

Use this skill when the user asks to run paper trading or to check live behavior without real money.

Preconditions

  • The strategy passes oracle3 strategy validate ... --json.
  • There is at least one interpretable backtest or auto-tune result.

Steps

  1. Start paper trading
  • oracle3 paper run --exchange <polymarket|kalshi|solana|rss> --strategy-ref <strategy_ref> --strategy-kwargs-json '<json>' --duration <seconds> --json
  • Add --monitor for the live terminal view.
  1. Control the running engine
  • oracle3 trade status --json
  • oracle3 trade state --json
  • oracle3 trade pause --json
  • oracle3 trade resume --json
  • oracle3 trade swap --strategy-ref <strategy_ref> --strategy-kwargs-json '<json>' --json
  • oracle3 trade stop --json
  1. Archive the results
  • Save the key outputs to data/research/<run_id>/paper/.
  • Include at least the configuration, a state snapshot and the end-of-run summary.

Hard rules

  • On any anomaly, pause first; resume or stop only after checking.
  • Never use live credentials during paper trading.
  • Every run must be replayable from its configuration (strategy ref, kwargs, duration, exchange).

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