v1.0.1

Alpaca Markets CLI

ReviewClawScan verdict for this skill. Analyzed May 1, 2026, 6:10 AM.

Analysis

This Alpaca integration matches its stated purpose, but it can place or cancel trades and close positions using brokerage API keys, so it needs careful review before use.

GuidanceInstall or use this skill only if you are comfortable granting an agent access to an Alpaca account. Start with paper trading keys, leave ALPACA_BASE_URL unset unless you intentionally need another environment, and require manual review before any live order, cancellation, or position-closing action.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Abnormal behavior control

Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.

Tool Misuse and Exploitation

SeverityHighConfidenceHighStatusConcern

scripts/alpaca_api.py

parser.add_argument("method" ...); parser.add_argument("endpoint" ...); allowed_methods = {"GET", "POST", "PUT", "PATCH", "DELETE"}; response = requests.request(...)

The helper exposes a generic authenticated API caller with mutating methods and caller-supplied endpoints/data. For a brokerage API, POST/PATCH/DELETE can place, alter, cancel, or close financial positions without any code-level confirmation or limits.

User impactIf used with live Alpaca credentials, an agent or mistaken command could execute real trades, cancel orders, or close positions.

RecommendationUse paper trading keys by default, require explicit human approval before any POST/PATCH/DELETE call, and consider adding endpoint allowlists, dry-run mode, trade-size limits, and live-trading confirmations.

Agentic Supply Chain Vulnerabilities

SeverityLowConfidenceHighStatusNote

requirements.txt

requests>=2.31.0

The dependency is purpose-aligned for HTTP API calls, but it is not pinned to an exact version, so future installs may resolve to newer package versions.

User impactA future dependency version could behave differently from the version originally tested.

RecommendationInstall in a controlled environment and consider pinning dependencies or using a lockfile when evaluating or deploying the skill.

Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse

SeverityMediumConfidenceHighStatusNote

scripts/alpaca_api.py

"APCA-API-KEY-ID": api_key, "APCA-API-SECRET-KEY": api_secret

The script uses Alpaca API credentials as expected for the integration. These credentials can access account data and, if live trading is enabled, can authorize real brokerage actions.

User impactSupplying live credentials gives the skill access to sensitive account information and trading authority.

RecommendationPrefer paper trading credentials, keep live keys separate, restrict or revoke keys when not needed, and avoid setting ALPACA_BASE_URL to the live endpoint unless you intentionally want live trading.