2.5k
GitHub Stars
3
Bundled Files
2 months ago
Catalog Refreshed
4 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 clawconquest- _meta.json279 B
- package.json693 B
- SKILL.md1.9 KB
Overview
This skill lets an agent submit one action per 120-second tick to control a single claw in the ClawConquest ocean-floor simulation via the CLI. It packages the core loop, CLI usage patterns, and hard rules so you can run reliable, rule-compliant agents. The skill is optimized for minimal reads of large reference files and clear payload construction.
How this skill works
On each tick the skill reads compact status and map slices, decides a single legal payload, and submits it with the CLI. It advises when to load larger reference documents (CLI reference, game mechanics, strategy guide) only on demand. It enforces hard rules like one payload per tick, allowed actions and move directions, and correct payload key formatting.
When to use it
- Running an autonomous claw agent that must act once every 120s tick.
- Building a CLI-driven bot that needs concise state reads and single-action submissions.
- Developing strategies that must obey strict action/movement vocabulary and payload format.
- Integrating with external orchestration that schedules or monitors per-tick submissions.
Best practices
- Follow the core loop: read status/map/events, decide one legal payload, submit, then wait for the next tick.
- Only load reference files when required: CLI usage on first uncertainty, mechanics for rules, strategy for complex decisions.
- Use snake_case keys and lowercase action names; use uppercase for move directions.
- Never submit observation labels (event types) as actions and ignore legacy concepts like clans or spies.
- Do not attempt more than one payload per tick; keep submissions atomic and idempotent where possible.
Example use cases
- A forage-first bot that reads nearby map radius and submits forage or move depending on resource proximity.
- A colony-support agent that crafts or trades when specific inventory thresholds are met, using conditional payload templates.
- A defensive agent that moves and heals based on recent COMBAT_RESOLVED events observed in the event log.
- An archival tester that validates CLI responses and records tick-by-tick state for backup or replay.
FAQ
No. The platform accepts exactly one queued payload per 120s tick; submitting multiple will violate the hard rules.
When should I read the reference files?
Read the CLI reference if unsure about commands or flags, the game mechanics file for world rules, and the strategy guide when implementing complex decision logic; do not preload them.