Automation
Task automation and scripting
module-builder
by yalgaeahn
Create new LabOne Q experiment/analysis modules in this repository by grounding design against the installed .venv laboneq_applications contracts before coding. Use when the user asks to add a new workflow/module from scratch, add a new tune-up experiment type, or perform a major interface redesign under experiments/ and analysis/.
ralph-loop
by 101mare
Start an autonomous work loop. Claude keeps working on the given task until it signals completion or the iteration limit is reached. Does NOT handle: prompt building (use ralph-loop-prompt-builder), plan review (use plan-review), code review (use pr-review). Usage: /ralph-loop <task description> Optional: /ralph-loop max=20 <task description> Cancel: delete .claude/ralph-loop.local.md or press Escape/Ctrl+C
async-python-patterns
by ma1orek
Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations.
engineer-work
by elliottrjacobs
Execute implementation plans with git branching, progress tracking, quality checks, and PR creation. Use when the user says "build this", "implement this", "start working", "execute the plan", or provides a plan file to execute.
workflow-local-dev
by lgariv-dn
Support local workflow platform development in the DAP workspace across frontend, backend, and infra teams. Provides access to Kubernetes (Kind), Tilt service management, database queries, and troubleshooting. Use when building backend/API features, adjusting infra configurations, checking logs, running tests, or debugging issues against locally deployed workflow engine components.
ralph-loop-prompt-builder
by 101mare
Builds effective prompts for the Ralph Loop autonomous work system. Asks clarifying questions about the task, then generates a structured prompt with clear requirements, verification steps, and completion criteria. Does NOT handle: loop execution (use ralph-loop), general prompts (use prompt-builder). Use this BEFORE starting a ralph-loop — it creates the prompt, not the loop itself. Recognizes: "ralph-loop-prompt-builder", "ralph prompt", "build ralph prompt", "prepare a ralph loop task", "help me write a ralph loop prompt", "structure this for ralph-loop"
aico-code-review
by yellinzero
Request structured code review to catch correctness, security, performance, and readability issues. Reviews should happen early and often. Use this skill when: - Completing a task and need quality check - After major feature implementation - Before merging to main branch - When stuck and need fresh perspective on code - User asks for "code review", "review my code", "check my code" - Subagent-driven workflow needs spec compliance or quality review Review categories: Correctness, Tests, Security, Performance, Readability, Error Handling Severity levels: Critical (fix now), Important (fix before proceeding), Minor (note for later)
kanban
by lambda610
"异步任务管理系统。用于：(1) 添加任务到 inbox，(2) 查看任务进度，(3) 处理 backlog。触发方式：用户说'添加任务'/'task add'/'kanban'或类似表达。注意：只写 inbox，不立即执行任务。Not for: 需要立即执行的任务。"
cloudflare-agents
by ma1orek
Build AI agents with Cloudflare Agents SDK on Workers + Durable Objects. Provides WebSockets, state persistence, scheduling, and multi-agent coordination. Prevents 23 documented errors. Use when: building WebSocket agents, RAG with Vectorize, MCP servers, or troubleshooting "Agent class must extend", "new_sqlite_classes", binding errors, WebSocket payload limits.
testcontainers-integration-tests
by baotoq
Write integration tests using TestContainers for .NET with xUnit. Covers infrastructure testing with real databases, message queues, and caches in Docker containers instead of mocks.
detect-python-command
by drillan
現在の環境で適切なPythonコマンドを判別し、スクリプトを実行します。「Pythonコマンドを確認」「どのpythonを使う」「Python実行方法」といった依頼や、他のスキルからPythonスクリプトを実行する前に使用してください。
aico-pm-story-acceptance
by yellinzero
Verify and close stories after frontend/backend tasks are completed. Check ALL related task files, update story acceptance criteria checkboxes. UNIQUE VALUE: Ensures BOTH frontend AND backend tasks are verified before closing story. Prevents premature story closure. Use this skill when: - Frontend or backend notifies "task completed, please verify" - User asks to "verify story", "accept story", "close story", "mark story done" - Need to check if a story can be marked as complete - User asks "is story X done?", "can we close story X?" CRITICAL: Must check BOTH frontend tasks (docs/reference/frontend/tasks/) AND backend tasks (docs/reference/backend/tasks/) before closing. Output: Update story file checkboxes from - [ ] to - [x]
product-customer-discovery
by piperubio
Plan and run product-focused customer discovery interviews and synthesize actionable customer insights. Use when you need to define discovery goals/hypotheses, identify an ICP/segments, create a recruiting plan, write an interview guide, conduct interviews, analyze notes (themes, JTBD, pains/gains), and produce a discovery readout with opportunities, risks, and next experiments.
aico-subagent-driven
by yellinzero
Execute implementation plan by dispatching fresh subagent per task. Each task gets: Implementer → Spec Review → Quality Review. Two-stage review ensures both correctness and quality. Use this skill when: - Have implementation plan with multiple independent tasks - Want automated execution with quality gates after each task - Tasks are mostly independent (not tightly coupled) - User asks to "execute the plan", "run the tasks", "auto implement" Prerequisites: Must have plan from aico-frontend-plan, aico-backend-plan, or aico-*-task-breakdown skill. Process: For each task: Dispatch Implementer → Spec Review (passes?) → Quality Review (passes?) → Next task Review order: ALWAYS spec compliance first, THEN code quality.
spec
by MartinNevlaha
"Spec-driven development coordinator (plan→implement→verify→learn). Orchestrates work by delegating to specialized agents."
git-trunk-based-workflow
by octivi
Plan and execute Git Trunk-Based Development workflows on a repository with main as trunk. Use whenever the user asks about branch strategy, branch naming, rebasing on main, merge conflicts during rebase, PR flow, merge strategy, safe history rewrite, or branch cleanup, even if they do not mention "trunk-based" explicitly. For commit message formatting and Conventional Commits wording, delegate to git-commits.
recursive-handoff
by SebastiaanWouters
"Execute the same task repeatedly with clean context via handoff. Triggers on: recursive loop, repeat until, keep doing until, loop until done. REQUIRES a finish condition to stop."
agentdocs-orchestrator
by Await-d
Advanced task orchestration system integrated with agentdocs knowledge management. Decomposes complex requests into atomic tasks, auto-creates workflow planning documents, manages multi-agent parallel execution, and syncs task status. Use when handling complex multi-step tasks, parallel execution needs, or sub-agent orchestration.
aico-backend-plan
by yellinzero
Create or enhance backend tasks with detailed implementation steps. Supports TWO modes: MODE A: Enhance existing task (add detailed steps to task in file) MODE B: Create new standalone task file (can contain single or multiple tasks) IMPORTANT: This skill creates MICRO-LEVEL atomic steps, NOT macro architecture plans. For architecture planning or feature scoping, use EnterPlanMode instead. Use this skill when: - Running /backend.plan command - User asks for "atomic steps", "step-by-step plan with verification" - Have a specific task and need implementation steps - User wants to create a standalone task file (not from story) - Need granular steps: Types → DB → Repository → Service → API → Tests DO NOT use for: - Architecture planning (use EnterPlanMode) - General development planning - Feature scoping or estimation Output: - MODE A: Update specific task section in file with Implementation Steps - MODE B: Create new standalone-{name}.md file with one or multiple tasks
engineer-plan
by elliottrjacobs
Create structured implementation plans using parallel research agents. Use when the user says "plan this", "create a plan", "implementation plan", or after completing a tech spec. Breaks specifications into ordered, actionable tasks with effort estimates.
forge-party
by fwehrling
FORGE Orchestrator — Launches 2-3 agents in parallel on a topic for multi-agent collaboration. Usage: /forge-party "topic"
nvr-list
by cadrianmae
This skill should be used when the user asks to "list neovim instances", "show all nvim", "what neovim processes are running", "list all editors", "show all active neovim", or wants to see all running neovim instances across all projects.
app-audit
by chen-ye
Analyzes installed Termux packages and Android apps to identify redundancies, categorize usage, and suggest cleanups. Use when the user asks to audit apps, check for bloatware, or analyze installed software.
astro
by SebastiaanWouters
Build, migrate, debug, and optimize Astro projects using current official patterns. Use when requests mention Astro, .astro files, astro.config.*, create-astro, astro add, content collections (astro:content), image optimization (astro:assets), adapters/SSR, or content-heavy sites including blogs with Markdown/MDX, RSS, and sitemap needs.