Loading...
Loading...
Found 31 Skills
Use when the workflow feels too complex, has accumulated cruft, or has redundant steps and overlapping tools that need consolidation.
Use when the user wants to tailor a workflow for a specific industry, domain, or vertical with specialized expertise, terminology, and guardrails.
Use when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.
Use when the user wants to push past conventional workflow limits with advanced performance techniques like parallel orchestration, streaming pipelines, or adaptive routing.
Use when the workflow works but needs polish, or as the final step in a diagnose → fix → refine cycle before shipping.
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
Use when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.
Use when deploying to production, handling sensitive data, or the workflow needs safety constraints, input validation, and security boundaries.
Use when starting a new project, adding a new agent to an existing system, or setting up workflow infrastructure from scratch.
Use when a single agent demonstrably cannot handle the task and multi-agent coordination is justified.
Use when the workflow needs multi-step processing with sequential, parallel, or conditional tool compositions and proper data flow.
Use when the agent needs access to information beyond its training data — knowledge sources, RAG pipelines, or grounding data.