OpenClaw Operator Capability Pack Skill
Expert OpenClaw operator capability skill for secure deployment, policy governance, tool boundaries, and production observability.
Open the source and read safety notes before installing.
Prerequisites
- OpenClaw environment access
- Policy/security requirements
- Monitoring and alerting platform
Schema details
- Install type
- package
- Reading time
- 9 min
- Difficulty score
- 87
- Troubleshooting
- Yes
- Breaking changes
- No
- Scope
- Source repo
- Stars
- 373,140 source repo stars
- Forks
- 77,409
- Updated
- 2026-05-19T11:43:27Z
- Package verified
- Yes
- SHA-256
- d67f69f050a67f21b64fd103dc9a901b46624621d7aaae84606ba3f657c12749
- Skill type
- capability-pack
- Skill level
- expert
- Verification
- validated
- Verified at
- 2026-04-10
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md |
| cursor | Adapter | .cursor/rules/<skill-name>.mdc |
| cli | Manual | AGENTS.md or tool-specific context file |
Full copyable content
# Trigger
"Use the OpenClaw operator capability pack for this environment."
# Required output
1) Deployment and trust-boundary map
2) Tool and permission policy matrix
3) Observability and SLO plan
4) Incident and recovery proceduresAbout this resource
Knowledge Freshness
This capability pack is pinned to documentation verified on 2026-04-10. When upstream docs change, refresh endpoint contracts, examples, and constraints before using this skill for production changes.
Retrieval Sources
- https://github.com/openclaw/openclaw
- https://github.com/openclaw/openclaw/blob/main/README.md
- https://github.com/openclaw/openclaw/blob/main/CONTRIBUTING.md
Always prefer direct retrieval from official docs/API references over model memory for limits, endpoint signatures, and behavior guarantees.
Core Workflow
- Confirm target version/runtime and pull latest official docs for the task scope.
- Build an execution plan with explicit read-only discovery before any mutation.
- Validate contracts, permissions, and safety constraints before applying changes.
- Execute with deterministic checkpoints and rollback criteria.
- Produce a verification report with evidence, caveats, and next actions.
Overview
This capability pack teaches agents to operate OpenClaw in production responsibly. It covers governance, privilege boundaries, runtime controls, and incident readiness.
Capability Scope
- Runtime architecture and isolation
- Tool governance and approval workflows
- Cost/latency/reliability controls
- Auditability and compliance-ready logs
- Incident containment and recovery
Compatibility
Native
- Claude Code / Claude: native skill usage via
SKILL.md. - Codex/OpenAI workflows: compatible with Agent Skills-style
SKILL.mdcontent as reusable workflow instructions.
Manual Adaptation
- Gemini CLI: native skill usage via
.gemini/skills/<skill-name>/SKILL.mdor.agents/skills/<skill-name>/SKILL.mdwhere supported. - Cursor: use the generated
.cursor/rules/*.mdcadapter for project rules. - OpenClaw and similar agents: use the same skill content as a reusable prompt/workflow file when native skill import is unavailable.
Production Rules
- Treat agent tool access as privileged surface.
- Prefer explicit approvals for high-impact actions.
- Segment environments and secrets by risk.
- Keep response plans tested and documented.
Troubleshooting
Issue: Agents exceed intended permission scope
Fix: Move to strict allowlists with per-tool approvals.
Issue: Hard to diagnose cross-agent failures
Fix: Add trace IDs and event correlation across all agent actions.
Issue: Cost spikes during autonomous runs
Fix: Add budget limits and route heavy tasks to cheaper model/tool paths.
Output Contract
- Provide an implementation plan ordered by risk and dependency.
- Provide exact production-ready config/commands with no placeholders.
- Call out secrets, permissions, and least-privilege requirements.
- Include rollback and recovery guidance for each risky step.
Validation Checklist
- Verify all referenced docs/versions before applying changes.
- Run regression checks for core user flow and error paths.
- Confirm observability/logging is enabled for changed components.
- Confirm security controls (auth, rate limits, input validation) still pass.
- Record final known limitations and follow-up actions.
Source citations
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.