← Back to Skills Marketplace
Strykr Prism
by
Next Frontier AI
· GitHub ↗
· v1.1.2
2169
Downloads
1
Stars
0
Active Installs
4
Versions
Install in OpenClaw
/install strykr-prism
Description
Real-time financial data API for AI agents. Stocks, crypto, forex, ETFs. 120+ endpoints. Alternative to Alpha Vantage, CoinGecko. Works with Claude, Cursor.
Usage Guidance
Before installing, verify the upstream service and credential handling: 1) Confirm the upstream project's homepage/repository and that the GitHub repo in skill.json actually exists and is maintained; the package currently has no authoritative homepage. 2) Ask the maintainer how PRISM_API_KEY is transmitted (Authorization header, query param, or not at all). Do not export/send secrets until you understand where they go. 3) Expect the helper script to require curl and jq; ensure those binaries are present or documented. 4) Remember this skill sends user-supplied identifiers (symbols, wallet addresses, queries) to an external third-party endpoint — only use it with non-sensitive data or when you trust the operator. 5) If you need higher assurance, request signed releases, an official domain/terms/privacy policy, or run your own audited gateway rather than relying on the railway.app endpoint. Given the mismatches in metadata and missing credential usage, proceed only after resolving these questions.
Capability Analysis
Type: OpenClaw Skill
Name: strykr-prism
Version: 1.1.2
The skill bundle is benign. All files consistently define and interact with a financial data API hosted at `https://strykr-prism.up.railway.app`. The `SKILL.md` provides clear instructions for an AI agent to use this API, and the `scripts/prism.sh` helper script exclusively uses `curl` to query this specific endpoint. There is no evidence of data exfiltration, malicious execution (e.g., `curl|bash`), persistence mechanisms, or prompt injection attempts against the agent. The skill properly requests an API key via environment variable (`PRISM_API_KEY`) as a configuration item, which is a standard and secure practice.
Capability Assessment
Purpose & Capability
The name, description, SKILL.md, and scripts all describe a market-data API and the provided endpoints align with that purpose. However, the skill metadata and repository/homepage situation is inconsistent: registry metadata lists no required env vars while skill.json declares PRISM_API_KEY as required, and the declared upstream (https://strykr-prism.up.railway.app) has no homepage or official owner linked in the package manifest. These inconsistencies reduce trust.
Instruction Scope
SKILL.md instructs the agent to send user queries, symbols, and wallet addresses to the external PRISM_URL via curl (expected for a data API). It does not instruct reading local files or unrelated system state. However, examples do not show sending an API key (Authorization header or query param), despite asking users to export PRISM_API_KEY — the mismatch is concerning because it's unclear how credentials are used or protected when requests are made.
Install Mechanism
There is no install spec (instruction-only), which is low risk in itself. But the included helper script uses curl and jq; the skill's declared required binaries list is empty, so the runtime dependency on jq/curl is undocumented. That mismatch can cause runtime failures or lead agents to try to install or invoke missing tools unexpectedly.
Credentials
skill.json marks PRISM_API_KEY as required and SKILL.md tells users to export it, but registry metadata provided earlier listed no required env vars. The runtime script never includes or demonstrates sending PRISM_API_KEY in requests (no Authorization header or query param shown). This could mean: (a) the key is actually required but the examples omit it (poor docs), (b) the key is unused (misconfigured metadata), or (c) the implementation expects the key in a non-obvious place. Any of these are suspicious because they affect how/if secrets are transmitted to the external service.
Persistence & Privilege
The skill does not request always:true, has no install spec that writes to disk beyond including a helper script, and does not ask to modify other skills or system-wide settings. It can be invoked by the model (normal behavior) but does not request elevated persistence privileges.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install strykr-prism - After installation, invoke the skill by name or use
/strykr-prism - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.2
Rebranded to OpenClaw
v1.1.1
SEO update
v1.1.0
- Updated description to highlight real-time capabilities and position PRISM as an alternative to Alpha Vantage, Polygon.io, and CoinGecko.
- Added `keywords` for discoverability, including references to AI agents, fintech, and major data competitors.
- Version bumped from 1.0.0 to 1.1.0.
- Streamlined introduction and branding in documentation for clarity and concise positioning.
- No changes to API endpoints or usage examples.
v1.0.0
Initial release: 120+ endpoints for canonical asset resolution, price lookups, token security, and cross-market intelligence
Metadata
Frequently Asked Questions
What is Strykr Prism?
Real-time financial data API for AI agents. Stocks, crypto, forex, ETFs. 120+ endpoints. Alternative to Alpha Vantage, CoinGecko. Works with Claude, Cursor. It is an AI Agent Skill for Claude Code / OpenClaw, with 2169 downloads so far.
How do I install Strykr Prism?
Run "/install strykr-prism" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Strykr Prism free?
Yes, Strykr Prism is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Strykr Prism support?
Strykr Prism is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Strykr Prism?
It is built and maintained by Next Frontier AI (@nextfrontierbuilds); the current version is v1.1.2.
More Skills