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

Tower

by koolamusic in koolamusic/claudefiles

Run the orchestrator's war room on visible Herdr panes so the user can watch every child agent work.

MITAuto-check passed

Install Tower

skills CLI
$ npx skills add koolamusic/claudefiles --skill tower -a claude-code

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

GitHub CLI
$ gh skill install koolamusic/claudefiles tower --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/koolamusic/claudefiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tower .claude/skills/tower && 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
tower
GitHub stars
130
Token cost
~1.2k tokens
SKILL.md length
625 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Run the orchestrator's war room on visible Herdr panes so the user can watch every child agent work.

  • The user says tower on
  • SKILL.md covers Commands, What stays the same, Substrate mapping and Success criteria
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Orchestrate this in herdr

What it does

Tower is an agent skill from koolamusic/claudefiles. Run the orchestrator's war room on visible Herdr panes so the user can watch every child agent work. Use when the user says 'tower on', 'orchestrate this in herdr', wants routed agents they can see, or when the orchestrator is on inside a Herdr-managed pane.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A minimal catalog of my favourite skills for working with claude. The licence is MIT.

When your agent uses it

  • The user says tower on
  • Orchestrate this in herdr
  • Wants routed agents they can see
  • The orchestrator is on inside a Herdr-managed pane

Example prompts

  • “tower on”
  • “orchestrate this in herdr”
  • “/tower”

What it can do on your machine

Read from SKILL.md and the folder at commit 297c432. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and markdown).

    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

Tower loads about 1.2k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 625 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~66
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from koolamusic/claudefiles at commit 297c432, republished under its MIT licence (© koolamusic). 625 words, ~1,164 tokens.

Download SKILL.mdSave it as .claude/skills/tower/SKILL.md (or your agent's skills folder).
name
tower
description
Run the orchestrator's war room on visible Herdr panes so the user can watch every child agent work. Use when the user says 'tower on', 'orchestrate this in herdr', wants routed agents they can see, or when the orchestrator is on inside a Herdr-managed pane.

Tower

The orchestrator skill decides who does what. This skill decides where they run: one Herdr pane per child, visible to the user, instead of invisible background subagents.

Gate first:

bash
test "${HERDR_ENV:-}" = 1

If the check fails, say the session is not inside Herdr and fall back to the orchestrator's own substrate. Do not run any herdr command.

Commands

  • tower on — orchestrator mode with this substrate. Loads orchestrator and herdr if they are not already in context.
  • tower off — same as orchestrator off.
  • tower status — the orchestrator status check, with pane states from Herdr.

What stays the same

Everything the orchestrator skill defines: the three slots, personas, routing rules, the delegation brief, the war room table, the stall cap, and the safety rules. Read them there. This file replaces only the "Child Agent Substrate" section. The herdr skill remains the authority for CLI syntax and safety.

Substrate mapping

Orchestrator stepTower
Spawn a childpane split (or tab create for an executor), then agent start <name> --kind claude --pane <id>
Continue a childagent prompt <name> "<text>" --wait --timeout <ms>
Status checkagent list; per child agent get <name>
Read a closeoutagent read <name> --source recent-unwrapped --lines 200
Worktree isolationworktree create --branch <name> for the executor's workspace
Stallagent_status unchanged across two status checks
Naming

The agent name is the war room key: <branch-or-key>-<slot>, lowercase, hyphens, under 32 chars. auth-exec, auth-audit, search-survey. The name follows the pane occupant, so the same child answers follow-up prompts on that branch, and agent list reads as the roster.

Placement
  • Surveyors and auditors are short-lived: split beside the calling pane with --no-focus, right when wide, down when tall, and close the pane after the closeout is recorded.
  • Executors are long-lived and own a branch: give each its own tab, labelled with the branch, so its transcript is not fighting for space. Use a worktree workspace when two executors are mutating at once.
  • Never create a workspace, tab, or pane the user did not ask for beyond these rules, and never close one this session did not create.
Dispatch
bash
herdr pane split --current --direction right --cwd "$PWD" --no-focus
herdr agent start auth-exec --kind claude --pane <returned-pane-id>
herdr agent prompt auth-exec "<delegation brief>" --wait --timeout 600000

Wait for agent start to return ready before prompting. The delegation brief is the orchestrator's, verbatim, plus one line: "Finish your closeout as a short Markdown block so it can be read from the terminal."

Show full SKILL.md (247 more words)Show less
Waiting

agent prompt --wait blocks this session on one child. With several children active, put each wait in a background Bash call, or prompt without --wait and use agent wait <name> --timeout <ms> at the next status check. A timeout does not prove the prompt was lost; read the pane before re-sending.

Blocked children

A child in blocked has a permission dialog or a question on screen. Do not answer it. Report the row as blocked, name the pane so the user can look, and route the decision to the user. This is the visibility the substrate exists for.

Reading results

Read the closeout with agent read. If the transcript is longer than the read returns, ask the child to write the closeout to a Markdown file in a temporary directory and reply with the path, then read that file. Findings from surveyors and auditors still come back to this session, and this session routes any fix to the owning executor.

War room table

Same four columns. Put the agent name in the Next cell on the first row for a branch so it survives summarization:

md
| auth | executor (backend) | working | pane auth-exec: migration in progress |

Success criteria

  • tower on inside Herdr yields a war room where every child is a visible pane.
  • Outside Herdr it degrades to the orchestrator's own substrate with one line of notice.
  • Same-branch follow-ups go to the same named agent.
  • A blocked child reaches the user, not an automatic answer.
  • Nothing in orchestrator or herdr is duplicated here beyond the table above.

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

Files

Just SKILL.md in skills/tower of koolamusic/claudefiles.

Open the folder on GitHubat commit 297c432

Compare with similar skills

Tower 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.

Tower compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tower this skillkoolamusic/claudefiles130—~1.2kAutomated safety check: PassMIT
Team Agent Orchestrationaffaan-m/ECC275k1 repos~1.2kAutomated safety check: PassMIT
Scenario War Roomalirezarezvani/claude-skills28k1 repos~2kAutomated safety check: PassMIT
Herdr Orchestrationpedronauck/skills6341 repos~3.3kAutomated safety check: PassNone
Orca Orchestrationstablyai/orca87k—~916Automated safety check: PassMIT
Agent Orchestrator Taskruvnet/ruflo74k3 repos~1kAutomated safety check: PassMIT

Similar skills

  • Team Agent Orchestration

    affaan-m/ECC

    Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates.

    275k GitHub starsUsed in 1 repo~1.2k tokens
    Agent WorkflowsAuto-check passed

  • Scenario War Room

    alirezarezvani/claude-skills

    Cross-functional what-if modeling for cascading multi-variable scenarios.

    28k GitHub starsUsed in 1 repo~2k tokens
    Testing & QAAuto-check passed

  • Herdr Orchestration

    pedronauck/skills

    Orchestrate Claude and Codex worker TUIs from a controller agent — one worker per named herdr tab, driven over the herdr socket CLI.

    634 GitHub starsUsed in 1 repo~3.3k tokens
    Auto-check passed

  • Orca Orchestration

    stablyai/orca

    Coordinate supervised Orca workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator…

    87k GitHub stars~916 tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Agent Orchestrator Task

    ruvnet/ruflo

    Agent skill for orchestrator-task - invoke with $agent-orchestrator-task

    74k GitHub starsUsed in 3 repos~1k tokens
    Agent WorkflowsAuto-check passed

  • Plan Orchestrate

    affaan-m/ECC

    Read a plan document, decompose it into steps, design a per-step agent chain from the ECC catalogue, and emit ready-to-paste /orchestrate custom prompts.

    275k GitHub starsUsed in 1 repo~4.5k tokens
    Agent WorkflowsAuto-check passed

More from koolamusic/claudefiles

All 13 skills in this repo

  • Explainer Formats

    koolamusic/claudefiles

    A skill your agent uses when asked to explain a topic, codebase, process, or document in a specific output format — plain language or Simplified Technical English (STE, in the style of ASD-STE100…

    130 GitHub stars~1.7k tokensUpdated 2 days ago
    Auto-check passed

  • Breadboarding

    koolamusic/claudefiles

    Transform a workflow description into affordance tables showing UI and Code affordances with their wiring.

    130 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed

  • Orchestrator

    koolamusic/claudefiles

    Turn the current session into a chief-of-staff thread that runs a war room of three role slots — surveyor, executor, auditor — and routes per-branch work to durable, reusable child agents.

    130 GitHub stars~1.7k tokensUpdated 2 days ago
    Auto-check passed

  • Retro

    koolamusic/claudefiles

    A skill your agent uses when a user completes a phase, sprint, milestone, or meaningful unit of work and needs a retrospective.

    130 GitHub stars~2.8k tokensUpdated 2 days ago
    Auto-check passed

  • Skill Creator

    koolamusic/claudefiles

    Guide for creating effective skills. An agent skill from koolamusic/claudefiles.

    130 GitHub stars~1.7k tokensUpdated 2 days ago
    Auto-check passed

  • Debug

    koolamusic/claudefiles

    A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework with built-in backward tracing for deep-stack failures…

    130 GitHub stars~3.1k tokensUpdated 2 days ago
    Auto-check passed

Questions about Tower

What does Tower do?

Run the orchestrator's war room on visible Herdr panes so the user can watch every child agent work. Tower is an agent skill from koolamusic/claudefiles. Run the orchestrator's war room on visible Herdr panes so the user can watch every child agent work.

When should I use Tower?

Tower fits situations like: the user says tower on; orchestrate this in herdr; wants routed agents they can see; the orchestrator is on inside a Herdr-managed pane.

How do I install Tower in Claude Code?

Run `npx skills add koolamusic/claudefiles --skill tower -a claude-code`. Or copy the skill folder (skills/tower in koolamusic/claudefiles) into .claude/skills/tower in your project. Claude Code loads it when a task matches its description.

How do I install Tower in Codex?

Run `npx skills add koolamusic/claudefiles --skill tower -a codex`. Or copy the skill folder (skills/tower in koolamusic/claudefiles) into .agents/skills/tower in your project. Codex loads it when a task matches its description.

Can I use Tower 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 koolamusic/claudefiles --skill tower -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tower, .gemini/skills/tower, .github/skills/tower and .opencode/skills/tower in your project.

What does Tower need to run?

SKILL.md names no scripts, command-line tools or credentials: Tower is instructions for the agent only.

Does Tower 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 Tower 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. Review the folder before installing.

What licence does Tower use?

Tower is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tower use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Tower?

Skills that share tags, products or a category with Tower: Team Agent Orchestration (affaan-m/ECC, 275k stars), Scenario War Room (alirezarezvani/claude-skills, 28k stars), Herdr Orchestration (pedronauck/skills, 634 stars) and Orca Orchestration (stablyai/orca, 87k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tower?

koolamusic (a GitHub user) maintains it in koolamusic/claudefiles, which has 130 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 5, 2026.

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