HRBP Skill — Remove (解雇 / 停用实例)

Remove external crew agent instances by updating openclaw.json and archiving workspaces.

8.4k|1.4k|Updated Apr 24, 2024
One-click install
npx skills add https://github.com/TeamWiseFlow/wiseflow --skill hrbp-skill-remove
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: HRBP Skill — Remove (解雇 / 停用实例)
Source: https://github.com/TeamWiseFlow/wiseflow/tree/main/crews/hrbp/skills/hrbp-remove
Command: npx skills add https://github.com/TeamWiseFlow/wiseflow --skill hrbp-skill-remove

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps HRBP users remove (deactivate) an external crew agent instance from their wiseflow/openclaw workspace safely, while preserving the agent’s workspace for recovery.

Core Features & Use Cases

  • External-only protection: prevents accidental deletion of internal crews like main, hrbp, and it-engineer.
  • Registry-aware removal: removes the agent from openclaw.json (agents list, bindings) and from workspace-hrbp/EXTERNAL_CREW_REGISTRY.md.
  • Workspace archival instead of permanent deletion: archives the instance workspace to ~/.openclaw/archived/... so it can be restored later.
  • User-confirmed safety workflow: requires explicit confirmation before any system-modifying action.

Quick Start

Ask the assistant to remove an external instance by ID after reviewing the listed plan and confirming the action explicitly.

Frequently Asked Questions about HRBP Skill — Remove (解雇 / 停用实例)

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

FAQPage Schema
How do I safely remove an external agent instance from my openclaw workspace?

To remove an external agent instance, the Skill updates openclaw.json and archives the agent workspace to ~/.openclaw/archived/ for later recovery. It requires explicit user confirmation before executing the deterministic remove-agent.sh script.

What happens to the workspace when I deactivate an external crew agent?

When you deactivate an external crew agent, its workspace is not permanently deleted but archived to ~/.openclaw/archived/. This preserves the agent's configuration and data for later recovery.

Can I use this workflow to delete internal crews like main or hrbp?

No, you cannot delete internal crews like main, hrbp, or it-engineer. The Skill enforces external-only protection by validating crew type via SOUL.md to prevent accidental deletion of critical internal agents.

What registry configurations are cleaned up when archiving an external agent?

Archiving an external agent cleans up registry configurations by removing the agent from the openclaw.json agents list, clearing channel bindings, and deleting its entry from the EXTERNAL_CREW_REGISTRY.md file.

Do I need bash and node dependencies to run the agent removal script?

Yes, you need bash, node, grep, sed, mktemp, and date installed. These dependencies are required to execute the remove-agent.sh script and perform deterministic workspace archival and registry updates.