Files

zhi 795a710376 refactor: enforce layer responsibilities across all skills

Rewrote docs/standard.md as the single source of truth for skill
structure (menu/tools/recipes/manual analogy). Trimmed all SKILL.md
files to pure routers, moved recruitment workflow out of SKILL.md
into workflows/recruitment.md, removed duplicated standards from
workflow files.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-17 20:40:16 +00:00

1.6 KiB

Raw Blame History

Recruitment Workflow

Full onboarding flow for new agents. Follow these steps when a request to create a new agent is received.

See claw-skills/docs/standard.md for skill structure and writing standards.

Step 1 — Gather Requirements

Communicate with the requester to collect:

New agent's agent-id
New agent's primary model (--model)
New agent's role and position
Whether the agent is a contractor (default: no)

Step 2 — Create Agent

Execute {baseDir}/scripts/new-agent with the gathered parameters:

# OpenClaw type
new-agent --type openclaw --agent-id <agent-id> --model <primary-model>

# Contractor type
new-agent --type contractor --contractor-provider <claude|gemini> --agent-id <agent-id>

Step 3 — Interview

Use the create-discussion-channel tool to start an interview with the new agent:

Participant: interviewee
Discussion guide: <@YOUR_DISCORD_USER_ID> please refer to {baseDir}/workflows/interviewer.md

Use ego-mgr get discord-id (via pcexec) to look up your Discord user ID if unsure.

After receiving the discussion callback, review the summary:

Contains agent's name and gender → proceed to Step 4
Missing either field → attempt another create-discussion-channel call
Still unavailable → notify the requester and proceed without it

Step 4 — Onboard

Use proxy-pcexec to call {baseDir}/scripts/onboard:

proxy-for: new agent's agent-id
Parameters: --name, --role, --position, --gender, --bot-token

Step 5 — Report

Notify the requester that onboarding is complete.

1.6 KiB Raw Blame History