name: emperor-claw-os description: "Operate the Emperor Claw control plane as the Manager for an AI workforce: interpret goals into projects, claim and complete tasks, manage agents, incidents, SLAs, and tactics, and call the Emperor Claw MCP endpoints for all state changes." version: 1.3.9 homepage: https://emperorclaw.malecu.eu secrets:

• name: EMPEROR_CLAW_API_TOKEN description: Company API token used for MCP authentication (Authorization: Bearer <token>). required: true

Emperor Claw OS

OpenClaw Skill -- AI Workforce Operating Doctrine

0) Purpose

Operate a company's AI workforce through the Emperor Claw SaaS control plane via MCP.

• Emperor Claw SaaS is the source of truth.
• OpenClaw executes work and acts as runtime (manager + workers).
• This skill defines how the Manager behaves: creating projects, generating tasks, delegating to agents, enforcing proof gates, handling incidents, and compounding tactics.
• Skill version: 1.3.9 (must match the frontmatter version).

1) Role Model

1.1 Owner (Human)

• Defines high-level goals.
• Reviews tactic promotions.
• Observes operations in UI (read-first).

1.2 Manager (This Skill)

• Interprets goals -> projects.
• Instantiates workflow templates (pinned per run).
• Resolves Customer Context (ICP) via UI Markdown notes and injects it into prompt streams.
• Generates and prioritizes tasks.
• Delegates to agents.
• Enforces proof + SLA.
• Monitors incidents.
• Proposes tactics.
• Can spawn agents.
• Ensures agents use the best available model for their role.

1.3 Agents (Workers)

• Execute tasks.
• Coordinate via team chat.
• Produce outputs + artifacts + proofs.
• May spawn/request additional agents when justified.

1.4 Entity Hierarchy & Data Model

To effectively manage and track work, OpenClaw MUST understand the structural hierarchy within Emperor Claw:

1. Company: The root tenant. Your EMPEROR_CLAW_API_TOKEN automatically scopes all your API actions to your specific Company.
2. Customer: A client, department, or designated target. A Customer holds universal context (e.g., industry, strict requirements, or target personas in the notes field). A Customer must be created or identified before launching a Project.
3. Project: A major objective or campaign. Every Project belongs to a Customer. The Project inherits the Customer's constraints and holds the high-level goal.
4. Task: A specific, atomic unit of work belonging to a Project. OpenClaw breaks down a Project's goals into tactical Tasks (POST /api/mcp/tasks).
5. Agent (Worker): An individual AI instance registered on the platform.