New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Tmux Agent Lane Orchestrator

by vincentkoc in vincentkoc/dotskills

Monitor and coordinate one tmux agent lane, reconstruct worker state from panes and recent Codex logs, classify progress and blockers, and produce concise manager summaries.

MITAuto-check passed

Install Tmux Agent Lane Orchestrator

skills CLI
$ npx skills add vincentkoc/dotskills --skill tmux-agent-lane-orchestrator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vincentkoc/dotskills tmux-agent-lane-orchestrator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vincentkoc/dotskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tmux-agent-lane-orchestrator .claude/skills/tmux-agent-lane-orchestrator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tmux-agent-lane-orchestrator
GitHub stars
108
Token cost
~967 tokens
SKILL.md length
391 words
Files
6 (incl. scripts, references, assets)
Skills in repo
19
Repo updated
First seen
Licence
MIT

At a glance

Monitor and coordinate one tmux agent lane, reconstruct worker state from panes and recent Codex logs, classify progress and blockers, and produce concise manager summaries.

  • Works in 6 steps: Establish lane scope. → Capture lane state. → Cross-check panes and logs. → …
  • Multiple coding-agent workers run in tmux windows named L1
  • SKILL.md covers Purpose, When to use, Workflow and Inputs, plus 2 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Tmux Agent Lane Orchestrator is an agent skill from vincentkoc/dotskills. Monitor and coordinate one tmux agent lane, reconstruct worker state from panes and recent Codex logs, classify progress and blockers, and produce concise manager summaries. Use when multiple coding-agent workers run in tmux windows named L1, L2, and similar lane identifiers.

Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts, reference files and assets (for example `agents/openai.yaml`, `references/factory-model.md` and `scripts/lane_snapshot.py`).

It works with tmux. The repository describes itself as: 🐙 A curated set of Codex and OpenClaw skills for workflow automation, technical debugging, and agent-assisted development patterns. The licence is MIT.

When your agent uses it

  • Multiple coding-agent workers run in tmux windows named L1
  • Similar lane identifiers

Example prompts

  • “/tmux-agent-lane-orchestrator”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Establish lane scope.
  2. Capture lane state.
  3. Cross-check panes and logs.
  4. Classify each pane.
  5. Intervene conservatively.
  6. Summarize in manager style.

What it can do on your machine

Read from SKILL.md and the folder at commit 8f972aa. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tmux Agent Lane Orchestrator loads about 967 tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 391 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~967
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from vincentkoc/dotskills at commit 8f972aa, republished under its MIT licence (© vincentkoc). 391 words, ~967 tokens.

Download SKILL.mdSave it as .claude/skills/tmux-agent-lane-orchestrator/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
tmux-agent-lane-orchestrator
description
Monitor and coordinate one tmux agent lane, reconstruct worker state from panes and recent Codex logs, classify progress and blockers, and produce concise manager summaries. Use when multiple coding-agent workers run in tmux windows named L1, L2, and similar lane identifiers.
license
MIT
metadata.source
https://github.com/vincentkoc/dotskills

tmux Agent Lane Orchestrator

Purpose

Turn a tmux window of coding-agent workers into a visible, auditable lane with clear state and next actions.

When to use

  • Monitor or summarize a tmux worker lane.
  • Reconstruct worker state after a manager cold start.
  • Detect duplicated, idle, waiting, blocked, or risky work.
  • Coordinate several coding-agent panes without mutating them blindly.

Workflow

  1. Establish lane scope.
    • Prefer an explicit lane number.
    • Otherwise infer it from a current tmux window named L<number>.
    • Do not inspect other lanes unless the operator expands scope.
  2. Capture lane state.
    • python3 scripts/lane_snapshot.py --lane <number>
    • Add --session <name> outside the active tmux session.
    • If a descendant command does not contain its resumed thread ID, repeat --thread L<number>.<pane>=<thread-id> from separately verified evidence.
    • Add --json for machine-readable output.
    • Add --cursor-file <path> only when bounded incremental state is wanted; the helper writes no persistent state by default.
    • Records larger than the smaller of --log-bytes and --total-log-bytes are skipped through their next newline. The cursor reports discarding_record while skipping; later events resume.
  3. Cross-check panes and logs.
    • Pane titles alone are weak evidence.
    • Resolve pane ID to shell PID, descendant Codex PID, exact thread ID, the state-database rollout path, and the newest turn.
    • Shared cwd and generic terms such as CI, failed, or running never establish ownership.
    • Missing or conflicting identity is unknown, never a restore target.
  4. Classify each pane.
    • Use the newest exact turn and changing event/tool/token counters.
    • A completed turn after an earlier error is completed, not blocked.
    • Report bounded bytes read and truncation with the state.
    • Include the evidence and next action, not only the label.
  5. Intervene conservatively.
    • Inspect before steering.
    • Avoid duplicate heavy checks.
    • Do not kill or mutate another pane without explicit scope.
    • Prefer reversible actions and targeted commands.
  6. Summarize in manager style.
    • One line per pane: mission, state, evidence, blocker, next action.
    • Add one short manager judgment about where attention belongs.
Show full SKILL.md (75 more words)Show less

Read references/factory-model.md when designing lane responsibilities or escalation policy.

Inputs

  • tmux session name.
  • Lane number or L<number> window.
  • Optional log keywords and capture depth.
  • Optional exact pane/thread declarations and bounded cursor path.
  • Optional operator-provided worker mission map.

Outputs

  • Current pane ID, shell PID, descendant agent PID, exact thread, and rollout snapshot.
  • Per-pane state classification with evidence.
  • Per-file and total log bytes read, cursor mode, and truncation status.
  • Concise manager summary and safe next actions.

Flow

mermaid
stateDiagram-v2
    [*] --> ResolveOneLane
    ResolveOneLane --> CaptureAndMatchIdentity
    CaptureAndMatchIdentity --> ReportUnknown: missing or conflicting identity
    CaptureAndMatchIdentity --> ClassifyNewestTurn: identity matched
    ClassifyNewestTurn --> ReportLane: observation only
    ClassifyNewestTurn --> TargetedIntervention: exact scope authorized
    TargetedIntervention --> VerifyAndReport
    ReportUnknown --> [*]
    ReportLane --> [*]
    VerifyAndReport --> [*]

© vincentkoc, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references, assets) in skills/tmux-agent-lane-orchestrator of vincentkoc/dotskills.

  • SKILL.md
  • agents/openai.yaml
  • assets/icon.jpg
  • references/factory-model.md
  • scripts/lane_snapshot.py
  • scripts/lane_snapshot_test.py

Open the folder on GitHubat commit 8f972aa

Compare with similar skills

Tmux Agent Lane Orchestrator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tmux Agent Lane Orchestrator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tmux Agent Lane Orchestrator this skillvincentkoc/dotskills108—~967Automated safety check: PassMIT
1passwordtrpc-group/trpc-agent-go1.9k14 repos~656Automated safety check: PassApache-2.0
CodeGraph Agent Evalcolbymchenry/codegraph74k—~950Automated safety check: PassMIT
Tmuxtrpc-group/trpc-agent-go1.9k23 repos~868Automated safety check: PassApache-2.0
CodexBar Live QAsteipete/CodexBar22k—~1.2kAutomated safety check: PassMIT
Tmuxopenclaw/openclaw392k1 repos~640Automated safety check: PassMIT

Similar skills

  • 1password

    trpc-group/trpc-agent-go

    Set up and use 1Password CLI (op). An agent skill from trpc-group/trpc-agent-go.

    1.9k GitHub starsUsed in 14 repos~656 tokens
    AI & LLM EngineeringAuto-check passed

  • CodeGraph Agent Eval

    colbymchenry/codegraph

    Benchmarks how much CodeGraph helps a coding agent on a real repository, comparing runs with and without it for a chosen local or published version.

    74k GitHub stars~950 tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Tmux

    trpc-group/trpc-agent-go

    Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.

    1.9k GitHub starsUsed in 23 repos~868 tokens
    Data & AnalyticsAuto-check passed

  • CodexBar Live QA

    steipete/CodexBar

    Runs live QA for the CodexBar app: provider usage matrix checks through its packaged CLI, config validation and menu checks, with 1Password-backed credentials handled safely.

    22k GitHub stars~1.2k tokensUpdated today
    Testing & QAAuto-check passed

  • Tmux

    openclaw/openclaw

    Control tmux sessions/panes for interactive CLIs: list, capture output, send keys, paste text, monitor prompts.

    392k GitHub starsUsed in 1 repo~640 tokens
    Auto-check passed

  • Agent Feature Reproduction

    QwenLM/qwen-code

    Reproduces a feature from Codex or Claude Code in Qwen Code by running the reference agent under capture, reading the traces, then implementing matching behavior.

    28k GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

More from vincentkoc/dotskills

All 19 skills in this repo

  • Openclaw PR Batch Sweep

    vincentkoc/dotskills

    Select, review, repair, validate, and land batches of up to 20 low-risk OpenClaw contributor pull requests using Vincent's maintainer preferences and bounded sub-agent lanes.

    108 GitHub stars~4.1k tokensUpdated 3 days ago
    Auto-check passed

  • Codebase Memory MCP

    vincentkoc/dotskills

    Resolve canonical Git checkouts, index and verify codebase-memory-mcp graphs through the guarded CLI, open its browser viewer on request, and safely audit duplicate worktree caches.

    108 GitHub stars~3.3k tokensUpdated 3 days ago
    Auto-check passed

  • Org Branch Cleanup

    vincentkoc/dotskills

    Audit and safely prune stale branches across a GitHub organization with immutable snapshots, conservative merged-PR classification, live SHA/protection/open-PR revalidation, resumable deletion…

    108 GitHub stars~1.5k tokensUpdated 3 days ago
    Auto-check passed

  • Session Done

    vincentkoc/dotskills

    Prepare a concise session handoff when the user asks to wrap up, capture continuation context, or use /done.

    108 GitHub stars~833 tokensUpdated 3 days ago
    Auto-check passed

  • Codex Goal Mining

    vincentkoc/dotskills

    Mine structured Codex /goal history locally or across a configured machine fleet, measure active goal time and resumed thread spans, identify unfinished and recurring semantic runs, and turn them…

    108 GitHub stars~1.2k tokensUpdated 3 days ago
    Auto-check passed

  • Semantic Slicing

    vincentkoc/dotskills

    Build local semantic review slices by combining clawpatch feature maps, deepsec threat candidates, visual review maps, and optional gitcrawl/discrawl evidence for repos such as openclaw/openclaw.

    108 GitHub stars~2k tokensUpdated 3 days ago
    Auto-check passed

Works with

Questions about Tmux Agent Lane Orchestrator

What does Tmux Agent Lane Orchestrator do?

Monitor and coordinate one tmux agent lane, reconstruct worker state from panes and recent Codex logs, classify progress and blockers, and produce concise manager summaries. Tmux Agent Lane Orchestrator is an agent skill from vincentkoc/dotskills. Monitor and coordinate one tmux agent lane, reconstruct worker state from panes and recent Codex logs, classify progress and blockers, and produce concise manager summaries.

When should I use Tmux Agent Lane Orchestrator?

Tmux Agent Lane Orchestrator fits situations like: multiple coding-agent workers run in tmux windows named L1; similar lane identifiers.

How do I install Tmux Agent Lane Orchestrator in Claude Code?

Run `npx skills add vincentkoc/dotskills --skill tmux-agent-lane-orchestrator -a claude-code`. Or copy the skill folder (skills/tmux-agent-lane-orchestrator in vincentkoc/dotskills) into .claude/skills/tmux-agent-lane-orchestrator in your project. Claude Code loads it when a task matches its description.

How do I install Tmux Agent Lane Orchestrator in Codex?

Run `npx skills add vincentkoc/dotskills --skill tmux-agent-lane-orchestrator -a codex`. Or copy the skill folder (skills/tmux-agent-lane-orchestrator in vincentkoc/dotskills) into .agents/skills/tmux-agent-lane-orchestrator in your project. Codex loads it when a task matches its description.

Can I use Tmux Agent Lane Orchestrator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vincentkoc/dotskills --skill tmux-agent-lane-orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tmux-agent-lane-orchestrator, .gemini/skills/tmux-agent-lane-orchestrator, .github/skills/tmux-agent-lane-orchestrator and .opencode/skills/tmux-agent-lane-orchestrator in your project.

What does Tmux Agent Lane Orchestrator need to run?

Going by SKILL.md and its folder, Tmux Agent Lane Orchestrator needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Tmux Agent Lane Orchestrator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Tmux Agent Lane Orchestrator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Tmux Agent Lane Orchestrator use?

Tmux Agent Lane Orchestrator is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tmux Agent Lane Orchestrator use?

About 967 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 842 tokens, read only when the agent opens those files.

What are the alternatives to Tmux Agent Lane Orchestrator?

Skills that share tags, products or a category with Tmux Agent Lane Orchestrator: 1password (trpc-group/trpc-agent-go, 1.9k stars), CodeGraph Agent Eval (colbymchenry/codegraph, 74k stars), Tmux (trpc-group/trpc-agent-go, 1.9k stars) and CodexBar Live QA (steipete/CodexBar, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tmux Agent Lane Orchestrator?

vincentkoc (a GitHub user) maintains it in vincentkoc/dotskills, which has 108 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 8, 2026.

Source: vincentkoc/dotskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.