Run any Skill in Manus with one click

Get Started

thrum

Stars28

Forks6

UpdatedJune 9, 2026 at 23:24

Main Thrum entry point for multi-agent coordination, messaging, session context, and command routing in Codex.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

leonletto

leonletto/thrum

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

10 files

SKILL.md

readonly

name	thrum
description	Main Thrum entry point for multi-agent coordination, messaging, session context, and command routing in Codex.

Thrum

Use this as the main Thrum skill in Codex. It is the umbrella entry point for multi-agent coordination, command selection, and message-routing decisions.

Use this when

Work must coordinate across agents, worktrees, or sessions.
You need to choose the right Thrum workflow before acting.
The request spans multiple Thrum commands rather than one narrow operation.

Command Skills

Codex registers the Claude plugin command surface as top-level skills:

thrum-prime
thrum-overview
thrum-update-project
thrum-team
thrum-inbox
thrum-send
thrum-reply
thrum-wait
thrum-restart
thrum-load-context
thrum-quickstart
thrum-configure-roles
thrum-project-setup

Use those when the user explicitly asks for one command. Use thrum when you need judgment across commands.

Core workflow

Prime context with thrum prime and capture identity, team, inbox, and sync health.
Decide whether the task is messaging, triage, session lifecycle, role setup, or project decomposition.
Route into the matching thrum-* command skill when the next step is command-specific.
Keep scope explicit: branch, worktree, files, intended audience, and expected output.
Re-arm a listener or tmux session pattern when continuous monitoring matters.

Command baseline

thrum prime
thrum overview
thrum team
thrum inbox --unread
thrum send "<message>" --to @<agent-or-group>
thrum reply <msg-id> "<response>"
thrum wait --timeout 120s
thrum who-has <path>

Tmux vs Listener

Prefer tmux-managed sessions when available. They get daemon nudges directly with no background listener cost.
When tmux is not available, use the background listener pattern and re-arm it after each completion.

Context Management

thrum prime gathers identity, team, inbox, git context, and sync health.
Save durable project state before compaction or handoff.
Restore saved work context after restart with thrum-load-context.

References

resources/TMUX_SESSIONS.md
resources/BOUNDARIES.md
resources/MESSAGING.md
resources/ANTI_PATTERNS.md
resources/LISTENER_PATTERN.md
resources/CLI_REFERENCE.md
resources/IDENTITY.md
resources/WORKTREES.md

More from this repository

same repository

thrum

leonletto/thrum

Multi-agent coordination via messaging, groups, and shared context. Use when agents need to communicate, delegate work, or coordinate across worktrees.

Reply to a message

Send a message to an agent

2026-06-0928

thrum

leonletto/thrum

Multi-agent coordination via messaging, groups, and shared context. Use when agents need to communicate, delegate work, or coordinate across worktrees.

2026-06-0928

thrum

leonletto/thrum

Multi-agent coordination via messaging, groups, and shared context. Use when agents need to communicate, delegate work, or coordinate across worktrees.

2026-06-0928

thrum-restart-extended

leonletto/thrum

Save a comprehensive 16-section restart snapshot and prepare for session restart. Use for designer/architect-grade handoffs needing wire contracts, capability matrix, anticipated Q&A, and design rationale that the standard $thrum-restart compact format cannot carry.

2026-06-0428

Thrum

Use this as the main Thrum skill in Codex. It is the umbrella entry point for multi-agent coordination, command selection, and message-routing decisions.

Use this when

Work must coordinate across agents, worktrees, or sessions.

You need to choose the right Thrum workflow before acting.

The request spans multiple Thrum commands rather than one narrow operation.

Command Skills

Codex registers the Claude plugin command surface as top-level skills:

thrum-prime

thrum-overview

thrum-update-project

thrum-team

thrum-inbox

thrum-send

thrum-reply

thrum-wait

thrum-restart

thrum-load-context

thrum-quickstart

thrum-configure-roles

thrum-project-setup

Use those when the user explicitly asks for one command. Use thrum when you need judgment across commands.

Core workflow

Prime context with thrum prime and capture identity, team, inbox, and sync health.

Decide whether the task is messaging, triage, session lifecycle, role setup, or project decomposition.

Route into the matching thrum-* command skill when the next step is command-specific.

Keep scope explicit: branch, worktree, files, intended audience, and expected output.

Re-arm a listener or tmux session pattern when continuous monitoring matters.

Command baseline

thrum prime thrum overview thrum team thrum inbox --unread thrum send "<message>" --to @<agent-or-group> thrum reply <msg-id> "<response>" thrum wait --timeout 120s thrum who-has <path>

Tmux vs Listener

Prefer tmux-managed sessions when available. They get daemon nudges directly with no background listener cost.

When tmux is not available, use the background listener pattern and re-arm it after each completion.

Context Management

thrum prime gathers identity, team, inbox, git context, and sync health.

Save durable project state before compaction or handoff.

Restore saved work context after restart with thrum-load-context.

References

resources/TMUX_SESSIONS.md

resources/BOUNDARIES.md

resources/MESSAGING.md

resources/ANTI_PATTERNS.md

resources/LISTENER_PATTERN.md

resources/CLI_REFERENCE.md

resources/IDENTITY.md

resources/WORKTREES.md