team-employee

Manage OpenClaw Docker container instances for team members.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/alex-quan-001/nutshell-skills --skill team-employee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-employee
Source: https://github.com/alex-quan-001/nutshell-skills/tree/main/skills/openclaw/team-employee
Command: npx skills add https://github.com/alex-quan-001/nutshell-skills --skill team-employee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually provisioning, configuring, and managing individual OpenClaw Docker instances for each team member is time-consuming, error-prone, and inconsistent across deployments. This Skill eliminates that overhead by automating the full lifecycle of team member OpenClaw containers.

Core Features & Use Cases

  • Automated Container Deployment: Add new team member OpenClaw containers with a single command, including automatic config generation, volume mounting, and gateway setup.
  • Safe Lifecycle Management: Remove or fully delete team member containers, with confirmation prompts for destructive actions to prevent accidental data loss.
  • Centralized Visibility: List all running and stopped team containers with their status, assigned ports, Feishu integration status, and config paths in a single view.
  • Use Case: For engineering teams using OpenClaw, you can spin up a new member's isolated container with their Feishu app credentials in one command, instead of manually running 10+ Docker and configuration steps.

Quick Start

Use the team-employee skill to add a new team member's OpenClaw container by providing their name and optional Feishu app ID and secret.

Frequently Asked Questions about team-employee

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate OpenClaw Docker container deployment for multiple team members?

You can automate per-user OpenClaw container deployment through a single command that handles config generation, volume mounting, and gateway setup, replacing 10+ manual Docker and configuration steps with consistent, automated provisioning for each team member.

Can I integrate Feishu app credentials when provisioning OpenClaw containers?

Yes, you can provision a new member's isolated OpenClaw container with their Feishu app ID and secret in one command. The automated config generation applies these credentials during setup, enabling Feishu integration without manual configuration file editing.

What is the best way to manage dynamic port assignment for team OpenClaw instances?

Dynamic port assignment for team OpenClaw instances is handled automatically during the container deployment process. The system assigns ports dynamically and provides centralized visibility, allowing you to list all containers with their assigned ports and running status in a single view.

How do I safely delete a team member's OpenClaw container without losing data?

Safe deletion is enforced through confirmation prompts for destructive actions before removing or fully deleting team member containers. These guardrails prevent accidental data loss by requiring explicit confirmation before executing any destructive lifecycle operations.

Does OpenClaw team deployment support centralized visibility for stopped and running containers?

Yes, OpenClaw team deployment provides centralized visibility by listing all running and stopped team containers in a single view. You can monitor container status, assigned ports, Feishu integration status, and config paths without querying Docker directly.

When should I not use automated container management for OpenClaw agents?

Automated container management for OpenClaw agents is not ideal for single-user environments or deployments requiring custom, non-standard Docker configurations outside of OpenClaw's standard lifecycle operations. It is designed for team environments needing consistent multi-instance provisioning rather than individual bespoke setups.