Ready-Made Skills and Prompts for AI Assistants

tradeSteward gives your assistant eight ready-made workflows, each a numbered list of steps that tells it which tools to use, in what order, and what never to do. In Claude Code they are skills; in Claude, ChatGPT, Codex and other clients they are the connector's prompts. This article explains how to start a workflow and covers the six bot and Backtick workflows; the two report workflows are in Ready-Made Report Workflows and Resources.

The plan and the connection you need are in Connect tradeSteward to Claude, ChatGPT or Codex.

How to start a workflow

Each workflow lists the permissions and the plan it needs. A workflow is offered to a connection only when the connection may use every tool its steps need and holds every permission it lists. One you are not offered is simply missing from the list; turn the permission on from Connected Apps and it appears. Choose What a Connection May Do has the full table.

In Claude Code

The tradeSteward plugin installs one skill per workflow, named with hyphens: build-bot, review-bot-performance, analyze-stop-fills, analyze-fill-slippage, backtest-strategy, backtest-to-bot, build-report and build-portfolio. Type a slash, the plugin name, a colon and the skill name, then your request in your own words:

/tradesteward:build-bot SPX 10 delta put spread, 9:31 ET, 1 contract, 200% stop, 50% profit target, Schwab individual account, strategy group Income

Claude Code also picks a skill on its own when your request matches its description, so "test this strategy in Backtick" starts backtest-strategy without the slash command. If the skill answers that its tools are not available, run /mcp, choose tradesteward and sign in.

In Claude, ChatGPT, Codex and other clients

The same eight workflows are the connector's prompts, named with underscores: build_bot, review_bot_performance, analyze_stop_fills, analyze_fill_slippage, backtest_strategy, backtest_to_bot, build_report and build_portfolio. A client that supports prompts lists them under the tradeSteward connector, each with a short title such as Build a bot and a form for its arguments. Pick one, fill in the arguments and send. Clients differ in where they put the list; look for the connector's prompts, templates or commands.

Build a bot and Test a strategy in Backtick ask for a strategy, and your app may require it. The other prompts can be sent empty. When a prompt arrives with nothing filled in, the assistant is told that you have not said what you want yet and that it must ask you before it creates or changes anything. Each argument is cut at 500 characters.

Bot workflows

Build a bot build-bot / build_bot

Turns a strategy you describe into a tradeSteward bot, saved switched off for you to review.

What it does

1. Reads your account context for broker accounts, symbols and plan limits, then lists strategies separately.
2. Reads the bot settings dictionary before choosing any setting, and uses only settings it lists, with their units and allowed values.
3. Asks you for anything that decides how much money is at risk and is missing from your request: the account, the strategy group, the size, the stop or the profit target. It never guesses those.
4. Checks the settings with the validation tool and fixes every field it reports.
5. Creates the bot.
6. Summarizes the bot in plain words (symbol, legs, entry time, size, stop and profit target) and tells you it is switched off and that you turn it on from the tradeSteward website after reviewing it.

Arguments: strategy (required): the strategy in your own words, with the symbol, the legs, when to enter, the size, the stop and the profit target.

Permissions: View bots and Create bots (always saved disabled). Any Trader plan.

Tools it uses: get_account_context, list_strategies, get_bot_settings_schema, validate_bot_settings, create_bot. The tools are explained in AI Assistant Tools: Building Bots and Pausing Trading.

Example: "Build a 0DTE SPX iron condor: sell the 10 delta call and put, buy wings 20 points out, enter at 10:00 ET, 2 contracts, stop at 150% of credit, profit target 40%, in my Schwab Individual ...4821 account, strategy group Condors." The assistant validates, creates the bot and answers with a summary and a reminder that the bot is off until you turn it on.

Review bot performance review-bot-performance / review_bot_performance

Reviews how your bots have traded: profit and loss, win rate, and the trades behind the numbers.

What it does

1. Reads your account context and lists your bots to find the ones your request is about.
2. Reads each bot's performance over the period you asked for, then the trades behind those numbers for all the bots in one request. Reads a bot's settings only when they help explain a result.
3. Counts every result once. A Multi-Entry bot is listed as one bot and as each of its entries, and the bot's performance already includes its entries, so the assistant never adds the two together.
4. To explain a Multi-Entry bot entry by entry, it reads the bot's trade list once and groups the trades by the entry that made each one: the list holds the trades the connection may see, from every entry it may see, and names each trade's entry.
5. Says that live bot profit and loss is before commissions whenever it quotes it, and never compares it directly with a Backtick figure, which is after commissions.
6. Reports totals, win rate, the best and worst trades and anything unusual, says how many trades each figure rests on, and says when there are too few to conclude anything.
7. Describes any change you might want instead of making it. It edits a bot only when you ask, and never a bot that is live.

Arguments: focus (optional): which bot, strategy or period to look at. Leave it out for the whole account.

Permissions: View bots, View bot settings, View performance, trades and logs. Any Trader plan.

Tools it uses: get_account_context, list_bots, get_bot, get_bot_performance, get_bot_trades. See AI Assistant Tools: Reading Your Account and Bots.

Example: "Review my put spread bots for October and tell me which one is dragging the group down."

Analyze stop fills analyze-stop-fills / analyze_stop_fills

Shows where your stops filled compared with where they were set, and against the last quote the bot logged before it sent the order. It describes only and changes nothing.

What it does

1. Reads your account context and lists your bots to find the ones in question. A Multi-Entry bot's stops already include its entries' stops, so each stop is counted once.
2. For each bot, reads the stops view of the trade fills tool: the closed trades that exited by a price stop, newest first, 25 to a page, up to 20 pages per bot. The tool takes a start date but no end date, so for a period such as "September" the assistant reads from the first day of the period and keeps only the stops that closed inside it, converting the recorded times to US Eastern first. If 20 pages are not enough to reach back to the start of your period, it says the figures cannot cover that period and offers a later start date. The tool is paced, so a bot with many stops takes a few minutes.
3. Reports two measures for each stop: against the last quote (0 is the best price the last bid and ask allowed, 100 the worst, and it can fall outside that range) and against the bot's own stop setting, in that setting's unit. It shows one-hit, no-check and resting stops against their setting only, because they have no logged quote, and it never fills a missing measure with an estimate.
4. Never pools stops that have a different unit (delta, price, dollar, multiple, percent, points), never pools resting stops with engine stops, and splits the stops where you changed the stop setting during the period.
5. Reports each group as a distribution, not an average: the number of stops, the median, the worst, the share beyond a size it states, attempts and the seconds from the first hit and from firing to the fill. It also reports the trades it could not measure, by reason. It reads the log lines behind one stop only when you ask and the connection has the logs tool.
6. Relates the result to the stop slippage and delay a Backtick assumes for the bot's stop speed, and says which Backtick stop values would match your live fills. A Backtick accepts stop slippage from 0 to 200 and stop delay from 0 to 240 seconds, as whole numbers, so it rounds and limits its suggestion and tells you when that changed it.
7. Says that live profit and loss is before commissions and a Backtick figure is after commissions, and does not edit the bot.

Arguments: focus (optional): which bot, stop type or period to look at.

Permissions: View bots, View bot settings, View performance, trades and logs. Any Trader plan.

Tools it uses: get_account_context, list_bots, get_bot, get_bot_trade_fills, and get_bot_logs when you want the log lines behind one stop.

Example: "How did the stops on my SPX 10 Delta Put Spread 9:31a bot fill in September, and what stop slippage should I give a Backtick of it?"

Match Backtick fills to your live fills analyze-fill-slippage / analyze_fill_slippage

Measures where your entries and stops filled inside the bid and ask and how long they took, then works out the Backtick slippage and delay values that match. It describes only, and builds a comparison Backtick only when you ask for one.

What it does

1. Reads your account context, lists your bots, agrees the period with you and reads each bot's entry speed and stop settings.
2. Reads the trade fills tool twice for each bot: the spread view, which lists every closed trade and measures its entry, and the stops view, which lists the trades that exited by a price stop. Both views page 25 trades at a time, up to 20 pages, and share a limit, so a bot can take several minutes. Periods with an end date are handled as in Analyze stop fills.
3. Measures each category. An entry is scored only when every leg's quote was stored within 2 seconds of the fill; entries with a quote further away are left out and counted. For entries and for engine stops it gives the count, the median, the mean and the 25th and 75th percentiles of the slippage and of the seconds, leading with the median because a mean alone is pulled by outliers. It treats the entry delay as a lower bound, because the clock starts after the broker call returned. It reports every excluded trade by reason.
4. Turns the figures into Backtick values: an entry slippage and delay pair and a stop slippage and delay pair, each the median of what was measured, with the 75th percentile as the conservative choice, rounded to whole numbers and limited to 0 to 200 for slippage and 0 to 240 seconds for delay. It sets them beside Backtick's defaults for the bot's entry speed and stop speed, and says which positions need the Overrides switch on.
5. Compares the measured medians with the bot's own stop speed setting and with Backtick's defaults, and says whether the defaults were kinder or harsher than your live fills, and by how much.
6. Says plainly what was not measured: profit-target, time and trail exits (the bot logs no quote when it sends them), entries that filled in part, and penny-wide spreads.
7. Only when you ask, and only when the connection offers the Backtick tools: makes a baseline Backtick from the bots it measured (or a copy of a Backtick you name), applies the measured overrides to a copy with the Overrides switch on for the measured positions and off for the others, runs both, waits for them and compares total profit after commissions, win rate, drawdown and the number of trades. It never touches a bot.
8. Reminds you that live profit and loss is before commissions and a Backtick figure is after commissions.

Arguments: focus (optional): which bot or period to look at, and whether to build a comparison Backtick.

Permissions: View bots, View bot settings, View performance, trades and logs (any Trader plan). The optional comparison Backtick also needs View Backticks and results, Create Backticks, Edit Backticks and positions and Run Backticks, on Backtick Professional.

Tools it uses: get_account_context, list_bots, get_bot, get_bot_trade_fills; for the comparison, get_backtick_capabilities, list_backtests, get_backtest, create_backtest, clone_backtest, update_backtest, run_backtest, wait_for_backtest, get_backtest_status and get_backtest_results.

Example: "Measure the fills of my SPX 10 Delta Put Spread 9:31a bot since July, give me the Backtick slippage and delay to use, and build the comparison Backtick."

Backtick workflows

Test a strategy in Backtick backtest-strategy / backtest_strategy

Sets up a Backtick for a strategy you describe, runs it and reads the results.

What it does

1. Reads your account context and the Backtick capabilities: the symbols and date ranges that have data and your plan's limits.
2. Reads the settings dictionary before choosing any position setting, and uses only settings that apply to positions.
3. Asks when your request leaves out the test period, the size, the stop or the profit target.
4. Creates the Backtick, makes every change to it in one call, then starts it. Several Backticks are started in one call.
5. Waits for the run to finish, asking again while it is still running, and does not call other tools in between. A run the server has scheduled for later is not waited for: the assistant tells you its place in line and checks back after the time the server gives. It reports a failed or refused run with the reason and stops.
6. Reads the results: the summary first, then positions, trades or the equity series as your question needs.
7. Gives you a chart link to the equity curve when your connection offers chart links, or draws the charts from the series in the site's chart colors when it is building a report for you.
8. Reports total profit after commissions, drawdown, win rate and the number of trades, and says that a Backtick is a simulation of the past, not a forecast.
9. Offers the portfolio builder when the Backtick covers one strategy across several cells, such as an entry-time sweep, and you are deciding how many contracts to run.
10. Creates no bot. If you then want one, that is a separate request.

Arguments: strategy (required): the strategy in your own words. period (optional): the dates to test, for example 2024 or the last two years; leave it out to be asked.

Permissions: View Backticks and results, Create Backticks, Edit Backticks and positions, Run Backticks. Needs Backtick Professional.

Tools it uses: get_account_context, get_bot_settings_schema, get_backtick_capabilities, create_backtest, update_backtest, run_backtest, wait_for_backtest, get_backtest_status, get_backtest_results, and create_backtest_chart_link when your connection offers it. See AI Assistant Tools: Building and Running Backticks.

Example: "Test an SPX 0DTE put spread sold at 20 delta, 25 points wide, entered at 9:45 ET with a 200% stop and no profit target, over 2023 and 2024."

Turn a Backtick position into a bot backtest-to-bot / backtest_to_bot

Picks a position from a completed Backtick and saves it as a bot, switched off for you to review.

What it does

1. Reads your account context for broker accounts and calls list_strategies for strategy groups.
2. Finds the Backtick in your list and reads it. Only a completed Backtick has results.
3. Reads the results for its positions and shows how each performed so that you can choose. When more than one is reasonable, it does not choose for you.
4. Asks which broker account and strategy group the bot belongs to, unless your request already says.
5. Converts the chosen position to a bot.
6. Reads the new bot and summarizes it in plain words.
7. Tells you the bot is switched off and that you turn it on from the tradeSteward website after reviewing it.

Arguments: position (optional): which Backtick and which of its positions, in your own words. Leave it out to choose from a list.

Permissions: View Backticks and results, Convert a Backtick position to a bot, View bots, Create bots (always saved disabled), View bot settings. Needs Backtick Professional and any Trader plan.

Tools it uses: get_account_context, list_strategies, list_backtests, get_backtest, get_backtest_results, convert_position_to_bot, get_bot. See AI Assistant Tools: Backtick Results, Charts and Portfolio Links.

Example: "Make a bot from the best position in my 'SPX 20 delta entry sweep' Backtick, in my Schwab Individual ...4821 account, strategy group Income."

The two report workflows, Build a report and Build a portfolio by size, and the two resources an assistant can read are in Ready-Made Report Workflows and Resources.