The Status Map skill enhances AI agent transparency by generating human-readable ASCII visualizations of session states. It provides real-time monitoring of agent progress, system health, and task transitions, allowing developers to quickly scan complex multi-agent workflows and debug session history without parsing raw JSON logs.

When should I use status-map?

status-map is useful in the following scenarios: • Real-time Session Monitoring: Use the PULSE or COMPACT templates to track agent progress, git status, and system health during long-running automated tasks. • Error Diagnosis and Debugging: Automatically trigger the ERROR_DEBUG template when a failure occurs to visualize the exact system state and lock status at the moment of impact. • Multi-Agent Orchestration: Generate DELEGATION templates to document context and state transitions when handing off tasks between different AI agents or sub-processes. • Workflow Validation: Utilize the PRE_COMMIT and SESSION_END templates to verify system integrity and rule compliance before finalizing code changes or closing a session.

name	status-map
description	Generate human-readable ASCII status visualizations for agent sessions
version	1.0.0

Status Map Skill

Purpose

Generate ASCII-based visualizations for human observability of AI agent sessions. Complements Sentinel Protocol (JSON-based) by providing quick, scannable status information.

When to Use

Every response (PULSE template)
Every 5 responses (COMPACT template)
Session start/end
Before/after delegations
On errors
Before commits

Template Catalog

Template	Purpose	Time
PULSE	1-line minimal status	1-2s
COMPACT	Quick 6-line check	3-5s
SESSION_START	Initial state	8-10s
SESSION_END	Handoff summary	20-30s
DELEGATION_PRE	Pre-delegation context	5-8s
DELEGATION_POST	Post-delegation result	8-12s
ERROR_DEBUG	Error diagnosis	15-20s
PRE_COMMIT	Commit validation	8-10s
FULL_REPORT	Complete audit	60-120s

Template Examples

PULSE (1-line)

[PULSE] ████████░░ 80% | ✓3 ↻1 ⚠0 | 25m | → Continue editing

COMPACT (6-line)

┌─────────────────────────────────────────────────────────────────┐
│  STATUS MAP | 2026-01-06T12:30 | Session: c614                  │
├────────────┬────────────────────────────────────────────────────┤
│ 🟢 GIT     │ main | clean | last: a31b933                       │
│ 🟢 AGENTS  │ 23 completed | 0 active | 0 blocked                │
│ 🟢 SENTINEL│ v1.0 | 10 rules | health: 100                      │
│ 🟢 LOCKS   │ 0 active | 0 stale                                 │
├────────────┴────────────────────────────────────────────────────┤
│ NEXT: aguardando instrucao do humano                            │
└─────────────────────────────────────────────────────────────────┘

Semaphore Indicators

Indicator	Meaning	Fallback
🟢	OK / Healthy	[OK]
🟡	Warning	[WARN]
🔴	Error / Critical	[FAIL]

Override Commands

Command	Template
`/status`	COMPACT
`/status full`	FULL_REPORT
`/status debug`	ERROR_DEBUG
`/status pre`	PRE_COMMIT
`/status end`	SESSION_END
`/status pulse`	PULSE

Template Inference

The AI automatically selects template based on context:

Session start? → SESSION_START
Error detected? → ERROR_DEBUG
About to delegate? → DELEGATION_PRE
Delegation returned? → DELEGATION_POST
About to commit? → PRE_COMMIT
Session ending? → SESSION_END
Every 5th response? → COMPACT
Default → PULSE

Skill based on Status Map System v1.0 | multi-agent-os

status-map

When & Why to Use This Skill

Use Cases