/status

> Show current system state -- active nodes, recent signals, pending items.

170 stars

byMiosa-osa

View on GitHub Installation ↓

Best use case

/status is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

> Show current system state -- active nodes, recent signals, pending items.

Teams using /status should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/status/SKILL.md --create-dirs "https://raw.githubusercontent.com/Miosa-osa/canopy/main/library/skills/operations/status/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/status/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How /status Compares

Feature / Agent	/status	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

> Show current system state -- active nodes, recent signals, pending items.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# /status

> Show current system state -- active nodes, recent signals, pending items.

## Usage
```
/status [--node <name>] [--verbose]
```

## What It Does
Provides a snapshot of the current operating state: active priorities, recent signals, pending action items, and system health. Without arguments, shows a high-level overview. With `--node`, shows detailed status for a specific node.

## Implementation
1. Read `rhythm/today.md` for current priorities.
2. Scan recent signal files (last 7 days) for activity.
3. Check pending action items across all nodes.
4. Run quick health metrics (index size, last reindex time).
5. Report: priorities, recent activity, blockers, system health.

With `--verbose`: include full signal summaries and cross-references.

## Examples
```bash
# System overview
/status

# Status for a specific node
/status --node ai-masters

# Verbose output with full details
/status --verbose
```

## Command