Loading...
Loading...
Found 36 Skills
Symptom-based background task troubleshooting - decision trees for 'task never runs', 'task terminates early', 'works in dev not prod', 'handler not called', with time-cost analysis for each diagnosis path
Implement robust background job processing with dead letter queues, retries, and state machines. Use when building async workflows, scheduled tasks, or any work that shouldn't block the request/response cycle.
Manage concurrent background workers with scheduling, dependencies, health monitoring, and automatic disabling of failing workers.
This skill should be used when the user asks to "run npm test after 30 minutes", "git commit after 1 hour", "wait 2h then deploy", "sleep 45m and run build", "after 10m run prettier", or provides a duration followed by a shell command to execute later.
Expert-level Apache Airflow orchestration, DAGs, operators, sensors, XComs, task dependencies, and scheduling
Only to be triggered by explicit super-swarm commands.
Use when facing 2 or more independent tasks that can be completed without shared state or sequential dependencies
Generate an energy-optimized, time-blocked daily plan
Decompose work into well-sized, well-ordered implementation units and plan each one thoroughly. Use when the user asks to "plan this implementation", "break this into steps", "help me plan the work", "decompose this into tasks", "create an implementation plan", "how should I break down this project", or "size this work".
Generate an onboarding checklist and first-week plan for a new hire. Use when someone has a start date coming up, building the pre-start task list (accounts, equipment, buddy), scheduling Day 1 and Week 1, or setting 30/60/90-day goals for a new team member.
Enables agents to register, manage, and execute scheduled tasks using OS native scheduler (crontab for Linux/WSL, launchd for macOS). No git, no dangerous flags, no session dependency. Tasks run headless, output to log files, user reads when ready. Use this skill when: - User wants to schedule recurring tasks with natural language - User mentions "every day at", "cada hora", "schedule", "programar", "automatizar" - User needs tasks to run without open session (headless) - User wants OS-level scheduling (crontab/launchd) - User mentions "cada minuto durante la próxima hora" or temporal intervals ACTIVATE when user mentions: "schedule", "programar", "cron", "cada día", "every hour", "automate", "tarea programada", "ejecutar automáticamente", "recordatorio", "cada minuto durante", "durante la próxima", "intervalo", "task scheduler", "opencode headless", "kiro scheduled", "background task", "tarea en segundo plano" DO NOT USE for: git operations, dangerous permissions, MCP sampling dependency.
OpenCode Multi-Agent Parallel Collaboration Configuration. Supports multiple agents working simultaneously to implement a pipeline development mode. Use when: (1) Need multiple agents to work in parallel (2) Need a master to schedule collaborative work among agents (3) Need to implement a standardized process of design → development → acceptance → testing (4) Need to configure OpenCode's multi-agent collaboration capability