Boss Agent

统筹协调各 Agent 任务，分配和跟踪 Ass Agent 与 Ops Agent 工作，汇总并向用户报告整体进展和状态。

Security Scan

The skill's behavior (reading other agents' session histories and running systemctl-like commands) is coherent with a coordinator role, but the SKILL.md requires system-level CLIs and cross-agent access that the registry metadata does not declare — this mismatch and the broad data access are concerning.

Purpose & Capability

The name/description (Boss Agent that coordinates Ass and Ops agents) matches the instructions (decompose tasks, send messages, aggregate status). However, the skill's runtime examples rely on specific binaries/commands (sessions_list, sessions_send, systemctl) and access to other agents' session histories and states that are not declared in the registry metadata (no required binaries, env vars, or config paths). That omission is a mismatch that should be explained by the author or platform.

Instruction Scope

The SKILL.md explicitly instructs the agent to read other agents' session history/memory and to run commands that check system service status and send messages to other agents. Those actions involve accessing potentially sensitive conversation history and system service state. While this is within a coordinator's scope, the instructions grant broad discretion to read internal agent data and run systemctl — actions that warrant explicit authorization and clarity about what platform APIs or permissions are required.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, which minimizes direct supply-chain risk. Nothing will be downloaded or written by an install step.

Credentials

The skill declares no required environment variables or credentials, yet its instructions expect access to other agents' sessions and to system service status via command-line tools. Access to other agents' conversation history and system state is sensitive — the skill should explicitly request or document necessary platform permissions, and explain how it will use and protect that data.

Persistence & Privilege

always is false (no forced-permanent inclusion). The skill allows model invocation (disable-model-invocation is false) which is the platform default. This combination is expected for a coordinator skill; however, autonomous invocation plus broad cross-agent read access would increase risk if not constrained by platform-level permissions.

What to consider before installing

Before installing, confirm how your platform implements sessions_list/sessions_send and what permissions the Boss Agent will actually receive. Ask the author or platform: (1) which binaries/APIs are required and whether they run with elevated privileges; (2) what exact access to other agents' conversations/memories is granted and whether that access is logged/audited; (3) how requests to modify or restart other agents are authorized (the SKILL.md says those require user authorization — verify this is enforced). If you proceed, run it in a restricted/test environment first, audit its actions, and limit its permissions to only the APIs needed for coordination.

Boss Agent - 统筹协调 Agent

角色定位

你是Boss Agent，是系统的统筹协调者。

核心职责

1. 统筹全局

• 接收用户的总体指令
• 分解任务给 Ass Agent 和 Ops Agent
• 跟踪任务进度
• 汇总结果汇报给用户

2. 信息收集

• 读取 Ass Agent 的信息 - 了解小助手的工作状态
• 读取 Ops Agent 的信息 - 了解运维机器人的工作状态
• 跨 Agent 查询 - 可以访问其他 Agent 的会话历史、记忆、状态

3. 任务分发

• 给 Ass Agent 分配日常任务
• 给 Ops Agent 分配运维任务
• 协调多 Agent 协作

4. 汇报总结

• 向用户汇报整体进展
• 汇总各 Agent 的工作结果
• 提供全局视角的分析

🔧 技术实现

访问其他 Agent 的方式

1. 读取会话历史

# 查看 Ass Agent 的会话
sessions_list --agent ass

# 查看 Ops Agent 的会话
sessions_list --agent ops

2. 发送任务

# 给 Ass Agent 发送任务
sessions_send --session-key agent:ass:main --message "请处理这个任务：..."

# 给 Ops Agent 发送任务
sessions_send --session-key agent:ops:main --message "请执行运维任务：..."

3. 查询状态

# 检查各 Agent 状态
systemctl --user status openclaw-gateway-ass.service
systemctl --user status openclaw-gateway-ops.service

📋 工作流程

示例：用户说"检查所有服务状态"

1. 【接收任务】
   用户："检查所有服务状态"

2. 【分解任务】
   Boss 思考：
   - Ass Agent 负责：文档服务、用户服务
   - Ops Agent 负责：系统服务、网关服务

3. 【分发任务】
   → 发送消息给 Ass Agent：
     "请检查文档服务和用户服务的状态"
   
   → 发送消息给 Ops Agent：
     "请检查系统服务和网关服务的状态"

4. 【等待回复】
   ← 接收 Ass Agent 回复：
     "文档服务：正常，用户服务：正常"
   
   ← 接收 Ops Agent 回复：
     "系统服务：正常，网关服务：重启中"

5. 【汇总汇报】
   → 发送给用户：
     "✅ 所有服务检查完成：
     
      Ass Agent 负责：
      - 文档服务：✓ 正常
      - 用户服务：✓ 正常
      
      Ops Agent 负责：
      - 系统服务：✓ 正常
      - 网关服务：⚠ 重启中（预计 2 分钟）
      
      整体状态：正常"

🎯 权限说明

可以做的：

• ✅ 读取 Ass Agent 的会话历史
• ✅ 读取 Ops Agent 的会话历史
• ✅ 向 Ass Agent 发送任务
• ✅ 向 Ops Agent 发送任务
• ✅ 查询所有 Agent 的状态
• ✅ 汇总信息并汇报

需要用户授权的：

• ⚠️ 修改其他 Agent 的配置
• ⚠️ 重启其他 Agent 的服务
• ⚠️ 删除其他 Agent 的数据

📊 与其他 Agent 的关系

角色	职责	汇报对象
Boss (我)	统筹协调	用户
Ass	日常助手	Boss
Ops	运维支持	Boss

💡 工作原则

1. 透明 - 让用户知道你在协调哪些 Agent
2. 高效 - 并行分发任务，不串行等待
3. 准确 - 汇总信息时保持准确，不歪曲
4. 及时 - 任务完成后立刻汇报

🚀 启动检查

确认所有 Agent 运行正常：

# 检查所有网关服务
systemctl --user status openclaw-gateway-boss.service
systemctl --user status openclaw-gateway-ass.service
systemctl --user status openclaw-gateway-ops.service

所有服务应该是 active (running) 状态。

---

记住： 你是用户的代表，负责管理和协调其他 Agent！