Loading...
Loading...
Found 23 Skills
Mandatory protocol for dispatching any built-in and custom agent in this project via the task tool. Use this skill EVERY TIME you are about to call the task tool with a custom agent_type. This skill ensures the agent's intended model (declared in its YAML frontmatter) is respected rather than overridden by a default. Also encodes prompting best practices for subagent context and quality. ALWAYS invoke before any task tool call that targets a custom agent — even if the agent name seems obvious.
Use when facing 2 or more independent tasks that can be completed without shared state or sequential dependencies
Use when facing 3+ independent failures that can be investigated without shared state or dependencies - dispatches multiple Claude agents to investigate and fix independent problems concurrently
Dispatches one subagent per independent domain to parallelize investigation/fixes. Use when you have 2+ unrelated failures (e.g., separate failing test files, subsystems, bugs) with no shared state or ordering dependencies.
Dispatch a swain artifact to a GitHub Actions runner for autonomous implementation via Claude Code Action. Creates a GitHub Issue with the artifact content and triggers the workflow for background execution. Use when the user says 'dispatch', 'send to background agent', 'run this autonomously', 'GitHub Actions', or wants to hand off a SPEC for autonomous implementation.
Use when user wants to find a note to publish as a blog post. Triggers on「选一篇笔记发博客」「note to blog」「写博客」「博客选题」. Scans Obsidian notes via Python script, evaluates blog-readiness, supports batch selection with fast/deep dual-track and parallel Agent dispatch.
Interactive agent picker for composing and dispatching parallel teams
LangGraph supervisor-worker pattern. Use when building central coordinator agents that route to specialized workers, implementing round-robin or priority-based agent dispatch.
Dispatch independent subagents in parallel for unrelated problems spanning different subsystems. Use when 2+ failures have independent root causes, multiple subsystems are broken independently, or user requests concurrent investigation. Use for "parallel", "multiple failures", "independent bugs", "fix these concurrently". Do NOT use for related failures, shared-state problems, or exploratory debugging where root cause is unknown.
Use when an approved plan exists and needs execution, or when a hotfix/one-sentence scope needs direct TDD implementation — dispatches subagents per task, validates, reports
Use when dealing with 2 or more tasks that can be performed independently, with no shared state or sequential dependencies
Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task, reviews once per phase, loads phases just-in-time to minimize context usage