herdr
Skill0 starsChanged 59 days agoMITView on GitHub
Inspect or control Herdr. In a Herdr-managed pane (HERDR_ENV=1), use the local CLI; from ChatGPT Web, Mobile, or Desktop, use the herdr_control MCP Bridge and never fall back to the CLI.
50 other projects use a version of this, 6 of them edited.
Adopted by
Most recently taken up by
- davidondrej/skillstheir own version, first seen Nov 15, 2026
- compozy/compozytheir own version, first seen Nov 13, 2026
- juraj-blahunka/skillstheir own version, first seen Nov 8, 2026
- bepaldes/heimdall-agenttheir own version, first seen Nov 8, 2026
- cormacc/dotagentstheir own version, first seen Nov 4, 2026
- rhasselle-oddball/claude-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use better-accessibility, show-me and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnasX7Skillbetter-accessibility
Helps your project comply with accessibility standards and best practices.
Also in 3 projects that use this
AnasX7Skillshow-me
Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.
Also in 5 projects that use this
kannaka-labsSkillskill-doctor
Environment diagnostics — check providers, auth, config, hooks, scheduler, and more. Use when: AUTOMATICALLY ACTIVATE when user asks about:. \"doctor\" or \"run doctor\" or \"diagnostics\". \"check my setup\" or \"is everything working\"
Also in 3 projects that use this
GoogleSkillwayfinder
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
Also in 6 projects that use this
AWSSkillwizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
Also in 5 projects that use this
MicrosoftSkillwriting-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
Also in 7 projects that use this
Other versions50 projects use a version of this.
Word for word · 0
None found.
Edited · 6
- ninehills/skills★ 28025% same
- ninehills/public-skills★ 8625% same
- bmaltais/skills★ 283% same
- jbaham2/herdr-plugin★ 190% same
- MoonTory/skills★ 131% same
- tanuuuuuuu/dotfiles★ 090% same
Wrote their own version · 44
- ogulcancelik/herdr★ 47ksame name
- herdrdev/herdr★ 47ksame name
- davidondrej/skills★ 4.3ksame name
- compozy/compozy★ 2.9ksame name
- dmmulroy/skills★ 428same name
- sammcj/agentic-coding★ 169same name
- romiluz13/mifal★ 47same name
- hcchengithub/peforth★ 37same name
- ulises-jeremias/agent-toolkit★ 20same name
- Mineru98/skills-store★ 13same name
34 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- acquisitionSkill
- after-actionSkill
- breachSkill
- cartographic-reconSkill
- chartSkill
- codifySkill
- conopsSkill
- coverSkill
- dossierSkill
- executeSkill
- go-nogoSkill
- netease-mailSkill
- neutralizeSkill
- paperworkSkill
- passdownSkill
- repairSkill
- sanitizeSkill
- taskingSkill
- tracebackSkill
- warroomSkill
- x-likes-digestSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 49 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
if HERDR_ENV=1, this is a Herdr-managed pane.
- Distinctive: line 44
create tabs for separate subcontexts inside one workspace
- Distinctive: line 46
start servers, watch logs, and run tests in sibling panes
- Distinctive: line 47
wait for specific output before continuing
- Distinctive: line 48
wait for another agent to finish
- Very specific: line 325
use pane read for current output that already exists.
- Very specific: line 329
if you are running inside herdr, the HERDR_ENV environment variable is set to 1.
“Common” is measured: kept by at least 6 in 10 of the 49 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
herdr — agent skill
Minimal entry
First choose the runtime path below. For a basic status check, discover the workspace, tab, and pane IDs, then read the target pane. Read only the operation section needed for the user request; recipes and agent coordination are optional.
runtime routing
choose exactly one control path before doing anything:
- if
HERDR_ENV=1, this is a Herdr-managed pane. use theherdrCLI instructions below. - otherwise, if the
mcp__herdr_control__*tools are available, this is an external ChatGPT client. use only the MCP Bridge instructions below. - otherwise, report that the Herdr Bridge is unavailable and stop.
when HERDR_ENV is not 1, never inspect or control Herdr through the local herdr CLI, shell commands, socket files, or an HTTP fallback. ChatGPT Web, Mobile, and Desktop must always use the MCP Bridge.
external ChatGPT clients: MCP Bridge
use only the capabilities actually exposed in the current tool list:
mcp__herdr_control__list_agents— list current agents and status.mcp__herdr_control__list_panes— list current panes and obtain fresh pane ids.mcp__herdr_control__read_pane— read an existing pane.mcp__herdr_control__prompt_agent— prompt an existing agent when the user authorized that write action.mcp__herdr_control__pane_send_text,pane_send_keys,pane_run— type, key, or run a user-authorized command in an existing pane.mcp__herdr_control__pane_wait_output,pane_split,pane_close— wait for output or manage a pane; closing requires explicit authorization for the exact pane.
pane ids are ephemeral. call list_agents or list_panes immediately before every pane operation; never reuse an id from an earlier turn. for writes, verify the selected pane still belongs to the intended target and report the resulting state.
if the requested operation is not exposed by the Bridge, say which capability is missing and stop. do not fall back to herdr CLI. in particular, do not imply that workspace, tab, split, run, close, or wait operations exist unless matching MCP tools are present.
Herdr-managed panes: local CLI
you are running inside herdr, a terminal-native agent multiplexer. herdr gives you workspaces, tabs, and panes — each pane is a real terminal with its own shell, agent, server, or log stream — and you can control all of it from the cli.
this means you can:
- see what other panes and agents are doing
- create tabs for separate subcontexts inside one workspace
- split panes and run commands in them
- start servers, watch logs, and run tests in sibling panes
- wait for specific output before continuing
- wait for another agent to finish
- spawn more agent instances
the herdr binary is available in your PATH. its workspace, tab, pane, and wait commands talk to the running herdr instance over a local unix socket.
if you need the raw protocol or full api reference, read the socket api docs.
concepts
workspaces are project contexts. each workspace has one or more tabs. unless manually renamed, a workspace's label follows the first tab's root pane — usually the repo name, otherwise the root pane's current folder name.
tabs are subcontexts inside a workspace. each tab has one or more panes.
panes are terminal splits inside a tab. each pane runs its own process — a shell, an agent, a server, anything.
agent status is detected automatically by herdr. the api exposes one public field for it:
agent_status—idle,working,blocked,done,unknown
done means the agent finished, but you have not looked at that finished pane yet.
plain shells still exist as panes, but herdr's sidebar agent section intentionally focuses on detected agents rather than listing every shell.
ids — workspace ids look like 1, 2. tab ids look like 1:1, 1:2, 2:1. pane ids look like 1-1, 1-2, 2-1. these are compact public ids for the current live session.
important: ids can compact when tabs, panes, or workspaces are closed. do not treat them as durable ids. re-read ids from workspace list, tab list, pane list, or create/split responses when you need a current id. do not guess that an older 1-3 is still the same pane later.
discover yourself
see what panes exist and which one is focused:
herdr pane listthe focused pane is yours. other panes are your neighbors.
list workspaces:
herdr workspace listtab management
list tabs in the current workspace:
herdr tab list --workspace 1create a new tab:
herdr tab create --workspace 1without --label, the new tab keeps the default numbered tab name.
create and name it in one step:
herdr tab create --workspace 1 --label "logs"rename it:
herdr tab rename 1:2 "logs"focus it:
herdr tab focus 1:2close it:
herdr tab close 1:2read another pane
see what is on another pane's screen:
herdr pane read 1-1 --source recent --lines 50--source visible= current viewport--source recent= recent scrollback as rendered in the pane--source recent-unwrapped= recent terminal text with soft wraps joined back together
split a pane and run a command
split your pane to the right and keep focus on your current pane:
herdr pane split 1-2 --direction right --no-focusthat prints json with the new pane nested at result.pane.pane_id. parse that value, then run a command in that pane:
NEW_PANE=$(herdr pane split 1-2 --direction right --no-focus | python3 -c 'import sys,json; print(json.load(sys.stdin)["result"]["pane"]["pane_id"])')
herdr pane run "$NEW_PANE" "npm run dev"split downward instead:
herdr pane split 1-2 --direction down --no-focuswait for output
block until specific text appears in a pane. useful for waiting on servers, builds, and tests.
for --source recent, matching uses unwrapped recent terminal text, so pane width and soft wrapping do not break matches. pane read --source recent still shows the pane as rendered. if you want to inspect the same transcript that the waiter matches, use pane read --source recent-unwrapped.
herdr pane wait-output 1-3 --match "ready on port 3000" --timeout 30000with regex:
herdr pane wait-output 1-3 --match "server.*ready" --regex --timeout 30000if it times out, exit code is 1.
wait for an agent status
block until another agent reaches a specific status:
herdr agent wait 1-1 --until done --timeout 60000use this when you want the same done / idle distinction the UI shows.
send text or keys to a pane
send text without pressing Enter:
herdr pane send-text 1-1 "hello from claude"press Enter or other keys:
herdr pane send-keys 1-1 Enterpane run sends the text and then a real Enter key in one request:
herdr pane run 1-1 "echo hello"workspace management
create a new workspace:
herdr workspace create --cwd /path/to/projectwithout --label, the new workspace keeps the default cwd-based name.
create and name one in one step:
herdr workspace create --cwd /path/to/project --label "api server"create one without focusing it:
herdr workspace create --no-focusfocus a workspace:
herdr workspace focus 2rename:
herdr workspace rename 1 "api server"close:
herdr workspace close 2close a pane
herdr pane close 1-3recipes
run a server and wait until it is ready
NEW_PANE=$(herdr pane split 1-2 --direction right --no-focus | python3 -c 'import sys,json; print(json.load(sys.stdin)["result"]["pane"]["pane_id"])')
herdr pane run "$NEW_PANE" "npm run dev"
herdr pane wait-output "$NEW_PANE" --match "ready" --timeout 30000
herdr pane read "$NEW_PANE" --source recent --lines 20run tests in a separate pane and inspect the result
herdr pane split 1-2 --direction down --no-focus
herdr pane run 1-3 "cargo test"
herdr pane wait-output 1-3 --match "test result" --timeout 60000
herdr pane read 1-3 --source recent --lines 30check what another agent is working on
herdr pane list
herdr pane read 1-1 --source recent --lines 80watch another pane robustly
use this pattern when you need to coordinate with a sibling pane:
# inspect what is already there
herdr pane read 1-3 --source recent --lines 40
# wait only for the next output you expect
herdr pane wait-output 1-3 --match "ready" --timeout 30000
# if you need to inspect the same transcript the waiter matched,
# read the unwrapped recent text directly
herdr pane read 1-3 --source recent-unwrapped --lines 40spawn a new agent and give it a task
herdr pane split 1-2 --direction right --no-focus
herdr pane run 1-3 "claude"
herdr pane wait-output 1-3 --match ">" --timeout 15000
herdr pane run 1-3 "review the test coverage in src/api/"coordinate with another agent
herdr agent wait 1-1 --until done --timeout 120000
herdr pane read 1-1 --source recent --lines 100notes
workspace list,workspace create,tab list,tab create,tab get,tab focus,tab rename,tab close,pane list,pane get,pane split,pane wait-output, andagent waitprint json on success.pane readprints text, not json.pane read --format ansiorpane read --ansireturns a rendered ANSI snapshot for TUI feedback loops.pane read --source recent-unwrappedis useful when you want to inspect the same unwrapped transcript thatpane wait-output --source recentmatches against.pane send-text,pane send-keys, andpane runprint nothing on success.- parse ids from
workspace create,tab create, andpane splitresponses when you need new ids.workspace createreturnsresult.workspace,result.tab, andresult.root_pane.tab createreturnsresult.tabandresult.root_pane. forpane split, the new pane id is atresult.pane.pane_id. - use
pane readfor current output that already exists. usepane wait-outputfor future output you expect next. --no-focuson split, tab create, and workspace create keeps your current terminal context focused.- without
--label, workspace create keeps cwd-based naming and tab create keeps numbered naming. --labelon tab create and workspace create applies the custom name immediately.- if you are running inside herdr, the
HERDR_ENVenvironment variable is set to1.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

