Tencent SkillHub · AI

Multi Workplace

Manage multiple workplaces (project directories) with multi-agent orchestration, isolated memory, and inter-agent communication. Use when the user mentions:...

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

Manage multiple workplaces (project directories) with multi-agent orchestration, isolated memory, and inter-agent communication. Use when the user mentions:...

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: README.md, SKILL.md, assets/templates/config.json, assets/templates/deploy/dev.md, assets/templates/deploy/main.md, assets/templates/deploy/pre.md

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 0.4.0

Provenance

Publisher: dickwu
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 18 sections Open source page

Workplace Skill

Manage multiple project workplaces with per-workspace agents, isolated memory, and Swarm-style agent orchestration.

/workplace Command (Telegram / Slash)

Hierarchical navigation with parent → child drill-down. /workplace or /workplace list → Show top-level view: parent workspaces and standalone workplaces as buttons. Parents show (N) child count. Current workspace marked with ✓. Click a parent button → Drill into children. Shows child buttons + "Use parent" + "← Back". /workplace <name> → If standalone or child, switch directly. If parent with children, show drill-in. /workplace parent:child → Direct switch using colon syntax (e.g. log-stream:logstream). /workplace status → Current workspace card with parent, linked, agents, deploy envs. /workplace agents → Agent list with start/stop buttons.

Colon Syntax

/workplace log-stream:logstream resolves parent by name, then finds child under that parent. Supports quick switching without navigating menus.

Context Switching

When the user switches workplaces (via button click, name, or colon syntax): Update ~/.openclaw/workspace/.workplaces/current.json with the selected UUID and path Update lastActive in registry.json Load the new workspace's .workplace/config.json for context Send confirmation: name, path, parent (if any), linked workplaces, agent list Subsequent messages in the session should be aware of the active workspace context Read current.json at the start of any workplace operation to know which workspace is active. See telegram-ui.md for full button layouts, callback routing, and platform fallbacks.

Quick Reference

CommandActionworkplace init [path]Initialize workplace (scan existing or set up new)workplace listList all workplaces (inline buttons to switch)workplace switch <name|uuid>Switch active workplaceworkplace scan [path]Discover .git workplaces in subdirectoriesworkplace link <path>Link a related workplaceworkplace unlink <path|uuid>Remove a linked workplaceworkplace statusCurrent workplace info + agent statusworkplace agentsList agents in current workplaceworkplace agent start <name>Start an agent (runs as sub-agent)workplace agent stop <name>Stop a running agentworkplace kernel startStart persistent kernel agentworkplace kernel stopStop kernel agentworkplace export [zip|json]Export workplace configworkplace import <file>Import workplace from exportworkplace delete <name|uuid>Remove from registryworkplace deploy <env>Show/run deploy instructionsworkplace sync <ide>Generate context for cursor/claude/opencode/all

Registry

Central registry at ~/.openclaw/workspace/.workplaces/: registry.json — all known workplaces with UUID, path, hostname, links current.json — currently active workplace

Per-Workplace Structure

Each project gets a .workplace/ directory: .workplace/ ├── config.json # UUID, name, path, hostname, linked, parent ├── agents/*.md # Agent role definitions (kernel.md always present) ├── memory/ # Isolated daily logs (YYYY-MM-DD.md) ├── skills/ # Workplace-specific skills (user-managed via git) ├── chat.md # Inter-agent communication ├── structure.json # Auto-scanned file tree ├── full-tree.md # Full tree with parent + linked workplaces (by hostname) ├── process-status.json # Agent runtime states and errors └── deploy/ # Deployment docs: dev.md, main.md, pre.md

Workplace Detection

Any directory with .git/ is a potential workplace Submodules included as nested workplaces Parent workplace auto-detected from parent directories Manual linking via workplace link

Initialize a Workplace

Run scripts/init_workplace.sh <path> [--name <name>] [--desc <desc>] For existing projects: scan file structure, read *.md files, analyze project type, suggest agents For empty folders: ask project name, description, language/framework, roles needed Creates .workplace/ structure, registers in central registry, sets as current See init-guide.md for full flow details

Agent System

Agents are defined as .md files in .workplace/agents/ with YAML frontmatter (name, role, triggers, handoff_to). Run agents via sessions_spawn with system prompts built from their definitions + workplace context. See agent-system.md for agent creation, Swarm handoff, and runtime details

Inter-Agent Communication

Agents communicate via chat.md using a structured message protocol. The Rust file-watcher server monitors changes and outputs parsed messages as JSON lines. See chat-protocol.md for message format spec

Rust File-Watcher Server

Binary at assets/bin/workplace-server-{os}-{arch}. Build from source with scripts/build.sh. # Start server for a workplace workplace-server /path/to/project # Server outputs JSON lines to stdout for each new chat.md message {"timestamp":"...","sender":"coder","recipient":"reviewer","broadcast":[],"message":"...","line_number":1}

Export/Import

ZIP: Full .workplace/ folder (memory excluded by default) JSON: Config + agent definitions + deploy docs as portable manifest Import generates a new UUID to avoid collisions

Chat UI (Telegram / Discord)

On platforms with inline buttons, workplace list shows a clickable switcher. workplace agents shows start/stop buttons per agent. workplace deploy shows environment buttons. See telegram-ui.md for message formats, button components, and callback handling. Fallback: numbered text lists on platforms without button support (WhatsApp, Signal).

IDE Integration

Sync workplace context to external coding tools: Cursor → .cursor/rules/workplace.mdc (MDC with frontmatter) Claude Code → CLAUDE.md (markdown, marker-based updates) OpenCode → opencode.jsonc instructions field Run workplace sync all to update all detected IDEs, or target one: workplace sync cursor. See ide-sync.md for implementation details.

Scripts

ScriptPurposescripts/init_workplace.shInitialize .workplace/ in a directoryscripts/scan_workplaces.shFind .git workplaces under a pathscripts/build.shBuild Rust server for current platform

Supermemory Integration

Each workplace uses its UUID as containerTag for supermemory operations: Kernel agent saves structure summaries and project facts All workplace memories are isolated by containerTag Enables cross-session project state awareness

Command Details

See commands.md for full command reference with examples.

Category context

Agent frameworks, memory systems, reasoning layers, and model-native orchestration.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

5 Docs1 Config

SKILL.md Primary doc
assets/templates/deploy/dev.md Docs
assets/templates/deploy/main.md Docs
assets/templates/deploy/pre.md Docs
README.md Docs
assets/templates/config.json Config