القائمة
Generate a status report across all workstreams using beads issue tracking. Shows active work, blockers, and available tasks.
التثبيت باستخدام 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 | status |
| description | Generate a status report across all workstreams using beads issue tracking. Shows active work, blockers, and available tasks. |
| argument-hint | ["none"] |
| user-invocable | true |
| allowed-tools | Bash(bd *) |
Generate a comprehensive status report by running these commands:
!bd stats 2>/dev/null || echo "No beads stats available"
!bd list --status=in_progress 2>/dev/null || echo "No in-progress issues"
!bd blocked 2>/dev/null || echo "No blocked issues"
!bd ready 2>/dev/null || echo "No ready issues"
Summarize findings in this format:
[List in-progress issues with assignees]
[List blocked issues and what they're waiting on]
[List ready issues that can be picked up]
[Stats summary — open/closed/blocked counts]
[Suggested next actions based on current state]
