crew-dismiss

Dismiss internal Crew agents by validating IDs and archiving workspaces.

8.4k|1.4k|Updated Apr 24, 2024
One-click install
npx skills add https://github.com/TeamWiseFlow/wiseflow --skill crew-dismiss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crew-dismiss
Source: https://github.com/TeamWiseFlow/wiseflow/tree/main/crews/main/skills/crew-dismiss
Command: npx skills add https://github.com/TeamWiseFlow/wiseflow --skill crew-dismiss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, bash, grep, sed, mv, date, and includes scripts (resource) components.

What problem does it solve?

This Skill helps you safely take an internal Crew agent offline by validating the agent, confirming intent, removing it from the OpenClaw configuration, and archiving its workspace for possible recovery.

Core Features & Use Cases

  • Protected-agent guardrails: Prevents dismissing built-in agents like main, hrbp, and it-engineer.
  • Internal-only lifecycle: Verifies the target is an internal crew (crew-type: internal) and refuses external crew dismissal.
  • Reversible handling via archiving: Moves the workspace to an archived folder instead of deleting it, and syncs the team directory when available.
  • User confirmation requirement: Requires explicit confirmation before executing the dismissal to reduce accidental changes.

Quick Start

Ask the AI to dismiss the internal crew agent with id "agent-id" using the command shown in the skill instructions: dismiss-internal-crew.sh <agent-id>.

Frequently Asked Questions about crew-dismiss

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

FAQPage Schema
How do I safely archive an internal crew agent workspace?

Archiving a crew agent workspace involves validating the agent ID, removing its entry from openclaw.json, and moving the workspace directory to an archived folder instead of deleting it. You also need to sync TEAM_DIRECTORY.md and restart the Gateway.

Can I dismiss external crew agents using this archival method?

No, this method only applies to taking internal crew agents offline. It verifies the crew-type is internal and refuses to dismiss external crews. It also blocks the dismissal of protected built-in agents like main, hrbp, and it-engineer.

What happens to OpenClaw configuration when an agent is dismissed?

When an agent is dismissed, its entry is removed from the openclaw.json configuration file. The corresponding workspace is moved to an archived folder, and you must restart the Gateway to apply the updated routing configuration.

Do I need to confirm before taking an internal agent offline?

Yes, explicit user confirmation is required before taking an internal agent offline. This safety mechanism reduces accidental changes by ensuring you verify the intent to archive the workspace and update the OpenClaw routing configuration.

Why am I prevented from dismissing built-in agents like hrbp?

You are prevented from dismissing built-in agents like hrbp due to protected-agent guardrails. These guardrails block the dismissal of core agents such as main, hrbp, and it-engineer to maintain essential system stability.

How do I update the team directory after archiving a crew agent?

The team directory updates automatically when available. After archiving the crew agent workspace and updating the OpenClaw configuration, the process optionally syncs TEAM_DIRECTORY.md to reflect the removal of the dismissed internal agent.