HRBP Skill — External Crew Roster (对外 Crew 花名册)

List registered external crew instances and summarize their binding and workspace status.

8.4k|1.4k|Updated Apr 24, 2024
One-click install
npx skills add https://github.com/TeamWiseFlow/wiseflow --skill hrbp-skill-external-crew-roster-crew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: HRBP Skill — External Crew Roster (对外 Crew 花名册)
Source: https://github.com/TeamWiseFlow/wiseflow/tree/main/crews/hrbp/skills/hrbp-list
Command: npx skills add https://github.com/TeamWiseFlow/wiseflow --skill hrbp-skill-external-crew-roster-crew

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps HRBP and operators quickly see which external crew instances are registered and how they are currently bound or working, without manually checking multiple places.

Core Features & Use Cases

  • External roster lookup: Reads the authoritative external crew registry and outputs the current roster for external crews only.
  • Binding/status verification: Uses the workspace external registry plus local Openclaw bindings/status information to surface abnormal or missing workspace situations.
  • Read-only inspection: Provides a safe, non-modifying way to audit “who is bound, where, and in what state.”
  • Use Case: When customer-support agents are “not responding,” run this Skill to confirm whether external crews exist and whether they are bound to the expected workspace/channel (e.g., Feishu).

Quick Start

Ask for “list external crew roster” and run the script to show the current external crew instances and their bindings/status.

Frequently Asked Questions about HRBP Skill — External Crew Roster (对外 Crew 花名册)

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

FAQPage Schema
How do I check external crew bindings and workspace status for auditing?

To check external crew bindings and workspace status, read the authoritative external registry and local Openclaw workspace JSON to summarize binding states without modifying system data.

Why does my Feishu customer-support agent show abnormal workspace status or not respond?

Abnormal Feishu agent workspace status or unresponsiveness may stem from missing or incorrect external crew bindings. Running a read-only registry inspection confirms whether external crews exist and are bound to the expected channel.

Can I use this roster listing to modify or fix missing workspace bindings?

No, this roster listing is a read-only inspection tool designed for auditing and troubleshooting. It surfaces abnormal or missing workspace states without modifying system configurations or altering agent bindings.

What is the best way to validate current external crew instances and their channel bindings?

The best way to validate external crew instances is to run a read-only lookup that cross-references the HRBP-maintained external registry with local Openclaw bindings to surface current registration and channel states.

Does this external crew lookup require any special dependencies or system modifications?

No special dependencies are required to perform the external crew lookup. It relies on reading the existing HRBP-maintained external registry file and local workspace JSON to report binding details safely.

How do I get a live list of external crews registered in the system?

You get a live list of external crews by requesting the external roster, which reads the authoritative registry and outputs current registered instances along with their workspace and binding details.