Loading...
Loading...
Found 254 Skills
Bidirectional agent team communication via the meet-ai chat server. Agents send and receive messages through the CLI, visible in the web UI.
Multi-instance (Multi-Agent) orchestration workflow for deep research: Split a research goal into parallel sub-goals, run child processes in the default `workspace-write` sandbox using Codex CLI (`codex exec`); prioritize installed skills for networking and data collection, followed by MCP tools; aggregate sub-results with scripts and refine them chapter by chapter, and finally deliver "finished report file path + key conclusions/recommendations summary". Applicable to: systematic web/data research, competitor/industry analysis, batch link/dataset shard retrieval, long-form writing and evidence integration, or scenarios where users mention "deep research/Deep Research/Wide Research/multi-Agent parallel research/multi-process research".
Guide for orchestrating Claude Code agent teams — multiple parallel Claude Code sessions coordinated by a team lead. Use this skill when the user mentions agent teams, teammates, parallel agents, multi-agent workflows, spawning agents, coordinating agents, delegate mode, plan approval for teammates, TeammateIdle or TaskCompleted hooks, or wants to break a task into parallel independent work streams. Also trigger on questions about tmux split-pane mode, in-process teammate mode, Shift+Up/Down agent switching, shared task lists, inter-agent messaging, or designing tasks for multi-agent decomposition. This is an experimental feature requiring CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS to be enabled.
Use when performing ralph wiggum style long-running development loops with pacing control.
This skill should be used when the user mentions "openclaw", "OpenClaw CLI", asks to "send a message via openclaw", "manage openclaw agents", "configure openclaw gateway", "check openclaw status", "run openclaw agent", or asks about OpenClaw setup, channels, devices, or messaging automation.
Autonomous multi-agent task orchestration with dependency analysis, parallel tmux/Codex execution, and self-healing heartbeat monitoring. Use for large projects with multiple issues/tasks that need coordinated parallel execution.
This skill should be run only when the user explicitly invokes it. Orchestrates end-to-end task implementation — understands the task, assesses complexity, implements directly or via a team of subagents for complex work, and always finishes with a code-polish pass.
Intelligently routes user requests to the most appropriate Claude Code skill. ALWAYS use this skill FIRST when user asks for help, mentions "skill", "which", "how to", or seems unsure about which approach to take. This is the default entry point for all skill-related requests.
Only to be triggered by explicit super-swarm commands.
Use when "CrewAI", "multi-agent systems", "agent orchestration", "AI crews", or asking about "autonomous agents", "agent collaboration", "role-based agents", "agent workflows", "AI team coordination"
Expert system for designing and architecting AI agent workflows based on proven Meta methodologies. Use when users need to build AI agents, create agent workflows, solve problems using agentic systems, integrate multiple tools into agent architectures, or need guidance on agent design patterns. Helps translate business problems into structured agent solutions with clear scope, tool integration, and multi-layer architecture planning.
Orchestrate in-session Task tool teams for parallel work. Fan-out research, implementation, review, and documentation across subagents. Use when: parallel tasks, fan-out, subagent team, Task tool, in-session agents.