ally-status

Monitor daemon state and pending ally messages via MCP functions.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/dotBeeps/hoard --skill ally-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ally-status
Source: https://github.com/dotBeeps/hoard/tree/main/cc-plugin/skills/ally-status
Command: npx skills add https://github.com/dotBeeps/hoard --skill ally-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitor the daemon state and any pending ally messages to surface current health and activity.

Core Features & Use Cases

  • Check attention state of running allies and the storybook-daemon.
  • Drain pending stone messages to fetch progress from Allies.
  • Register a session to inform the daemon of a connected client.
  • Use to diagnose stalled quests or verify MCP connectivity.

Quick Start

Check the current status of your allies and daemon, and confirm the MCP connection is live.

Frequently Asked Questions about ally-status

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

FAQPage Schema
How do I monitor daemon health and check ally status in an active MCP session?

Diagnosing stalled quests involves checking the attention state of running allies and draining pending stone messages to fetch progress. This surfaces whether the daemon is active or if the session has disconnected and needs registration.

What is the best way to verify MCP connectivity and confirm an active session is registered?

To verify MCP connectivity, register a session to inform the daemon of a connected client. This confirms your active session is registered and allows the daemon to track the connection and report ally activity accurately.

How do I drain pending stone messages to fetch progress updates from allies?

Draining pending stone messages fetches progress updates from allies by pulling queued data from the daemon. This process surfaces pending communications and verifies that ally reports are being transmitted correctly through the MCP connection.

Why does my ally report show stalled progress during an active daemon session?

Stalled progress in an ally report during an active daemon session indicates a connectivity issue or an unregistered client. Checking the attention state and draining pending stone messages helps diagnose whether the daemon is actively receiving progress updates.

Can I use this to diagnose stalled quests without additional dependencies?

Yes, you can diagnose stalled quests without additional dependencies. The monitoring functions operate natively through MCP to surface daemon state and pending ally messages, requiring no external components to verify active sessions or connectivity.