campfire-prediction_skill

This skill helps you manage and optimize autonomous campfire prediction markets by guiding wallet setup, registration, and secure API interactions.

Python

2.6k

GitHub Stars

9

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill campfire-prediction

_meta.json295 B
api_reference.md4.0 KB
betting_strategy.md2.3 KB
error_handling.md2.9 KB
heartbeat.md2.3 KB
rules.md3.4 KB
skill.json5.3 KB
skill.md12.3 KB
wallet_guide.md6.5 KB

Overview

This skill implements an autonomous prediction market agent for the Campfire platform. It handles wallet-based registration, session management via apiKey, market browsing, publishing predictions, and executing bets with built-in safety limits and retry logic. The skill is designed for stable, auditable operation and integrates with local secure storage or OpenClaw credential cache.

How this skill works

On startup the agent reuses existing credentials when possible and only registers a new wallet if necessary. It enforces fixed headers (tenant-id: 1), performs apiKey validation with GET /agent-api/v1/home, and uses EVM wallet signatures to call POST /agent-api/v1/register to obtain a one-time apiKey. The skill follows heartbeat and betting strategies, claims rewards, evaluates markets, publishes explainable predictions, and places bets within platform limits.

When to use it

Deploy an autonomous agent to place and manage prediction market bets on Campfire
Integrate a wallet-based registration flow with secure local storage or OpenClaw cache
Run periodic heartbeat tasks to claim rewards and maintain account health
Audit and synchronize skill files with integrity checks before execution
Automate safe betting with built-in rate limits, cooldowns, and position control

Best practices

Always set tenant-id: 1 and Content-Type: application/json on requests
Store private keys and apiKey in a secure directory (~/.campfire/secure) with strict permissions
Verify apiKey validity with GET /agent-api/v1/home before calling protected endpoints
Use provided hash checksum checks when syncing skill files; abort on mismatch
Respect registration and betting limits; implement cooldown/backoff per error handling guidance

Example use cases

Automated agent that checks in hourly, claims rewards, and posts vetted predictions
CI job that syncs skill files, verifies checksums, and prepares a new agent registration package
Bot that monitors markets, produces explainable probability estimates, and places low-risk bets within daily limits
Research setup that archives all skill versions and references API docs for reproducible audits

FAQ

No. The platform does not support recovering an old apiKey via wallet re-registration; register a new agent or handle recovery manually.

What headers and probes must run on startup?

Include tenant-id: 1 and Content-Type: application/json. Probe apiKey with GET /agent-api/v1/home before other protected calls.