菜单
Plan and create a NESTED team hierarchy (parent coordination team + per-stream child teams) for a complex multi-stream goal. Use INSTEAD of recommend-team/materialize-team when the goal names 2+ parallel work-streams (e.g. frontend + backend + DevOps). Onboarding-only.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Search the live web for a query and return ranked results (title, URL, snippet) as JSON. Works with no API key (DuckDuckGo HTML fallback) and uses the Brave Search API or SerpAPI automatically when BRAVE_API_KEY / SERPAPI_KEY is set. Any agent can call it for research, competitor analysis, market/trend lookups, fact-checking, finding sources to cite, or grounding a non-software goal (marketing, growth, commerce) in real-world information.
Transcribe a local audio (or video) file to text with timestamps using Whisper. Defaults to local whisper.cpp (free, offline, word/segment-level timestamps) and automatically falls back to the OpenAI Whisper API (whisper-1) when the local engine is not installed. Any agent can call it for meetings, podcasts, voice notes, interviews, or video audio tracks.
Accept and take the next available task from the task queue. Use when an agent is idle and ready to pick up the highest-priority unassigned task. For assigning tasks to specific agents, use assign-task instead.
Register the agent as active with the Crewly backend on startup. Use when an agent first launches and needs to join the team and become visible to the orchestrator. For confirming responsiveness after registration, use heartbeat instead.
Analyze git changes and produce a structured code review with automated checks for missing tests, debug statements, potential secrets, large changes, and dependency modifications. Use when reviewing staged changes, unstaged diffs, recent commits, or branch comparisons before submitting a pull request. For task-level quality gates, use check-quality-gates instead.
Assign a task to a specific agent via the task management system. Use when the orchestrator needs to target a particular agent with a known task ID. For agents self-assigning the next available task, use accept-task instead.
| name | Synthesize Hierarchy |
| description | Plan and create a NESTED team hierarchy (parent coordination team + per-stream child teams) for a complex multi-stream goal. Use INSTEAD of recommend-team/materialize-team when the goal names 2+ parallel work-streams (e.g. frontend + backend + DevOps). Onboarding-only. |
| version | 0.1.0 |
| category | onboarding |
| skillType | claude-skill |
| assignableRoles | ["orchestrator"] |
| triggers | ["synthesize hierarchy","create sub-teams","nested teams","parallel teams"] |
| tags | ["onboarding","hierarchy","sub-teams"] |
| execution | {"type":"script","script":{"file":"execute.sh","interpreter":"bash","timeoutMs":30000}} |
For a COMPLEX goal with 2+ parallel work-streams (e.g. "build a SaaS with a React frontend, a Node backend, and DevOps"), a single flat team is the wrong shape. This skill:
HierarchyPlan — a parent coordination team + one child team per stream.
Nothing is created. Show the plan to the user and get approval first
(a new-team launch is a Commitment — it ALWAYS needs explicit approval).--materialize '<planJSON>'): instantiate the approved
plan — parent team first, then each child team linked via parentTeamId.
All teams are LIVE (real members, prompts, hierarchy) via the same
provisioning path as materialize-team.If the plan comes back with NO children (fewer than 2 streams detected), fall
back to the normal recommend-team → materialize-team flow — one team is
sufficient.
# 1. Plan (pure — show the result to the user for approval):
bash execute.sh --industry "build a SaaS: React frontend, Node API backend, DevOps" --scale small-team
# 2. After the user approves, materialize the exact plan you showed:
bash execute.sh --materialize '<the plan JSON from step 1>'
| Flag | Required | Description |
|---|---|---|
--industry | for plan | Free-text goal/domain description |
--scale | for plan | solo | small-team | company |
--tasks | no | JSON array of {name, tier} tasks |
--max-subteams | no | Branching cap (default 5) |
--materialize | for create | The approved plan JSON — instantiates it |
This skill is callable only when orc is in 'onboarding' mode.