← Back to Skills Marketplace
skinnynoizze

Sports Betting

by skinnynoizze · GitHub ↗ · v1.3.1 · MIT-0
cross-platform ⚠ suspicious
1118
Downloads
0
Stars
3
Active Installs
7
Versions
Install in OpenClaw
/install sports-betting
Description
Place and claim decentralized sports bets on-chain via Pinwin and Azuro: real-time odds, high liquidity, no custody. Fetch prematch and live games from the A...
Usage Guidance
This skill appears internally consistent and implements the expected flow for on‑chain betting. Before installing: 1) Only use a dedicated wallet/private key with limited funds — the skill will sign real transactions with BETTOR_PRIVATE_KEY. 2) Review and verify the contract addresses and API hosts (Pinwin, Azuro/onchainfeed) in the constants; mismatch could indicate tampering. 3) Be aware scripts log decoded payloads and request bodies (which may contain betting details); avoid running where logs are public. 4) Install npm deps from the official registry only and audit packages if you need higher assurance. 5) Keep the agent invocation manual (the skill already sets disable-model-invocation: true) and always confirm each transaction as instructed. If you want greater safety, require a hardware or remote-signing step (use a signer that never exposes the raw private key) or review the GitHub source and checksum before use.
Capability Analysis
Type: OpenClaw Skill Name: sports-betting Version: 1.3.1 The skill bundle provides a legitimate sports betting interface for the Polygon network using Pinwin and Azuro. While it requires a sensitive 'BETTOR_PRIVATE_KEY', the implementation follows security best practices: the key is used only for local EIP-712 signing via 'viem' and is never transmitted. The 'SKILL.md' instructions include strict safety rules requiring explicit user confirmation for every transaction, and the scripts ('place-bet.js', 'claim-bets.js') perform rigorous integrity checks on API payloads and contract addresses before signing. No evidence of data exfiltration, malicious execution, or prompt injection was found.
Capability Assessment
Purpose & Capability
The skill's name/description (Pinwin/Azuro on Polygon) match the actual code and network endpoints. Requesting a wallet private key (BETTOR_PRIVATE_KEY) and Node is expected for signing and broadcasting EIP-712 transactions. Declared constants (token, contract addresses, RPC, Pinwin/API endpoints) are directly used by the scripts.
Instruction Scope
Runtime instructions are narrow and focused: fetch games, prepare payloads, require explicit user confirmation before any signing/sending, and query subgraphs for status. The SKILL.md contains explicit safety rules (one confirmation per bet, no autonomous retries) and the skill is invocation-only (disable-model-invocation: true). Note: scripts print request/decoded payloads and other debug info to console; those logs can expose bet details and should be considered when running in a shared/logged environment.
Install Mechanism
There is no packaged installer; the skill is instruction-only but includes package.json and package-lock.json. It expects the user to run npm install (viem, @azuro-org/dictionaries, dotenv). These are public npm packages (registry.npmjs.org) — standard but carries the usual npm supply-chain risk; no obscure download URLs or extracted archives are used.
Credentials
Only one high-sensitivity env var is required: BETTOR_PRIVATE_KEY (declared as primaryEnv). That is proportional to the purpose (signing blockchain transactions). The SKILL.md recommends storing the key in a .env file under the skill workspace with chmod 600; this is reasonable but still means the agent environment will have direct access to the private key. Consider using a dedicated betting wallet with limited funds.
Persistence & Privilege
The skill is not always-enabled, does not request system-wide config changes, and is invocation-only (disable-model-invocation true). It does not modify other skills’ configs. No elevated persistence privileges are requested.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install sports-betting
  3. After installation, invoke the skill by name or use /sports-betting
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.3.1
sports-betting 1.2.3 — Major cleanup and claim script addition. - Added scripts/claim-bets.js for handling bet claim/redeem actions. - Removed legacy reference files (api.md, bets-subgraph.md, dictionaries.md, polygon.md, subgraph.md, viem.md). - Updated and clarified contract addresses for claimContract and clientCore. - Expanded documentation on secure handling of BETTOR_PRIVATE_KEY, emphasizing .env usage and security. - Improved and clarified constants, setup instructions, and best practices for user safety.
v1.2.2
sports-betting 1.2.2 - Updated Azuro data-feed source to the new REST API endpoint (`https://api.onchainfeed.org/api/v1/public/market-manager/`) for fetching games and odds. - The get-games.js script now uses the REST API, with two-step data fetching, improved main market detection, and direct human-readable titles (no more subgraph JSON parsing). - Added support for team/match search via a new `--search` option in the get-games.js script. - Clarified usage: use the bundled script for all listings; do not call the REST API directly. - @azuro-org/dictionaries is now required only for bet placement, not for listing games.
v1.0.4
**sports-betting v1.0.4** Initial code and documentation release with strict safety and invocation rules. - Added standalone betting scripts: `get-games.js`, `place-bet.js`, and `watch-bets.js` for listing games, placing bets, and monitoring bet status. - Introduced full skill documentation with strict user confirmation and transaction safety requirements. - Defined all Polygon constants (addresses, URLs, tokens) directly in documentation for reliable reference. - Required explicit user confirmation for on-chain actions; autonomous or background execution is prohibited. - Clarified invocation instructions, dependencies, and environment requirements.
v1.0.3
No functional changes in this release. - Quoted description, compatibility, and homepage, so YAML parses them consistently and colons/commas in the text won’t cause issues. - Internal documentation and flow descriptions were significantly shortened and clarified in SKILL.md for easier reference. - User-facing feature set and integration points remain unchanged. - No modifications detected in code or logic.
v1.0.2
sports-betting 1.0.2 - Clarified environment variable requirements: BETTOR_PRIVATE_KEY is now required, POLYGON_RPC_URL is optional (defaults to public endpoints if unset). - Updated compatibility and metadata to reflect these env changes. - Improved documentation for security best practices: strongly recommends using a dedicated betting wallet and warns against exposing private keys. - Changed homepage URL in metadata to point to https://github.com/skinnynoizze/pinwin-agent. - No changes to code or implementation; documentation and metadata only.
v1.0.1
**Enhanced transparency and security for bet placement and approval.** - Now always displays and explains all decoded bet payload details (amount, selections, relayer fee, etc.) to the user before any signing or approval. - Adds strict verification that the payload matches the user's requested amount and selections before signing—if there’s a mismatch, the process is stopped and the user is alerted. - Requires bet approval only up to the bet amount plus relayer fee (plus a 0.2 USDT buffer), not unlimited—improving safety. - Verifies that only the correct relayer and Polygon claim contract are used (never using values passed from external payloads) for all approvals and signing.
v1.0.0
sports-betting v1.0.0 - Initial release enabling on-chain sports betting on Polygon via Pinwin and Azuro Protocol. - Fetch prematch/live games, pick selections, place bets, and claim winnings using the Pinwin API. - Compatibility requires Node, viem, @azuro-org/dictionaries, Polygon RPC URL, and wallet private key. - Includes detailed flows for placing bets and claiming winnings, with user prompts for missing preferences. - Ensures sufficient balances before betting and provides status checks for bet resolution and redemption.
Metadata
Slug sports-betting
Version 1.3.1
License MIT-0
All-time Installs 3
Active Installs 3
Total Versions 7
Frequently Asked Questions

What is Sports Betting?

Place and claim decentralized sports bets on-chain via Pinwin and Azuro: real-time odds, high liquidity, no custody. Fetch prematch and live games from the A... It is an AI Agent Skill for Claude Code / OpenClaw, with 1118 downloads so far.

How do I install Sports Betting?

Run "/install sports-betting" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Sports Betting free?

Yes, Sports Betting is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Sports Betting support?

Sports Betting is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Sports Betting?

It is built and maintained by skinnynoizze (@skinnynoizze); the current version is v1.3.1.

💬 Comments