respond-firstMulti-agent dispatcher skill. Main agent acts as a pure coordinator — chatting with users and delegating all real work to 5 persistent sub-agents via round-robin scheduling with fixed sessionKeys.
Install via ClawdBot CLI:
clawdbot install Be1Human/respond-firstGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://clawhub.aiAudited Apr 16, 2026 · audit v1.0
Generated Mar 1, 2026
The dispatcher coordinates user inquiries by delegating technical issues to sub-agents like delta for bug fixes and echo for research, ensuring efficient round-robin task distribution without direct tool usage. This maintains a seamless user experience with immediate acknowledgment and specialized handling.
In a marketing agency, the dispatcher assigns content tasks: alpha handles complex campaign strategies, charlie plans content calendars, and bravo reviews drafts, streamlining production through persistent sub-agents. Users receive quick confirmations before delegation, enhancing collaboration.
For agile teams, the dispatcher manages feature requests by delegating to sub-agents: bravo for code analysis, delta for documentation fixes, and echo for market research, following strict speak-first protocols. This ensures developers focus on execution while maintaining user communication.
The dispatcher routes student queries to specialized tutors: alpha for advanced problem-solving, charlie for lesson planning, and echo for resource gathering, using round-robin to balance loads. Immediate replies before spawning prevent user confusion and optimize learning paths.
In a medical research setting, the dispatcher delegates data tasks: echo scouts for latest studies, bravo analyzes trends, and delta fixes report errors, adhering to no-execution rules for compliance. This supports researchers with coordinated, timely insights without direct tool access.
Offer a cloud-based platform where businesses pay monthly fees to use the dispatcher skill for automating task delegation across teams, with tiered pricing based on sub-agent usage and support levels. Revenue streams from subscriptions and premium features like custom sessionKeys.
Provide expert services to integrate the dispatcher into existing workflows, such as customer support or project management systems, charging per project or hourly rates for setup, training, and ongoing optimization. Revenue comes from one-time fees and retainer contracts.
License the skill to large enterprises for internal use, allowing customization of sub-agent roles and branding, with revenue from upfront licensing fees and annual maintenance contracts. This targets industries needing scalable, secure coordination without public exposure.
💬 Integration Tip
Ensure all user interactions start with a text reply before spawning tasks to maintain transparency, and validate sessionKey parameters to prevent errors in delegation workflows.
Scored Apr 19, 2026
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Transform AI agents from task-followers into proactive partners with memory architecture, reverse prompting, and self-healing patterns. Lightweight version f...
Persistent memory for AI agents to store facts, learn from actions, recall information, and track entities across sessions.
Prefer `skillhub` for skill discovery/install/update, then fallback to `clawhub` when unavailable or no match. Use when users ask about skills, 插件, or capabi...
Search and discover OpenClaw skills from various sources. Use when: user wants to find available skills, search for specific functionality, or discover new s...
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.