# Hire Team

> Scaffold a bilingual Scout/Writer/Producer OpenClaw team when the user asks to hire a team, create a multi-agent content pipeline, build Scout Writer Producer roles, or 搭建内容生产三人组 / 多 Agent 协作团队.

- Skill: `qqyule/hire-team` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add qqyule/hire-team`
- Raw SKILL.md: https://api.skillmd.com/api/skills/qqyule/hire-team/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: qqyule (https://skillmd.com/u/qqyule)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/qqyule/hire-team

---


# hire_team

Use this skill when the user wants to bootstrap a three-role OpenClaw content team with `Scout`, `Writer`, and `Producer`, especially for requests like:

- "hire a team"
- "create a scout writer producer team"
- "set up a multi-agent content pipeline"
- "搭建多 Agent 内容流水线"
- "组建内容生产三人组"

## What this skill does

- Creates a reusable team scaffold in a target directory.
- Generates `workspace-scout/`, `workspace-writer/`, and `workspace-producer/`.
- Writes role-specific `SOUL.md` and `MEMORY.md` files.
- Writes `TEAM.md` and `openclaw-setup.md` in the team root.
- Returns a concise setup summary and manual next steps.

## Rules

- Do not promise `openclaw run hire_team`. This skill is triggered by normal chat intent.
- Do not modify the user's OpenClaw config automatically.
- Do not overwrite existing files unless the user explicitly asks to replace them.
- If OpenClaw is not installed, still generate the scaffold and explain the manual setup path.

## Workflow

1. Resolve the target directory.
   Use the user-provided path when available. Otherwise default to the current workspace.
2. Resolve options.
   Use `--team-prefix` when the user gives a project/team name.
   Default `--lang bilingual`.
   Add `--force` only when the user explicitly allows overwriting.
3. Run the initializer from the skill root, or use an absolute path to the script:

```bash
node "<skill-root>/scripts/init-team.js" --target-dir "<target-dir>" --team-prefix "<team-prefix>" --lang bilingual
```

4. Read the script output and reply with a structured summary:
   - `Created`
   - `Skipped`
   - `Environment`
   - `Next steps`

## Files to read when needed

- `templates/scout_soul.md`
- `templates/writer_soul.md`
- `templates/producer_soul.md`
- `scripts/init-team.js`

## Output standard

Keep the response compact. Mention:

- absolute target directory
- created files and skipped files
- whether `openclaw` was detected
- the next 2-4 commands the user should run