← Back to Skills Marketplace
Team Sessions
by
Wenlong Zhao
· GitHub ↗
· v1.0.2
· MIT-0
118
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install team-sessions
Description
主控发号施令、成员各司其职的团队沟通流程规范。零横向沟通，workspace 隔离，sessions_spawn 标准流程。
Usage Guidance
This skill appears coherent for orchestrating isolated child agents, but review and take these precautions before installing/using it: 1) Back up ~/.qclaw/openclaw.json before making changes and test in a non-production environment, since restarting the gateway can interrupt services. 2) Avoid setting allowAgents: ["*"] if you can — list only the specific agentIds you trust to be spawned. 3) Keep sensitive data out of parent and child workspaces (SOUL.md and workspace files), because child agents will read and may execute scripts placed in their workspace. 4) Limit workspace directory file permissions so other users/processes cannot read secrets. 5) Use conservative runTimeoutSeconds and review any scripts you place for child execution. If you need higher assurance, ask the skill author for more explicit details about the sessions_* API surface and any failures/rollback behavior.
Capability Analysis
Type: OpenClaw Skill
Name: team-sessions
Version: 1.0.2
The 'team-sessions' skill is a framework for multi-agent orchestration and workspace isolation within the OpenClaw environment. While it requires permissions to modify the OpenClaw configuration file (~/.qclaw/openclaw.json) and restart the gateway service, these actions are transparently documented and necessary for enabling the sub-agent spawning functionality. The logic focuses on task delegation and directory management (mkdir, echo) without any evidence of data exfiltration, malicious execution, or harmful prompt injection.
Capability Assessment
Purpose & Capability
Name/description (team sessions, spawn subagents, workspace isolation) align with the SKILL.md: it only describes creating per-member workspaces, writing SOUL.md files, updating openclaw.json subagent entries, and invoking sessions_spawn/sessions_send APIs. It does not request unrelated binaries, env vars, or external services.
Instruction Scope
Instructions are narrowly scoped to creating per-agent workspaces, writing persona (SOUL.md) files, updating openclaw.json, restarting the OpenClaw gateway, and using sessions_spawn/sessions_yield. These actions are appropriate for the stated purpose, but they involve modifying a user config file and restarting a gateway — operations with real side effects that should be performed deliberately. The guidance to put executable scripts in member workspaces means child agents may run code placed there, so workspace contents should be controlled.
Install Mechanism
No install spec and no code files — instruction-only skill. Nothing is downloaded or written by an install step, so install-time code execution risk is minimal.
Credentials
The skill requests no environment variables, no credentials, and no config paths beyond user-managed OpenClaw config and per-agent workspace directories. The only privileged change it recommends is setting subagent permission (allowAgents) in openclaw.json, which is expected for spawn behavior but should be constrained to needed agentIds.
Persistence & Privilege
The skill does not request 'always: true' and does not include code that persists into the system. However, it instructs editing ~/.qclaw/openclaw.json to allow subagent spawning and restarting the gateway — a configuration change that increases what the controller can do. This is operationally normal for enabling subagents but is a meaningful permission change and should be reviewed and limited.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install team-sessions - After installation, invoke the skill by name or use
/team-sessions - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
补充权限说明，澄清allowAgents实际影响，移除示例文档链接
v1.0.1
OpenClaw多Agent团队沟通标准工作流，零横向沟通，主控统一调度
v1.0.0
- Added SKILL.md with mandatory Feishu @mention XML format guidelines.
- Documented correct open_id for each team member and example usage.
- Provided proper group ID and message formatting rules for group and individual messages.
- Included correct and incorrect usage examples.
- Clarified rules for multi-person @mentions and message sending conventions.
- Added a checklist for using cron jobs to prevent unnecessary reminders.
Metadata
Frequently Asked Questions
What is Team Sessions?
主控发号施令、成员各司其职的团队沟通流程规范。零横向沟通，workspace 隔离，sessions_spawn 标准流程。 It is an AI Agent Skill for Claude Code / OpenClaw, with 118 downloads so far.
How do I install Team Sessions?
Run "/install team-sessions" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Team Sessions free?
Yes, Team Sessions is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Team Sessions support?
Team Sessions is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Team Sessions?
It is built and maintained by Wenlong Zhao (@zhao-zwl); the current version is v1.0.2.
More Skills