Make Bets | With your creditCard

The declared purpose (agent shopping with owner-approved, guardrailed wallets) aligns with the single required credential (CREDITCLAW_API_KEY) and the API endpoints (creditclaw.com/api/v1). However the registry name provided by the submitter ('Make Bets | With your creditCard') does not match the internal skill name (creditclaw-amazon) and the skill content explicitly disallows gambling in its spending policy — this naming mismatch is suspicious and unexplained. The skill's docs also assume the ability to write files under the user's home (e.g., ~/.creditclaw/skills and .creditclaw/cards) and to run node decrypt.js, but the manifest declares no required binaries/config-paths; that's an inconsistency.

Instructions tell the agent to download skill files and to save owner-provided encrypted card files to disk and then execute a decrypt script (node decrypt.js) delivered inside that file. They explicitly recommend spawning ephemeral sub-agents to run decrypt and checkout steps, but also include a fallback that allows the main agent to run the decrypt step if sub-agent capabilities aren't available. That means the skill directs the agent to fetch external content, persist files to the home directory, and execute code delivered at runtime — actions that significantly expand the agent's scope and create opportunities for code execution or data exposure if the runtime is not properly sandboxed.

There is no formal install spec (lowest install risk). However the runtime instructions encourage using curl to fetch and save remote files from creditclaw.com into local ~/.creditclaw directories. The URLs are all on the same domain as the API, which is expected, but writing and executing content fetched at runtime (especially the decrypt script embedded in owner-delivered files) increases the attack surface even without a packaged installer.

Only one required environment variable is declared (CREDITCLAW_API_KEY), which is appropriate for an API-based payment integration. That credential is necessary and proportional. Minor inconsistency: the manifest lists no required config paths, yet the instructions tell the agent to save files to ~/.creditclaw and .creditclaw/cards — so the skill expects filesystem access that isn't reflected in the metadata. Also the registry name hinting at gambling is inconsistent with the spending.md which explicitly blocks gambling.

The skill is not always-enabled and does not request elevated platform privileges. It does instruct saving files to user home and the workflow relies on ephemeral sub-agents, but it does not claim the ability to change other skills or system settings. The risk here stems from writing/executing runtime-delivered content rather than from elevated declared privileges.