status

Summarize boot health, agent schema, hydrogen targets, fleet, open work, and unpushed changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/rudi193-cmd/Aionic-Claude-Skills --skill status-rudi193-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/rudi193-cmd/Aionic-Claude-Skills/tree/main/skills/status
Command: npx skills add https://github.com/rudi193-cmd/Aionic-Claude-Skills --skill status-rudi193-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a fast, read-only snapshot of the system's health and status without performing any writes, enabling quick assessments.

Core Features & Use Cases

  • Boot health status derived from boot_status
  • Agent schema: atom count, edge count, and the ratio vs target
  • Hydrogen targets: shell progress against target benchmarks
  • Fleet availability: providers and last response time
  • Open work: top priorities from ganesha.open_work
  • Unpushed changes: uncommitted changes across repos
  • Session delta: atoms written, atoms archived, edges created during the session

Quick Start

Trigger a quick, read-only status snapshot to review boot health, agent schema, hydrogen targets, fleet, open work, and unpushed changes.

Frequently Asked Questions about status

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

FAQPage Schema
How do I get a read-only system health snapshot without triggering writes?

A read-only system health snapshot summarizes boot health, agent schema, fleet availability, and unpushed changes without performing any writes. It queries internal status sources to provide a quick assessment of current system conditions.

What metrics are included in a system status snapshot?

A system status snapshot includes boot health, agent schema atom and edge counts, hydrogen target progress, fleet provider availability, open work priorities, unpushed changes, and session delta metrics like atoms written and archived.

How do I check unpushed changes and boot health across my environment?

Checking unpushed changes and boot health requires querying boot_status and repository sources directly. The snapshot aggregates uncommitted changes across repos alongside boot health to highlight pending work and system stability.

Can I review agent schema edge counts and fleet availability in a single view?

Reviewing agent schema edge counts and fleet availability in a single view is supported by the status snapshot. It aggregates agent schema ratios against targets and fleet provider last response times into one summarized report.

Does generating a status snapshot require write access to internal sources?

Generating a status snapshot requires read-only access to internal sources like boot_status, agent schema, hydrogen targets, fleet, ganesha.open_work, and unpushed changes. It strictly avoids write operations to ensure safe system assessments.

What is the best way to monitor session delta and open work priorities?

Monitoring session delta and open work priorities is best handled by a read-only status snapshot. It tracks atoms written, atoms archived, edges created during the session, and extracts top priorities from ganesha.open_work.