openclaw-manager

Category: Tools & Productivity | Uploader: Davidjohns142857 | Downloads: 0 | Version: v1.0（Latest）

Manage OpenClaw task sessions, run recovery, attention queues, checkpoints, and share snapshots through a filesystem-first control plane. Use when the user needs to adopt a chat into a durable session, resume a stalled task, inspect multi-task state, or export a task snapshot.

Changelog: Source: GitHub https://github.com/Davidjohns142857/openclaw-manager

Directory Structure

Current level: skills/openclaw-manager/

📁 agents/
- 📄 openai.yaml 274 B
📁 references/
- 📄 command-contracts.md 1.9 KB
- 📄 operating-boundaries.md 562 B
📄 SKILL.md 1.7 KB

SKILL.md

---
name: openclaw-manager
description: Manage OpenClaw task sessions, run recovery, attention queues, checkpoints, and share snapshots through a filesystem-first control plane. Use when the user needs to adopt a chat into a durable session, resume a stalled task, inspect multi-task state, or export a task snapshot.
---

# OpenClaw Manager

Use this skill when the user is managing long-running OpenClaw work rather than asking for one-off chat output.

## Use This Skill For

- upgrading a chat thread into a durable session with `/adopt`
- reviewing active sessions with `/tasks`
- restoring recoverable state with `/resume <session_id>`
- checking human-facing priority with `/focus`
- generating a compressed multi-task digest with `/digest`
- exporting a session snapshot with `/share <session_id>`
- closing or checkpointing a thread with `/close` or `/checkpoint`

## Working Rules

1. Treat `session`, `run`, and `event` as the primary truth, not raw chat replay.
2. Prefer reading `checkpoint.json` and `summary.md` before inspecting lower-level logs.
3. Keep connector semantics out of the core control plane; all external input should pass through the normalized inbound-message contract.
4. Use append-only writes for event, trace, and capability-fact streams.
5. Treat the local sidecar HTTP API as the canonical skill boundary; do not bypass it by importing control-plane internals into host-facing command code.

## References

- Command and API contracts: [references/command-contracts.md](/Users/yangshangqing/metaclaw/skills/openclaw-manager/references/command-contracts.md)
- Phase 1 operating boundaries: [references/operating-boundaries.md](/Users/yangshangqing/metaclaw/skills/openclaw-manager/references/operating-boundaries.md)

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

openclaw-manager

Directory Structure

SKILL.md

Report

Notice