ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Alpaca Py Cli

v2.0.0

AI agent skill for Alpaca Markets trading. Intelligent setup wizard (alpaca init) guides users through registration. Trade stocks/crypto, manage portfolios,...

⭐ 0· 715·1 current·4 all-time
byEugene Lin@zijunl
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
medium confidence
✓
Purpose & Capability
Name/description (Alpaca trading CLI) match the declared requirements: python3 and Alpaca API credentials (ALPACA_API_KEY, ALPACA_SECRET_KEY, ALPACA_PAPER) are appropriate for this purpose.
ℹ
Instruction Scope
SKILL.md explicitly instructs running interactive commands (alpaca init / alpaca auth) that save credentials to shell startup files. That is within the skill's scope, but it is high-impact: setup will modify ~/.zshrc/ ~/.bashrc/ ~/.profile and create environment variables readable by any process in those shells. The docs correctly warn agents not to run setup autonomously and require user consent. Minor inconsistency: setup.json and README reference a scripts path (~/.openclaw/workspace/skills/.../scripts/alpaca) and suggest editing a shebang there, but no script file is present in the skill bundle — this mismatch should be clarified before proceeding.
✓
Install Mechanism
There is no install spec (instruction-only). Dependencies are Python packages (alpaca-py, pytz) installable via pip; no arbitrary remote archive downloads or unusual installers are required. Risk is limited to installing standard pip packages.
✓
Credentials
Required environment variables are exactly the Alpaca API credentials expected for a trading CLI. The skill does not request unrelated secrets. The documentation warns that these variables will be stored in shell config (reasonable for a CLI but increases exposure).
ℹ
Persistence & Privilege
Skill does not request always:true and does not ask to modify other skills or system-wide agent settings. The only persistence is writing API keys into user shell startup files (explicitly documented). This is a normal behavior for a CLI but is a lasting change and increases blast radius if agents or other processes have shell access.
Assessment
This skill appears to do what it claims (control Alpaca via a Python CLI), but it will write your API keys into shell startup files and can persist changes to your shell environment. Before installing or letting an agent run setup: 1) Decide to use paper-trading keys (recommended) and only grant minimal permissions. 2) Require explicit, manual user consent for running alpaca auth/init — do not allow autonomous agent runs that perform auth. 3) Inspect any changes the setup will make to ~/.zshrc, ~/.bashrc, or ~/.profile and consider storing keys in a secure vault or restricted file instead of exporting them globally. 4) Verify the pip packages (alpaca-py, pytz) come from the official sources. 5) Ask the skill/author to clarify the setup.json/README step that edits a script in ~/.openclaw/workspace (the bundle contains no scripts) before running automatic shebang edits. If you want a lower-risk workflow, run setup and auth manually on an isolated environment (or container) and revoke keys after testing.

Like a lobster shell, security has layers — review code before you run it.

latestvk978t5052qph55476cr9e6sb8581f9ex

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

📈 Clawdis
Binspython3
EnvALPACA_API_KEY, ALPACA_SECRET_KEY, ALPACA_PAPER

Comments