getpaseo
Official@getpaseo
Paseo provides multi-agent coordination and iterative verification frameworks for complex task execution and inter-agent communication management.
Agent Skills by getpaseo
Showing 11 vetted skills indexed across 1 GitHub repositories.
release-beta
Executes the documented beta release workflow for the Paseo project.
release-stable
Cuts a stable Paseo release by patching, minor bumping, or promoting from beta.
paseo-help
Diagnose Paseo setup, connectivity, provider, and update issues using current documentation.
paseo-plugin
Build, install, and manage trusted local Paseo plugins with React Native surfaces and RPC handlers.
paseo-advisor
Launches a single Paseo agent to give a second opinion on the current task.
paseo-orchestrate
Orchestrate end-to-end task delivery with Paseo agents via MCP tools.
paseo-loop
Automate iterative worker-verifier cycles with the Paseo daemon.
paseo
Coordinate Paseo agent operations via CLI for task execution and monitoring.
paseo-committee
Coordinate two AI agents to plan complex problems with root-cause analysis.
paseo-handoff
Transfers tasks between agents, preserving metadata via Rocket.Chat's API.
paseo-chat
Manage agent communication in Paseo chat rooms via the CLI.
Frequently Asked Questions About getpaseo
FAQPage SchemaWhat specific tasks does Paseo enable?▼
Paseo enables multi-agent coordination, iterative verification cycles, and complex problem decomposition. It facilitates root-cause analysis through committee-based planning and manages stateful task transfers between distributed entities while maintaining metadata integrity across communication channels.
Which personas benefit from using Paseo?▼
Paseo is designed for systems architects and engineers focused on distributed task management and multi-entity coordination. It is ideal for developers building complex, multi-step problem-solving architectures that require rigorous verification and structured communication between distinct processing units.
What are the prerequisites for running Paseo?▼
Paseo requires an environment configured for MCP-compliant operations and Rocket.Chat connectivity for metadata persistence. Users must ensure their environment supports daemon-based execution for iterative cycles and has the necessary permissions to manage inter-entity communication rooms.