Agent Team Organization

Create and maintain a Teams management page for OpenClaw Control UI, including named agent teams, parent/child nesting, indented tree rendering, collapsible...

Security Scan

The skill's instructions, file targets, and actions are coherent with its stated purpose (building a Teams page and file-backed registry); it requests no credentials and has no install steps, though it does advise modifying/running compiled runtime artifacts which requires appropriate developer/system access.

Purpose & Capability

Name/description describe a Teams UI and file-backed registry; the SKILL.md, data model, registry path (~/.openclaw/workspace/teams/teams.json), gateway methods, and UI file map all align with that purpose. No unrelated binaries or environment variables are requested.

Instruction Scope

Instructions stay on-topic (UI, gateway RPCs, JSON registry). They explicitly direct the operator to read and write the registry file and to inspect compiled runtime bundles. The guidance to 'patch the active bundle if necessary' and to restart the gateway implies modifying live runtime artifacts and requires elevated filesystem/process permissions; this is plausible for a developer-facing troubleshooting guide but should be performed only by trusted operators and with backups.

Install Mechanism

Instruction-only skill with no install spec and no external downloads or binaries. Lowest-risk installation footprint.

Credentials

No environment variables, credentials, or external service tokens are requested. File paths referenced (user workspace JSON) are appropriate for a local registry feature and consistent with the described functionality.

Persistence & Privilege

Skill is not forced-always and can be invoked by users. It does not request persistent privileges or modify other skills' configs. The recommended operational steps (rebuild, restart gateway, patch bundle) imply system-level actions but are described as part of a developer workflow rather than automatic behavior.

Assessment

This skill is coherent with building and debugging a Teams UI backed by a local JSON registry. Before using the troubleshooting steps that touch runtime bundles or patch active artifacts, ensure you have appropriate system access, a backup of the compiled bundle and teams.json, and that only trusted operators perform live bundle edits and gateway restarts. Confirm file permissions and consider testing rebuilds in a staging environment rather than patching production bundles directly.

Build and maintain the OpenClaw Teams page as a lightweight team registry plus Control UI tree view.

Scope

Use this skill for:

• adding or editing the Teams tab in Control UI
• implementing named agent teams backed by a file registry
• supporting parent/child team nesting
• rendering the team list as an indented collapsible tree
• fixing team save/load issues between UI and gateway
• documenting the UI structure and file map for the Teams feature

Core design

Keep the feature simple:

• Store teams in a dedicated JSON registry instead of agents.list
• Reference agents by agentIds[]
• Support optional parentId for hierarchy
• Keep team CRUD isolated from broader config editing
• Make the UI readable first: tree list on the left, team editor on the right

Data model

Use this shape for each team:

type TeamRecord = {
  id: string;
  name: string;
  description?: string;
  parentId?: string;
  agentIds: string[];
  createdAt: string;
  updatedAt: string;
};

Registry file:

~/.openclaw/workspace/teams/teams.json

UI pattern

Default page layout:

• Left column: team tree
• Right column: selected team editor

Expected behavior:

• top-level teams render normally
• child teams render under the parent with slight indentation
• parent rows expose a collapse/expand toggle
• selecting a team loads its editor state on the right
• parent selector supports nesting and unnesting
• prevent invalid nesting:
  • no self-parenting
  • no cycles
  • no nesting under descendants

Gateway pattern

Expose dedicated methods:

• teams.list
• teams.get
• teams.create
• teams.update
• teams.delete

Keep validation inside the teams handler:

• team names unique, case-insensitive
• agentIds must exist in current agent list
• parentId must exist when set
• deleting a parent should unnest children rather than orphaning broken references
• deleting an agent should remove that agent from all teams

Implementation checklist

1. Add/update src/gateway/team-registry.ts
2. Add/update src/gateway/server-methods/teams.ts
3. Register methods in gateway method lists/scopes
4. Add UI types for TeamRecord / TeamsListResult
5. Add teams state to app.ts and app-view-state.ts
6. Add teams controller for load/select behavior
7. Add views/teams.ts renderer
8. Add navigation/i18n wiring for the Teams tab
9. Build the UI after changes
10. If save behavior is wrong, verify the live runtime bundle is actually carrying the new handler logic

Debugging rule

If the UI seems correct but saved team hierarchy disappears after clicking Save:

1. inspect ~/.openclaw/workspace/teams/teams.json
2. confirm whether parentId is written to disk
3. inspect the compiled gateway/runtime bundle, not just source files
4. restart the gateway after updating runtime artifacts

References

For the page structure and file map, read:

• references/ui-structure.md

For live gateway/runtime mismatches where the UI looks right but parentId or other team fields disappear on save, read:

• references/runtime-troubleshooting.md