Loading...
Loading...
Found 56 Skills
Use the `date` command via Bash tool whenever you or the user mention time, dates, or temporal concepts. Verify current date/time before ANY temporal response, as environment context may be outdated. Parse expressions like "tomorrow", "next week", "3 days", "in 2 weeks", "next Monday at 3pm". Proactively invoke for deadlines, schedules, time-sensitive tasks, week numbers, or any date/time reference.
Use when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows.
Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.
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 user wants to push past conventional workflow limits with advanced performance techniques like parallel orchestration, streaming pipelines, or adaptive routing.
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
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.
Use when the workflow needs to self-correct, improve over time, or establish feedback loops and evaluation cycles.