Alpha Vantage

v1.0.2

Alpha Vantage integration. Manage data, records, and automate workflows. Use when the user wants to interact with Alpha Vantage data.

0· 97·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill advertises Alpha Vantage integration and all runtime instructions describe using the Membrane CLI to connect, list actions, run actions, and proxy requests to Alpha Vantage — which is coherent with the stated purpose.
Instruction Scope
SKILL.md confines execution to using the Membrane CLI and browser-based auth flows. It does not instruct reading local files, environment variables, or system-wide config outside the Membrane workflow. It does, however, route API calls through Membrane's proxy (explicitly stated), so data and credentials will transit Membrane's service.
Install Mechanism
The skill is instruction-only (no install spec) but tells users to run `npm install -g @membranehq/cli`. Installing a global npm package is standard but does write binaries to disk and runs third-party code from the npm registry; this is an expected dependency for the described workflow but carries the usual supply-chain considerations.
Credentials
The skill declares no required environment variables or primary credential. It relies on Membrane to manage Alpha Vantage credentials via the CLI/browser auth flow, which is proportionate to the purpose. Users should note that credentials are managed/stored by Membrane (not by this skill).
Persistence & Privilege
The skill has no always:true flag and does not request persistent system-wide privileges. It instructs users to install a CLI tool and to create connections via Membrane, but does not modify other skills or agent-wide configuration beyond standard connector setup.
Assessment
This skill is coherent: it uses the Membrane CLI to access Alpha Vantage and does not ask for unrelated credentials. Before installing, verify the @membranehq/cli package and the getmembrane.com / GitHub repository to ensure they are the official projects you trust. Be aware that API requests and credentials will be proxied/managed by Membrane — if your data is sensitive, confirm Membrane's privacy/security practices and consider using an isolated environment for installing global npm packages. If you prefer not to install a global CLI, you can run the CLI from a container or local npm project instead.

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

latestvk975cbd7hab8jq5k3n1tktff0s842gq6

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments