The Odds Api
v1.0.0The Odds API integration. Manage data, records, and automate workflows. Use when the user wants to interact with The Odds API data.
⭐ 0· 99·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
OpenClaw
Benign
high confidencePurpose & Capability
Name and description indicate The Odds API integration and all instructions request only the Membrane CLI and a Membrane account to proxy and run actions against The Odds API — these are appropriate and proportional to the declared purpose.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests. It does not ask the agent to read unrelated files, access unrelated environment variables, or transmit data to unexpected endpoints. It explicitly recommends not asking for API keys.
Install Mechanism
There is no automatic install spec in the registry (instruction-only). The skill tells users to run `npm install -g @membranehq/cli` (or use npx in examples). Installing an npm CLI is a reasonable requirement, but installing global npm packages runs third-party code — verify the package/publisher or prefer `npx` or a local install if you want less system-wide change.
Credentials
The skill declares no required environment variables or credentials and relies on Membrane to manage authentication. This is proportionate to its purpose. Note that using Membrane means the service (Membrane) will handle and store credentials on the user's behalf.
Persistence & Privilege
The skill does not request persistent or always-on privileges, and is user-invocable only. It does not modify other skills or agent-wide settings.
Assessment
This skill appears coherent and limited to using the Membrane CLI to access The Odds API. Before installing or running the CLI: 1) verify the @membranehq/cli package and publisher (or use `npx` to avoid a global install); 2) understand that Membrane will proxy requests and manage credentials server-side — review their privacy/security policies to know what request/response data is transmitted and stored; 3) be aware the CLI login opens a browser for auth (or uses a headless flow); and 4) if you want tighter control, avoid global installs and prefer ephemeral/local CLI runs. If you need confirmation about what Membrane stores or how long credentials are kept, check Membrane's documentation or support before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk975t6vr9xwf2qje8gjfdhtr7n84h3h1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.