Agent skill

Alpaca Broker Trading Orders

Place and manage orders on behalf of accounts via the Alpaca Broker API — order creation (qty vs notional, fractional shares, order types/TIF/classes), order status lifecycle, replace/cancel…

Apache-2.0Auto-check passedBusiness, Finance & HR

Install Alpaca Broker Trading Orders

skills CLI

$ npx skills add alpacahq/alpaca-skills --skill alpaca-broker-trading-orders -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install alpacahq/alpaca-skills alpaca-broker-trading-orders --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/alpacahq/alpaca-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/broker-api/trading-orders .claude/skills/alpaca-broker-trading-orders && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "alpaca-broker-trading-orders" agent skill from https://github.com/alpacahq/alpaca-skills/tree/main/skills/broker-api/trading-orders into .claude/skills/alpaca-broker-trading-orders/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alpaca-broker-trading-orders", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/alpacahq/alpaca-skills/tree/main/skills/broker-api/trading-orders

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add alpacahq/alpaca-skills --skill alpaca-broker-trading-orders -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install alpacahq/alpaca-skills alpaca-broker-trading-orders --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alpacahq/alpaca-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/broker-api/trading-orders .agents/skills/alpaca-broker-trading-orders && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "alpaca-broker-trading-orders" agent skill from https://github.com/alpacahq/alpaca-skills/tree/main/skills/broker-api/trading-orders into .agents/skills/alpaca-broker-trading-orders/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alpaca-broker-trading-orders", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add alpacahq/alpaca-skills --skill alpaca-broker-trading-orders -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install alpacahq/alpaca-skills alpaca-broker-trading-orders --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alpacahq/alpaca-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/broker-api/trading-orders .cursor/skills/alpaca-broker-trading-orders && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "alpaca-broker-trading-orders" agent skill from https://github.com/alpacahq/alpaca-skills/tree/main/skills/broker-api/trading-orders into .cursor/skills/alpaca-broker-trading-orders/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alpaca-broker-trading-orders", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/alpacahq/alpaca-skills.git --path skills/broker-api/trading-orders

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add alpacahq/alpaca-skills --skill alpaca-broker-trading-orders -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install alpacahq/alpaca-skills alpaca-broker-trading-orders --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alpacahq/alpaca-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/broker-api/trading-orders .gemini/skills/alpaca-broker-trading-orders && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "alpaca-broker-trading-orders" agent skill from https://github.com/alpacahq/alpaca-skills/tree/main/skills/broker-api/trading-orders into .gemini/skills/alpaca-broker-trading-orders/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alpaca-broker-trading-orders", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install alpacahq/alpaca-skills alpaca-broker-trading-orders

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add alpacahq/alpaca-skills --skill alpaca-broker-trading-orders -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/alpacahq/alpaca-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/broker-api/trading-orders .github/skills/alpaca-broker-trading-orders && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "alpaca-broker-trading-orders" agent skill from https://github.com/alpacahq/alpaca-skills/tree/main/skills/broker-api/trading-orders into .github/skills/alpaca-broker-trading-orders/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alpaca-broker-trading-orders", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add alpacahq/alpaca-skills --skill alpaca-broker-trading-orders -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install alpacahq/alpaca-skills alpaca-broker-trading-orders --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alpacahq/alpaca-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/broker-api/trading-orders .opencode/skills/alpaca-broker-trading-orders && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "alpaca-broker-trading-orders" agent skill from https://github.com/alpacahq/alpaca-skills/tree/main/skills/broker-api/trading-orders into .opencode/skills/alpaca-broker-trading-orders/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alpaca-broker-trading-orders", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: alpaca-broker-trading-orders
GitHub stars: 154
Token cost: ~2.3k tokens
SKILL.md length: 937 words
Files: 2
Skills in repo: 14
Repo updated: Sep 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Place and manage orders on behalf of accounts via the Alpaca Broker API — order creation (qty vs notional, fractional shares, order types/TIF/classes), order status lifecycle, replace/cancel…

Works in 7 steps: Endpoints → Create-order request → Fractional / notional rules → …
Building trading
SKILL.md covers Reference, 1. Endpoints, 2. Create-order request and 3. Fractional / notional rules, plus 4 more sections
Reaches docs.alpaca.markets

What it does

Alpaca Broker Trading Orders is an agent skill from alpacahq/alpaca-skills. Place and manage orders on behalf of accounts via the Alpaca Broker API — order creation (qty vs notional, fractional shares, order types/TIF/classes), order status lifecycle, replace/cancel, positions, and trading-account buying power. Use when building trading, recurring-invest, or portfolio flows on Alpaca in any language.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).

It sits in Business, Finance & HR, covering Trading and backtesting. The repository describes itself as: Agent skills for Alpaca's Trading API and Broker API: drop-in SKILL.md files for AI coding assistants. The licence is Apache-2.0.

When your agent uses it

Building trading
Recurring-invest
Portfolio flows on Alpaca in any language

Example prompts

“/alpaca-broker-trading-orders”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

Endpoints
Create-order request
Fractional / notional rules
Order status lifecycle
Positions & trading account
Documented gotchas
Idempotency & recurring-invest lessons

What it can do on your machine

Read from SKILL.md and the folder at commit 39111ab. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- docs.alpaca.markets
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Alpaca Broker Trading Orders loads about 2.3k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 937 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~89
When it runs · the whole SKILL.md, loaded when a task matches: ~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from alpacahq/alpaca-skills at commit 39111ab, republished under its Apache-2.0 licence (© alpacahq). 937 words, ~2,342 tokens.

Download SKILL.mdSave it as .claude/skills/alpaca-broker-trading-orders/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: alpaca-broker-trading-orders
description: Place and manage orders on behalf of accounts via the Alpaca Broker API — order creation (qty vs notional, fractional shares, order types/TIF/classes), order status lifecycle, replace/cancel, positions, and trading-account buying power. Use when building trading, recurring-invest, or portfolio flows on Alpaca in any language.

Alpaca Broker API — Trading on Behalf of Accounts

Place, modify, cancel, and track orders for an end-user account, and read positions & buying power. The defining feature of Broker API trading: account_id is in the path — you act for a user account, not your own.

Read alpaca-broker-integration first. Broker API + HTTP Basic auth. (The standalone Trading API uses /v2/orders with no account in the path; everything else here transfers.)

Reference

Guides: https://docs.alpaca.markets/docs/orders-at-alpaca, https://docs.alpaca.markets/docs/fractional-trading
API ref: https://docs.alpaca.markets/reference/postorder
Live schema: alpaca-docs MCP → get-endpoint title "Broker API" path /v1/trading/accounts/{account_id}/orders

1. Endpoints

Method	Path	Purpose
POST	`/v1/trading/accounts/{id}/orders`	Create order
GET	`/v1/trading/accounts/{id}/orders`	List orders (filter by `status`, `symbols`, `after`…)
GET	`/v1/trading/accounts/{id}/orders/{order_id}`	Get order by ID
GET	`/v1/trading/accounts/{id}/orders:by_client_order_id?client_order_id=…`	Get by your client ID
PATCH	`/v1/trading/accounts/{id}/orders/{order_id}`	Replace (modify) order
DELETE	`/v1/trading/accounts/{id}/orders/{order_id}`	Cancel one order (204)
DELETE	`/v1/trading/accounts/{id}/orders`	Cancel all (207 Multi-Status)
POST	`/v1/trading/accounts/{id}/orders/estimation`	Cost-estimate an order
GET / DELETE	`/v1/trading/accounts/{id}/positions[/{symbol_or_asset_id}]`	List / close positions
GET	`/v1/trading/accounts/{id}/account`	Trading-account details (buying power etc.)

2. Create-order request

Schema-required: type and time_in_force. Conditionally required: symbol, side, and exactly one of qty/notional.

json

// notional market buy (dollar-based, fractional)
{ "symbol": "AAPL", "notional": "25.00", "side": "buy", "type": "market", "time_in_force": "day",
  "client_order_id": "your-own-uuid" }

// limit qty sell
{ "symbol": "AAPL", "qty": "3", "side": "sell", "type": "limit", "limit_price": "190.00", "time_in_force": "gtc" }

Field	Values / notes
`symbol`	required (except `mleg` multi-leg options)
`qty`	decimal string, up to 9 dp. Fractional only for `market`+`day`
`notional`	decimal string, up to 9 dp. Mutually exclusive with `qty`
`side`	`buy`, `sell` (plus advanced: `sell_short`, …)
`type`	`market`, `limit`, `stop`, `stop_limit`, `trailing_stop`
`time_in_force`	`day`, `gtc`, `opg`, `cls`, `ioc`, `fok`
`limit_price` / `stop_price`	required for limit/stop variants
`trail_price` / `trail_percent`	one required for `trailing_stop`
`extended_hours`	bool; only with `type=limit` and TIF `day`/`gtc`
`client_order_id`	≤128 chars; your idempotency key (auto-generated if omitted)
`order_class`	`simple` (default), `bracket`, `oco`, `oto`, `mleg`
`take_profit` / `stop_loss`	`{limit_price}` / `{stop_price, limit_price?}` for bracket/oco/oto
`position_intent`	`buy_to_open`, `sell_to_close`, …

qty XOR notional (verbatim rule): pass one or the other — supplying both → 400. In the response, whichever you didn't use comes back null.

3. Fractional / notional rules

On by default for all accounts (live + paper).
Asset must have fractionable: true (check the Assets API — see alpaca-broker-market-data), else requested asset is not fractionable.
TIF must be day for fractional/notional.
Notional is limited to market and limit (day); only limit for extended hours. Fractional qty additionally allows stop/stop_limit per the guide.
No shorting fractional — all fractional sells are marked long.
Precision: up to 9 decimal places for both qty and notional.

4. Order status lifecycle

OrderStatus (the order object's status): new, partially_filled, filled, done_for_day, canceled, expired, replaced, pending_cancel, pending_replace, accepted, pending_new, accepted_for_bidding, stopped, rejected, suspended, calculated.

Order status ≠ trade-event event. The order object's status is the enum above. The SSE trade-update stream reports a richer event enum that adds operational events not present as a status — including held (multi-leg secondary legs awaiting trigger), trade_bust, trade_correct, restated, order_cancel_rejected, order_replace_rejected. So held exists as a trade event but never as an order status. See alpaca-broker-sse-events.

Terminal: filled, canceled, expired, rejected (and replaced for the original order). Everything else is in-flight.

Early-state distinctions (these trip people up):

accepted — received by Alpaca, not yet routed to a venue (common outside market hours).
new — received and routed to exchanges; the usual initial live state.
pending_new — routed but not yet accepted for execution (rare).

So the typical opening sequence is accepted → pending_new → new, then fills. Lesson: treat new/accepted/pending_new as "exists but not done." Persist the order on submit, then update on fill/cancel/reject events — don't block the user waiting for a terminal state synchronously.

Show full SKILL.md (399 more words)Show less

5. Positions & trading account

Position key fields: symbol, asset_id, qty, qty_available (free of open orders), side (long/short), avg_entry_price, market_value, cost_basis, unrealized_pl, unrealized_plpc, current_price, change_today.

TradeAccount key fields:

buying_power (with margin multiplier 1–4), cash, cash_withdrawable, equity, last_equity.
Blockers: trading_blocked, account_blocked, transfers_blocked, trade_suspended_by_user.
multiplier, regt_buying_power, non_marginable_buying_power, long_market_value, initial_margin, maintenance_margin, sma.

Lesson — check buying power before notional orders. For a "spend $X" UX, read buying_power/cash first and reject/notify on insufficient funds, rather than letting Alpaca reject the order. (Cache it per account within a batch run to avoid re-fetching.)

PDT/day-trade fields are deprecated (since 2026-04-27, sunset 2026-07-06) following FINRA's intraday-margin rule change: daytrade_count, pattern_day_trader, daytrading_buying_power, bod_dtbp, plus config dtbp_check/pdt_check. They still exist in the schema today but stop relying on them.

6. Documented gotchas

Wash-trade rejection (403): if a user's two orders could self-cross (opposite sides, crossable prices), Alpaca rejects. Opposing market/stop pairs are always rejected; opposing limits rejected when buy-limit ≥ sell-limit. Use bracket/oco/trailing_stop for simultaneous take-profit + stop-loss — they're exempt.
Bracket constraints: requires both take_profit.limit_price and stop_loss.stop_price; TP must be above SL for a buy; no extended hours; TIF day/gtc; child legs activate only after the entry fully fills; canceling one cancels the group.
Notional orders can't be replaced — cancel and resubmit (IPO-class notional is the exception). Fractional qty can't be changed on replace ("full shares only").
Replace ≠ guaranteed: a 200 from PATCH can still be rejected if the original fills first; watch the trade-updates stream. Can't replace while accepted/pending_new/pending_cancel/pending_replace.
Cancel semantics: single cancel → 204, or 422 if no longer cancelable; cancel-all → 207 per-order results; close-all positions → 207. Close-single accepts mutually-exclusive qty or percentage.

7. Idempotency & recurring-invest lessons

Always set client_order_id from your own transaction record. It's your dedup key and lets you look the order up (orders:by_client_order_id) if the create response is lost. Note it dedups lookup, not necessarily replay — combine it with a local "already-submitted?" guard.
Recurring/scheduled buys (lesson): the robust pattern is — fetch pending invest instructions from your DB → check buying power → place a notional market/day order per instruction → record the returned order → mark the instruction done only after a successful create. On insufficient funds, cancel the instruction and notify, don't silently skip. Schedule the batch shortly before market open and respect the market clock (alpaca-broker-market-data).
Track fills via the trade events SSE stream, not by polling each order — see alpaca-broker-sse-events.

Related skills: prices/assets/clock → alpaca-broker-market-data; fills in real time → alpaca-broker-sse-events; rate limits on bulk placement → alpaca-broker-rate-limits-resilience; money formatting → alpaca-broker-money-precision.

Files

SKILL.md and 1 other file in skills/broker-api/trading-orders of alpacahq/alpaca-skills.

SKILL.md
reference.md

Open the folder on GitHubat commit 39111ab

Compare with similar skills

Alpaca Broker Trading Orders next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Alpaca Broker Trading Orders compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Alpaca Broker Trading Orders this skillalpacahq/alpaca-skills	154	—	~2.3k	Automated safety check: Pass	Apache-2.0	1 mo ago
Tushare Datazillionare/zillionare	322	2 repos	~2.3k	Automated safety check: Pass	None	today
Tradingview MCPatilaahmettaner/tradingview-mcp	5k	—	~1.3k	Automated safety check: Pass	MIT	yesterday
Digital Oraclekomako-workshop/digital-oracle	878	—	~5.9k	Automated safety check: Pass	MIT	2 mo ago
Polyclawchainstacklabs/polyclaw	359	1 repos	~2k	Automated safety check: Pass	Apache-2.0	5 mo ago
Markdownfacioquo/stock-indicators-dotnet	1.2k	—	~812	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Tushare Data
zillionare/zillionare
面向中文自然语言的 Tushare 数据研究技能。用于把“看看这只股票最近怎么样”“帮我查财报趋势”“最近哪个板块最强”“北向资金在买什么”“给我导出一份行情数据”这类请求，转成可执行的数据获取、清洗、对比、筛选、导出与简要分析流程。适用于 A 股、指数、ETF/基金、财务、估值、资金流、公告新闻、板块概念与宏观数据等研究场景。
322 GitHub starsUsed in 2 repos~2.3k tokens
Business, Finance & HRAuto-check passed
Tradingview MCP
atilaahmettaner/tradingview-mcp
AI Trading Intelligence — live prices, 30+ technical indicators, backtesting (6 strategies), walk-forward overfitting detection, trade logs, equity curves, licensed news sentiment (Marketaux), and…
5k GitHub stars~1.3k tokensUpdated yesterday
Business, Finance & HRAuto-check passed
Digital Oracle
komako-workshop/digital-oracle
Answer prediction questions using market trading data, not opinions.
878 GitHub stars~5.9k tokensUpdated 2 mo ago
Business, Finance & HRAuto-check passed
Polyclaw
chainstacklabs/polyclaw
Trade on Polymarket via split + CLOB execution. An agent skill from chainstacklabs/polyclaw.
359 GitHub starsUsed in 1 repo~2k tokens
Business, Finance & HRAuto-check passed
Markdown
facioquo/stock-indicators-dotnet
Format and lint Markdown in this repository against GitHub Flavored Markdown and its markdownlint-cli2 configuration — headers, lists, code fences, callouts (VitePress containers on docs-site pages…
1.2k GitHub stars~812 tokensUpdated yesterday
Business, Finance & HRAuto-check passed
Openmobius Skill
MobiusQuant/OpenMobius-skill
Provides multi-school trading Q&A, chart/OHLCV analysis, annotation, and fresh-market workflows covering ICT/SMC, ChanLun, Wyckoff, Price Action, Order Flow, VSA, and Elliott Wave.
697 GitHub stars~7.2k tokensUpdated 1 mo ago
Business, Finance & HRAuto-check passed

More from alpacahq/alpaca-skills

All 14 skills in this repo

Alpaca Broker Account Onboarding
alpacahq/alpaca-skills
Open and manage brokerage accounts via the Alpaca Broker API — account creation, KYC/CIP, identity & disclosures, agreements, document upload (incl.
154 GitHub stars~2.3k tokensUpdated 1 mo ago
Auto-check passed
Alpaca Broker Funding Transfers
alpacahq/alpaca-skills
Move money between an Alpaca brokerage account and the EXTERNAL banking world via the Broker API — ACH relationships, wire recipient banks, classic transfers (deposits/withdrawals), the v1beta…
154 GitHub stars~2.4k tokensUpdated 1 mo ago
Auto-check passed
Alpaca Broker Integration
alpacahq/alpaca-skills
Entry point for integrating with the Alpaca Broker API (plus Market Data and Trading APIs) in any programming language.
154 GitHub stars~3k tokensUpdated 1 mo ago
Auto-check passed
Alpaca Broker Journals
alpacahq/alpaca-skills
Move cash (JNLC) and securities (JNLS) BETWEEN accounts inside your own Alpaca omnibus via the Broker API — single, batch, and reverse-batch journals, the Idempotency-Key header, journal status…
154 GitHub stars~2.1k tokensUpdated 1 mo ago
Auto-check passed
Alpaca Broker Money Precision
alpacahq/alpaca-skills
Handle money and numeric precision correctly with the Alpaca API — numbers-as-strings on the wire, decimals vs floats, rounding/truncation before sending amounts, fractional-share precision, and…
154 GitHub stars~1.2k tokensUpdated 1 mo ago
Auto-check passed
Alpaca Broker Rate Limits Resilience
alpacahq/alpaca-skills
Make Alpaca API clients resilient — rate-limit header handling, HTTP 429 backoff, exponential retry, bounded concurrency/worker pools, pagination loops, batch sizing, and timeouts.
154 GitHub stars~1.4k tokensUpdated 1 mo ago
Auto-check passed

Questions about Alpaca Broker Trading Orders

What does Alpaca Broker Trading Orders do?

Place and manage orders on behalf of accounts via the Alpaca Broker API — order creation (qty vs notional, fractional shares, order types/TIF/classes), order status lifecycle, replace/cancel…. Alpaca Broker Trading Orders is an agent skill from alpacahq/alpaca-skills. Place and manage orders on behalf of accounts via the Alpaca Broker API — order creation (qty vs notional, fractional shares, order types/TIF/classes), order status lifecycle, replace/cancel, positions, and trading-account buying power.

When should I use Alpaca Broker Trading Orders?

Alpaca Broker Trading Orders fits situations like: building trading; recurring-invest; portfolio flows on Alpaca in any language.

How do I install Alpaca Broker Trading Orders in Claude Code?

Run `npx skills add alpacahq/alpaca-skills --skill alpaca-broker-trading-orders -a claude-code`. Or copy the skill folder (skills/broker-api/trading-orders in alpacahq/alpaca-skills) into .claude/skills/alpaca-broker-trading-orders in your project. Claude Code loads it when a task matches its description.

How do I install Alpaca Broker Trading Orders in Codex?

Run `npx skills add alpacahq/alpaca-skills --skill alpaca-broker-trading-orders -a codex`. Or copy the skill folder (skills/broker-api/trading-orders in alpacahq/alpaca-skills) into .agents/skills/alpaca-broker-trading-orders in your project. Codex loads it when a task matches its description.

Can I use Alpaca Broker Trading Orders in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alpacahq/alpaca-skills --skill alpaca-broker-trading-orders -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/alpaca-broker-trading-orders, .gemini/skills/alpaca-broker-trading-orders, .github/skills/alpaca-broker-trading-orders and .opencode/skills/alpaca-broker-trading-orders in your project.

What does Alpaca Broker Trading Orders need to run?

SKILL.md names no scripts, command-line tools or credentials: Alpaca Broker Trading Orders is instructions for the agent only.

Does Alpaca Broker Trading Orders access the network?

SKILL.md names 1 domain. In commands or code: docs.alpaca.markets; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Alpaca Broker Trading Orders safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Alpaca Broker Trading Orders use?

Alpaca Broker Trading Orders is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Alpaca Broker Trading Orders use?

About 2.3k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Alpaca Broker Trading Orders?

Skills that share tags, products or a category with Alpaca Broker Trading Orders: Tushare Data (zillionare/zillionare, 322 stars), Tradingview MCP (atilaahmettaner/tradingview-mcp, 5k stars), Digital Oracle (komako-workshop/digital-oracle, 878 stars) and Polyclaw (chainstacklabs/polyclaw, 359 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Alpaca Broker Trading Orders?

alpacahq (a GitHub organization) maintains it in alpacahq/alpaca-skills, which has 154 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 8, 2026.

Source: alpacahq/alpaca-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Alpaca Broker Trading Orders

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Alpaca Broker API — Trading on Behalf of Accounts

Reference

1. Endpoints

2. Create-order request

3. Fractional / notional rules

4. Order status lifecycle

5. Positions & trading account

6. Documented gotchas

7. Idempotency & recurring-invest lessons

Files

Compare with similar skills

Similar skills

More from alpacahq/alpaca-skills

Related

Questions about Alpaca Broker Trading Orders