thrum-overview

Consolidate identity, team presence, inbox, and sync status into one overview.

28|5|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/leonletto/thrum --skill thrum-overview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: thrum-overview
Source: https://github.com/leonletto/thrum/tree/main/codex-plugin/skills/thrum-overview
Command: npx skills add https://github.com/leonletto/thrum --skill thrum-overview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates identity, team presence, inbox messages, and sync status into a single, easy-to-scan view, reducing context-switching and coordination overhead.

Core Features & Use Cases

  • Unified status overview: presents identity, active team members, unread inbox messages, and synchronization health in one place.
  • Cross-workspace coordination: helps teams across worktrees stay aligned by surfacing global and per-worktree states.
  • Operational readiness: provides both human-readable summaries and machine-friendly outputs for automation contexts.

Quick Start

Run thrum overview to display the current identity, team, inbox, and sync status.

Frequently Asked Questions about thrum-overview

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

FAQPage Schema
How do I get a unified overview of team presence, inbox messages, and sync status?

You can generate a unified overview by running the thrum overview command, which consolidates identity, active team members, unread inbox messages, and synchronization health into a single snapshot.

What is the best way to check identity and synchronization state across multiple worktrees?

To check synchronization state across worktrees, you need a tool that surfaces both global and per-worktree conditions, allowing teams operating across different workspaces to stay aligned and monitor operational readiness.

Does the thrum overview command support machine-readable outputs for automation?

Yes, the thrum overview command supports machine-readable outputs, enabling integration with automation contexts while also providing human-readable summaries for quick status checks.

Can I use a single command to monitor cross-workspace coordination and unread inbox messages?

Yes, you can monitor cross-workspace coordination and unread inbox messages simultaneously by generating a holistic status snapshot that integrates the underlying team, inbox, and sync subsystems into one view.

Why do I need a consolidated status snapshot instead of checking team, inbox, and sync subsystems individually?

You need a consolidated status snapshot to eliminate the need to check team, inbox, and sync subsystems individually, reducing context-switching and coordination overhead when managing agents and worktrees.