The fire skill executes a written implementation plan task-by-task with strict, disciplined verification and no unauthorized improvisation.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install fire
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install fire using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
The fire skill functions as the execution engine for an AI coding agent, acting on prepared technical recipes. Much like a kitchen line cook following an order ticket exactly as written, this skill takes a pre-defined implementation plan and processes it systematically, station by station. It ensures that no task leaves the pass unchecked and absolutely nothing is improvised on the live codebase.
Operating within the broader ecosystem of Openclaw Skills, fire enforces rigid preconditions such as working exclusively on dedicated feature branches or isolated worktrees, and establishing a green baseline before modifying code. It bridges the gap between high-level planning and concrete execution, offering both a solo execution mode and a brigade mode that orchestrates dedicated implementer subagents for complex tasks.
To utilize this execution engine within your Openclaw Skills workspace, ensure your environment is initialized and your implementation plan is generated.
Ensure you have an active plan file (typically generated via a recipe skill), then trigger execution:
# Trigger the execution engine using explicit intents
openclaw fire
# Alternative natural language triggers managed by the framework
# "execute the plan"
# "build it"
Ensure that your testing framework is globally accessible within the environment, as the skill will run automated checks before and after execution.
The fire skill organizes its runtime operations, task management, and output tracking according to a structured taxonomy:
| Data Component | Format / Structure | Purpose |
|---|---|---|
| Input Plan | Markdown File (.md) with Checklist Boxes |
Contains discrete tasks, specific validation instructions, and explicit commit boundaries. |
| Feature Branch | Git Branch Named fire/<plan>-<date> |
Isolates all execution side-effects away from the default repository branch. |
| Worktree Directory | Gitignoring Git-Worktree Folder | Provides temporary workspace isolation when native harness tools are unavailable. |
| Live Worklist | Updated Markdown Checkboxes (- [x]) |
Serves as the real-time state tracking mechanism for human operators and crash recovery. |
Loading
A structured AI agent skill designed to capture and extract durable, high-value technical knowledge at the end of a development session for long-term retention.

A design-first workflow skill that ensures all engineering tasks are fully designed, scoped, and user-approved before writing a single line of code.

Plate is a prose hygiene and leak-scrubbing skill that ensures outward-facing text like PRs, READMEs, blogs, and commits is free of identity, system, and infrastructure data leaks before publishing.

An automated web-research and scoring agent that evaluates search trends, competitor landscapes, and monetization viability to generate HTML feasibility reports.

An AI-driven execution engine that systematically processes code audits and bug backlogs, resolving issues one-by-one with rigorous validation and isolated commits.

A read-only repository audit skill that evaluates codebase health across seven stations and generates a prioritized, action-oriented backlog sorted by leverage.








































