swarm_query

Aggregate read-only swarm health and task status across projects.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/ollieb89/openrepo --skill swarm-query
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarm_query
Source: https://github.com/ollieb89/openrepo/tree/main/agents/clawdia_prime/skills/swarm_query
Command: npx skills add https://github.com/ollieb89/openrepo --skill swarm-query

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides the L1 orchestrator (ClawdiaPrime) with essential read-only visibility into the operational status of all projects within the swarm, enabling effective monitoring and bottleneck detection without interfering with ongoing operations.

Core Features & Use Cases

  • Swarm Overview: Get an aggregated view of active, queued, completed, and failed tasks across all projects.
  • Project-Specific Status: Drill down into the details of any single project, including task lists and container status.
  • Stalled Task Identification: Proactively find tasks that have become stuck or inactive, allowing for timely intervention.
  • Health Scoring: Monitor the overall health of each project to identify potential issues before they escalate.
  • Use Case: As an L1 orchestrator, you can quickly check the overall health of your AI swarm, identify which projects are experiencing delays or failures, and drill down to understand the root cause of any bottlenecks.

Quick Start

Ask for an overview of the entire swarm's status.

Frequently Asked Questions about swarm_query

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor swarm health and task status across multiple projects?

You can monitor swarm health by aggregating read-only state data across all projects to view active, queued, completed, and failed tasks. This provides cross-project visibility without modifying ongoing operations.

What is the best way to detect stalled tasks and bottlenecks in an AI swarm?

Detecting bottlenecks involves querying project status to proactively identify tasks that have become stuck or inactive. You can drill down into individual project details to understand the root cause of delays.

Can I check project status concurrently without interfering with active orchestration operations?

Yes, you can safely check project status concurrently using shared locks (LOCK_SH). This read-only approach ensures safe concurrent access without modifying the swarm state or interfering with ongoing tasks.

How does health scoring work for swarm orchestration monitoring?

Health scoring works by aggregating operational status data to monitor the overall health of each project. This allows you to identify potential issues and stalled tasks before they escalate into major failures.

How do I prevent state file thrashing when querying swarm status frequently?

You prevent state file thrashing by utilizing a time-to-live (TTL) cache when querying swarm status. This caching mechanism reduces continuous disk reads during frequent health monitoring and bottleneck detection.