agentleFS
INo-xiousINo-xious/stockbit-mcp/skills/trade-with-guardrails/SKILL.md

trade-with-guardrails

Skill58 starsChanged 3 months agoMITView on GitHub

Use Stockbit website virtual trading or the separate local paper ledger for simulated buy, sell, amend and cancel requests. Real-money execution is unavailable; brokerage portfolio tools are read-only.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 4 are distinctive, and 5 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.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a request leaves the simulation account unclear, clarify which of the last two the user means.

    line 15
  2. Distinctive:

    Never present simulated holdings or fills as real money.

    line 16
  3. Very specific:

    Read virtual_portfolio and virtual_orders first.

    line 21
  4. Very specific:

    Read trading_status. When paper is off, the user can enable it at their terminal with stockbit-auth trading-enable --paper.

    line 32
  5. Very specific:

    Call paper_order_preview with the requested action, symbol, price and lots (or the existing paper order identifier).

    line 35
  6. Very specific:

    Never set confirm: true on the user's behalf without authorization for that specific change.

    line 43
  7. Distinctive:

    Never ask for the PIN, password, OTP, cookie or token in chat.

    line 44
  8. Very specific:

    Never resend an uncertain write.

    line 46
  9. Distinctive:

    Keep absent or unrecognised values absent.

    line 48

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

Simulated trading with guardrails

This server cannot execute real-money trades. Distinguish three accounts before selecting tools:

  • Brokerage portfolio: portfolio, position, cash_balance, orders and order_history read the real account. Simulation mode does not redirect these tools.
  • Stockbit website virtual account: virtual_portfolio, virtual_position and virtual_orders.
  • Local paper ledger: paper_portfolio, paper_position and paper_orders.

If a request leaves the simulation account unclear, clarify which of the last two the user means. Never present simulated holdings or fills as real money. A request for a real-money trade cannot be fulfilled by silently substituting a simulation.

Website virtual trading

Read virtual_portfolio and virtual_orders first. Use virtual_config for the website's fee settings. Activate with virtual_activate only when the user intends to start the virtual account.

For a simulated order, state the account, symbol, side, limit price and lots before calling virtual_order. Use virtual_order_amend or virtual_order_cancel with an order identifier read from that virtual account. Every virtual write requires authorization for that specific change; confirm: true conveys that authorization. These tools support day limit orders and do not publish trades to the social stream.

Local paper ledger

Read trading_status. When paper is off, the user can enable it at their terminal with stockbit-auth trading-enable --paper; this cannot enable real trading.

Call paper_order_preview with the requested action, symbol, price and lots (or the existing paper order identifier). Read the ticket's checks and relay its summary verbatim, including the PAPER ACCOUNT label. After agreement, use the corresponding paper_order_buy, paper_order_sell, paper_order_amend or paper_order_cancel with the ticket identifier. Tickets expire after two minutes. Local simulated fill rules do not match exchange execution or Stockbit's virtual engine.

Results and secrets

  • Never set confirm: true on the user's behalf without authorization for that specific change.
  • Never ask for the PIN, password, OTP, cookie or token in chat. Brokerage reads may require the user to unlock a securities session through their own terminal.
  • Never resend an uncertain write. Read outcome and relay message; inspect current orders before deciding what happened. An accepted order record is not proof that it filled.
  • Keep absent or unrecognised values absent. Do not turn missing cash, positions or quantities into zero.

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.