From amaltash
Use when the user wants to do anything on their Amaltash trading account from Claude — sign in / authenticate, create or fine-tune a trading strategy from an idea, run a backtest, deploy or undeploy a strategy, provision a paper account, finish KYC, connect a bank, or deposit / withdraw / check balance. Triggers on "Amaltash", "my trading account", "backtest my strategy", "deploy this strategy", "fund my account", "connect my bank", "paper trading account".
How this skill is triggered — by the user, by Claude, or both
Slash command
/amaltash:amaltash-tradingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This plugin exposes the Amaltash account through the hosted `amaltash` MCP
This plugin exposes the Amaltash account through the hosted amaltash MCP
server (mcp.amaltash.com). Authentication is OAuth, handled by the MCP client:
the user runs /mcp → amaltash → Authenticate and approves once in the
browser; Claude stores and refreshes the access token. (Headless/CI setups
instead send a personal amat_… token as a Bearer header — see the README.)
connection_status to see what's set up (live/paper account, KYC, banks)./mcp, pick amaltash, and
choose Authenticate, then approve in the browser. Do NOT attempt a
headless login yourself.| Goal | Tool |
|---|---|
| Confirm the connection works | authenticate (validates the current OAuth/Bearer credential) |
| Who am I / profile | get_account_info |
| Find strategies | search_marketplace |
| Create a strategy from an idea | create_strategy (streams token usage → strategy_id) |
| Improve a strategy | fine_tune_strategy (revise → draft → backtest → activate) |
| Backtest | backtest_strategy (streams; returns metrics + equity_curve) |
| Deploy with capital | deploy_strategy (respects the platform minimum) |
| Stop a deployment | undeploy_strategy |
| Get a $25K paper account | provision_paper_account (streams provision → fund) |
| Where am I in onboarding | connection_status |
| Links to finish KYC / connect bank / connect exchange | connect_links |
| Brokerage status | get_brokerage_status |
| Balance | get_account_balance |
| Balance + why cash isn't all withdrawable | balance_detail |
| Connected banks | list_banks |
| Add money | deposit_funds (ACH if a bank is linked, else a Plaid connect link, or method="wire") |
| Take money out | withdraw_funds (needs confirm=true) |
connect_links
and give the user the relevant URL to finish in their signed-in browser.withdraw_funds with
confirm=true (or deploy_strategy live) until the user has explicitly
approved the amount. Default to paper (paper_trade=true) when unsure.create_strategy, fine_tune_strategy,
backtest_strategy, provision_paper_account) emit progress as they run —
relay it. backtest_strategy returns a downsampled equity_curve
([{t, v}]) you can render or summarize.get_account_balance / deposit_funds will say so;
guide the user to provision_paper_account (sandbox) or connect_links (live).create_strategy makes one strategy and returns its strategy_id. When it
succeeds, STOP and hand control back to the user. Do not automatically
fine-tune, optimize, or chain into another create — that's the user's call.
Briefly report what was created and offer the next steps as options, e.g.:
backtest_strategy (suggest a window if they didn't
give one).fine_tune_strategy revises a strategy's code from a plain-English instruction,
then drafts → backtests → activates it. Never call it on your own initiative
— only when the user has explicitly asked to change or fix the strategy.
create_strategy,
backtest_strategy, or deploy_strategy fails because the strategy code
itself errored (a compile/runtime/execution bug in the generated code), tell
the user what broke and offer to fix it via fine_tune_strategy (with the
error text as the instruction, e.g. "Fix this execution error: ").
Run it only once they say yes; if they accept and it still errors after
two attempts, stop and show the error rather than looping.
fine_tune_strategy.fine_tune_strategy with it. Always re-backtest and
compare metrics (CAGR, Sharpe, max drawdown) against the prior version so
the user can see whether it actually improved.Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub arpwal/amaltash-mcp-plugin --plugin amaltash