By jbaham2
Makes Claude an expert at herdr, the agent-aware terminal multiplexer: herding fleets of agents, designing and restoring workspace/tab/pane layouts, monitoring agent state, managing sessions, and authoring configuration. Vendors the official herdr agent skill and complements it with workflow judgment.
Configure or tune herdr — keybindings, theme, agent-detection rules, notifications, or write a herdr plugin.
Save, restore, or design a reusable herdr pane/tab layout.
Reattach to herdr or recover a session after a restart or update — explain what survived.
Triage your herdr agent fleet — find which agents are blocked, done, or need attention.
Set up a herdr workspace and herd a fleet of agents to work a multi-part task in parallel.
Read-only triage of a herdr agent fleet. Use to find which agents are blocked, done-but-unreviewed, or stuck, and to explain why a herdr agent's detected state looks wrong. Inspects and reports only — never sends input, spawns, or restarts agents.
Sets up a herdr workspace and dispatches a fleet of coding agents to work a multi-part task in parallel, then coordinates their handoffs. Use when a task should be split across several agents in herdr. Spawns and assigns agents (without stealing focus) and wires up wait-coordination between them.
Monitors and triages a fleet of agents in herdr, and explains why a herdr agent's detected state looks wrong. Teaches the detection-AUTHORITY model (lifecycle-state hooks vs screen-manifest detection), state roll-up across pane/tab/workspace, a triage workflow for finding who needs attention, and a debugging path with `herdr agent explain`. Defers raw command syntax to the vendored herdr skill and live `herdr --help`. Triggers: 'which herdr agent needs attention', 'why does herdr show my agent as idle/blocked', 'monitor my agents status', 'an agent is stuck/blocked in herdr', 'herdr agent state is wrong / explain detection', 'is my agent done in herdr'.
Control herdr from inside it. Manage workspaces and tabs, split panes, spawn agents, read output, and wait for state changes — all via CLI commands that talk to the running herdr instance over a local unix socket. Use when running inside herdr (HERDR_ENV=1).
Use when configuring or tuning herdr through its config file or detection manifests — editing ~/.config/herdr/config.toml, changing keybindings (prefix mode, direct shortcuts, special keys, custom pane/shell/plugin_action commands), setting a theme or custom colors, tuning agent-detection/labeling rules, configuring notifications and sounds, terminal/shell and sidebar/scrollback/mouse behavior, experimental flags, or authoring herdr's own plugins (herdr-plugin.toml). Triggers: 'configure herdr', 'change herdr keybindings', 'rebind herdr prefix', 'set a herdr theme', 'tune herdr agent detection rules', 'herdr notifications/sounds', 'edit config.toml for herdr', 'write a herdr plugin', 'create herdr-plugin.toml'. Does NOT cover in-pane control CLI, session/workspace lifecycle, or the meaning of agent states.
Use when designing, saving, or reproducing a pane/tab arrangement in herdr — 'save/restore my herdr layout', 'set up a reusable pane layout in herdr', 'recreate this workspace layout', 'export a herdr layout tree', 'declarative workspace setup in herdr', or capturing an editor+server+logs+tests arrangement as a shareable, reproducible artifact. Also covers the judgment around resize/swap/move/zoom for legibility. Use this skill to arrange, save, or reproduce panes *now*; for session lifecycle, recovery, and which-container-to-use judgment use herdr-workspace-management. Defers raw command syntax to the vendored herdr skill and the live socket API; defers keybindings to herdr-configuration.
Use when herding a fleet of coding agents in herdr — deciding whether to run several agents in parallel vs a single agent, setting up an agent council/team, having one agent coordinate or manage others, routing input to a specific agent by name or pane, dividing work so agents don't collide, making agent B wait on agent A, spawning helper agents without stealing focus, or running a fleet on a remote box. Holds the durable judgment of multi-agent assignment; defers all raw command syntax to the vendored herdr skill and the live CLI. Triggers: 'run several agents in parallel in herdr', 'set up an agent council/team', 'have one agent coordinate others', 'herd agents on a remote box', 'split a task across multiple coding agents', 'route this to a specific agent', 'make one agent wait for another'.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Makes Claude a genuine expert at herdr, the agent-aware terminal multiplexer: herding fleets of coding agents, designing and restoring workspace/tab/pane layouts, monitoring agent state, managing sessions, and authoring configuration.
It vendors the official herdr agent skill (the authoritative in-pane control reference) and complements it with durable workflow judgment the official skill doesn't cover.
| Skill | Owns |
|---|---|
herdr (vendored) | Raw in-pane control mechanics + HERDR_ENV=1 guard + id rules + recipes (official, AGPL) |
herdr-workspace-management | Session/server lifecycle, detach/reattach, native resume, workspace-vs-tab-vs-pane organization |
herdr-multi-agent | Fan-out strategy, council/team/manager-worker patterns, routing, dependency coordination, remote fleets |
herdr-agent-monitoring | Detection-authority model (hooks vs screen-manifest), fleet triage, herdr agent explain, gotchas |
herdr-layouts | Designing, exporting, and restoring reusable layout trees; declarative workspace-from-tree |
herdr-configuration | Authoring config.toml + detection manifests: keybindings, themes, notifications, herdr-plugin authoring |
/herd <task> — set up a workspace and herd a fleet of agents on a multi-part task./herd-status — triage the fleet: who is blocked, done, or needs attention (read-only)./herd-layout save|restore|design [name] — manage a reusable layout./herd-config <what> — configure/tune herdr (keybindings, theme, detection rules, notifications)./herd-resume — reattach or recover a session after a restart/update.herdr-fleet-monitor — read-only triage of the agent fleet.herdr-orchestrator — sets up and dispatches a fleet, wiring up handoffs.SessionStart — if Claude is running inside herdr (HERDR_ENV=1), injects a short context note so
the herdr skills engage. Emits nothing and never blocks when run outside herdr.SKILL.md (pinned, see skills/herdr-agent-skill/VENDORED.md)
is the single source of truth for command mechanics. The complement skills hold only durable
judgment and defer stale-prone facts (flags, socket method names, defaults) to the live herdr
CLI and docs.herdr
binary (herdr --help, herdr --default-config) and fall back to WebFetch of herdr.dev/docs
when it isn't on PATH. For live lookups against your running session, herdr must be installed.# from a clone of this repo
/plugin marketplace add /path/to/herdr-plugin
/plugin install herdr@herdr-marketplace
No MCP server and no auth required. The plugin is most useful when run inside a herdr-managed
pane (so the herdr CLI can talk to your running session over its local socket).
This plugin is licensed AGPL-3.0-or-later as a whole (see LICENSE). It vendors the official herdr
agent skill (skills/herdr-agent-skill/SKILL.md + LICENSE), which herdr distributes under
AGPL-3.0-or-later; licensing the whole plugin AGPL avoids any redistribution conflict. Reusers must
keep derivative works open under the same terms. Provenance and the pinned upstream commit are in
skills/herdr-agent-skill/VENDORED.md.
meta/ROADMAP.md — build phases and status.meta/DECISIONS.md — architecture decisions and the ownership map.meta/source-tracker.md — every source, what it taught, and where it landed.npx claudepluginhub jbaham2/herdr-plugin --plugin herdrTurn any service's documentation into a Claude Code expert plugin: map the docs, fill the builder prompt, then build the plugin — as guided slash commands.
Makes Claude an expert at LlamaCloud (Parse, Extract, Classify, Split, Sheets, Cloud Index), LiteParse, and the LlamaIndex framework + agentic Workflows. Skills hold durable judgment; the wired LlamaIndex docs MCP fetches current API facts live.
Expert system for Langfuse setup, observability, prompt management, evaluation, and monitoring. Bundles distilled knowledge, skills, agents, commands, and hooks.
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.