一键导入
helm
Evaluate current system state and recommend phase transitions. Reads phase state, canary signals, beads issues, and git activity to make steering decisions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Evaluate current system state and recommend phase transitions. Reads phase state, canary signals, beads issues, and git activity to make steering decisions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Source and independently verify candidates for a role from a job description URL. Runs the source-candidates workflow (Webset creation → Exa verification of every claim → validated/rejected CSVs). Use whenever the user wants to find candidates, source people for a role, run a recruiting search from a job posting, or invokes /source-candidates.
Verify a webset item's enrichments against public data using independent Exa searches. Returns structured verdict with confidence score, evidence, and discrepancies. Use when a channel event or workflow step requires enrichment verification before proceeding.
Produce uniform, verified background reviews / biographies / profiles for a SHORTLIST of entities (people or companies) by dispatching one research subagent per entity in parallel, then synthesizing and persisting the results. Use when the user asks for "bios", "background reviews", "profiles", "tell me about each of these", or a comparison across several candidates — especially after a [[websets-secondary-review]] produced a shortlist. For a single entity use [[deep-research-item]] instead; this is the parallel, many-entities harness.
Run comprehensive research on an entity — news, funding, tech stack, buyer mapping, angle building. Writes findings to the webset store and optionally to Airtable. Use after verification passes or when a channel event requires deep research on a specific entity.
View, add, modify, or remove per-source workflow configurations. These configs control how channel events are routed to workflow chains. Manages data/workflow-configs.json.
Build Claude Code Channels — MCP servers that push events into a live Claude Code session so Claude can react to things happening outside the terminal. Use this skill whenever the user wants to: build a custom channel server, push webhooks/CI alerts/monitoring events into Claude Code, build a two-way chat bridge (Telegram, Discord, or custom), relay tool-use permission prompts remotely, understand the channel notification protocol, declare the claude/channel or claude/channel/permission capability, wire up sender gating/allowlists, or package a channel as a plugin. Trigger on any mention of Channels, channel MCP, push events to Claude Code, Claude Code from phone, or remote control Claude Code.
| name | helm |
| description | Evaluate current system state and recommend phase transitions. Reads phase state, canary signals, beads issues, and git activity to make steering decisions. |
| argument-hint | ["none"] |
| user-invocable | true |
| allowed-tools | Bash(bd *), Bash(git log*), Bash(git status*), Bash(cat *), Read |
Evaluate the current system state and recommend whether to stay in the current phase or transition.
Read current phase:
!cat .claude/state/system_phase.json 2>/dev/null || echo '{"phase": "exploration"}'
Read canary signals:
!cat .claude/state/canary_signals.json 2>/dev/null || echo '{"pressure": 0}'
Read beads state:
!bd stats 2>/dev/null || echo "No beads stats"
!bd list --status=in_progress 2>/dev/null || echo "No in-progress issues"
!bd blocked 2>/dev/null || echo "No blocked issues"
Read recent git activity:
!git log --oneline -5 2>/dev/null || echo "No recent commits"
Based on the gathered state, evaluate against these transition criteria:
exploration → convergence:
convergence → execution:
execution → completion:
## Helm Assessment
### Current Phase: [phase]
**Entered:** [when]
**Reason:** [why we're in this phase]
### System State
- Canary pressure: [X%]
- In-progress issues: [N]
- Blocked issues: [N]
- Recent activity: [summary]
### Phase Transition Evaluation
[Which transition criteria are met/unmet]
### Recommendation
**[STAY | TRANSITION to X]**
Rationale: [why]
### Active Topology
Primary: [which agents/skills should be most active]
Secondary: [available but not primary]
Dormant: [should not be invoked unless explicitly needed]
If recommending a transition AND the user approves, update the phase state file:
cat > .claude/state/system_phase.json << 'EOF'
{
"phase": "[new_phase]",
"transitioned_at": "[ISO timestamp]",
"reason": "[rationale]",
"canary_pressure": [current_pressure],
"active_topology": ["[primary agents]"]
}
EOF
Do NOT update the phase file without user confirmation. Present the recommendation and wait.