Loading...
Loading...
Found 8,783 Skills
Guides engineering of multi-agent systems—agent roles and specialization, orchestration topologies (supervisor, peer-to-peer, hierarchical, blackboard), task decomposition and routing, inter-agent messaging (A2A-style patterns), shared vs partitioned state, fan-out/fan-in and DAG workflows, synchronization and consensus, conflict resolution, fault tolerance and retries across agents, cost/latency/token budgets, cross-agent observability, testing multi-agent flows, and deployment (queues, durable workflows). Framework-agnostic; high-level LangGraph, Deep Agents, and agenthub—not single-agent loops (agentic-ai-developer), ML training (ai-engineer), strategy-only whiteboard (enterprise-strategist), or PM planning (technical-program-manager). Use for multi-agent system, multi-agent engineer, agent orchestration, supervisor agent, agent topology, fan-out fan-in, agent handoff protocol, multi-agent workflow, agent coordination, blackboard pattern, hierarchical agents, A2A, agent DAG, multi-agent architecture.
Bump a pinned dependency (TransformerEngine, Megatron-LM, NRX, etc.), regenerate the lockfile, open a PR, and drive it to green by attaching a watchdog to the "CICD NeMo" workflow and quarantining failing functional tests as flaky until the run is green.
Brev instance operating guidance for NeMo-RL agents working in /home/ubuntu/RL with limited workspace disk, a larger /ephemeral volume, and optional /home/ubuntu/RL/.env secrets. Use when running auto-research campaigns, experiments, training jobs, model or dataset downloads, shared cache-heavy commands, log-producing runs, checkpoint generation, W&B or Hugging Face authenticated workflows, or any workflow that may create large files on Brev.
Use when writing or modifying Python code that imports `genoray` to read genotypes/dosages from VCF, PGEN, or SparseVar (`.svar`) files. Covers the public API surface, mode constants, range queries, chunking, filtering, and the SparseVar workflow. Skip for unrelated bioinformatics work.
Placekey integration. Manage data, records, and automate workflows. Use when the user wants to interact with Placekey data.
Marketstack integration. Manage data, records, and automate workflows. Use when the user wants to interact with Marketstack data.
CDR Platform integration. Manage data, records, and automate workflows. Use when the user wants to interact with CDR Platform data.
DealerSocket integration. Manage data, records, and automate workflows. Use when the user wants to interact with DealerSocket data.
Simplicate integration. Manage data, records, and automate workflows. Use when the user wants to interact with Simplicate data.
Design background Data Atlas style agents for Itô basket research, market discovery, parameter drafting, and human-in-the-loop editing. Use for architecture and workflow planning, not live order execution.
Write dense storyboard-grid prompts for short-form image or previsualization workflows. Use this when a generation controller needs a 6-9 panel grid with hook logic, visible actions, product timing, and negative constraints before image or video request architecture.
Route generative media requests before any creative planning or provider execution. Use this when the user asks to generate, modify, dub, animate, or assemble image, video, audio, workflow, or analysis-derived media and the first decision is which generation controller should own the job.