Loading...
Loading...
Found 99 Skills
Production ETL patterns orchestrator. Routes to core reliability patterns and incremental load strategies.
Researches topics and trends for blog content with parallel multi-agent execution. USE WHEN orchestrator invokes research phase OR user says 'research topic', 'find trends', 'gather information for blog'.
Deploys a Next.js or Vite project to Vercel, pushes all environment variables from .env.local to production, adds a SPA rewrite rule for Vite, and updates the Supabase site_url to the live domain. Called by the vibe-ship orchestrator.
Turn any record into a shared workspace where agents and humans collaborate. Attach a simple workspace schema to any entity — contacts, companies, deals, projects, tickets — and let any participant contribute updates, tasks, notes, and issues. The record becomes the coordination. No orchestrator, no message bus — just read the workspace, do your work, record what you did. Intelligence accumulates. Use when multiple agents, humans, or systems need to work on the same entity together.
(Industry standard: Routing Agent / Orchestrator Pattern) Primary Use Case: Analyzing an ambiguous trigger and routing it to one of the specific specialized implementations. Routes triggers to the appropriate agent-loop pattern. Use when: assessing a task, research need, or work assignment and deciding whether to run a simple learning loop, red team review, dual-loop delegation, or parallel swarm. Manages shared closure (seal, persist, retrospective, self-improvement).
Autonomously draft and polish chapters through multi-skill editorial passes. Use when you have a complete outline and want to produce a polished first draft with iterative refinement.
Orchestrates full decomposition (scope → Epics → Stories) by delegating ln-210 → ln-220. Sequential Story decomposition per Epic. Epic 0 for Infrastructure.
Expert architectural standards for building scalable Godot applications (Apps, Tools, UI, or Games) using the Composition pattern. Use when designing node structures, refactoring monolithic scripts, or implementing complex behaviors. Enforces "Has-A" relationships over "Is-A" inheritance.
Injects managed chaos into environments to test system resilience. Validates that self-healing and monitoring systems work as expected under stress.
NEVER escalate without investigation first. This is the Iron Law. Use when evaluating whether to escalate models, facing genuine complexity requiring deeper reasoning, novel patterns with no existing solutions, high-stakes decisions requiring capability investment. Do not use when thrashing without investigation - investigate root cause first. DO NOT use when: time pressure alone - urgency doesn't change task complexity. DO NOT use when: "just to be safe" - assess actual complexity instead.
Initialize thread-system files in a fresh directory by creating threads/_template and the minimum repository-native thread templates before any thread advance.
Diagnoses sales needs and sequences appropriate skills for comprehensive deal execution. Use this skill when unsure which sales skill to use, planning multi-step deal strategies, coaching reps on process, or coordinating complex sales motions.