ClawFi
Analysis
ClawFi is a coherent market-data API skill, but users should know it can create bot credentials and publish market observations or signals when asked.
Findings (4)
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.
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.
Only call observe, signal, source, or knowledge/block when the user has explicitly asked to submit or publish data to ClawFi
The skill exposes write endpoints for market observations, signals, sources, and knowledge. This is purpose-aligned, but publishing financial-market content should remain user-directed.
npx clawfi@latest install clawfi
The README recommends a user-run npm installer using the moving `@latest` tag and says it writes the skill into several agent skill directories. This is a disclosed installation path, but users should verify the package source before running it.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
The response returns `botId` and `apiKey` once; store them and send as `x-bot-id` and `x-api-key` on every request.
The skill uses service credentials for a bot identity. This is disclosed and expected for API access, but it is still account-like authority that should be stored carefully.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Submit a market observation... Submit a directional signal... Write a structured wiki-style block for a symbol.
The skill can add persistent market observations, signals, and knowledge blocks that may later be read as context. This is the core purpose, but inaccurate or low-quality submissions could influence future research.
