Herdr Names
Rename Herdr tabs, panes, and agents so each sidebar entry says in a few words what that session is doing. Use whenever the user mentions Herdr and wants tab, pane, or agent names renamed, relabeled, cleaned up, tidied, or made clearer; says a tab or agent name is confusing, meaningless, stale, or just a number; asks what a tab is; or wants the sidebar readable at a glance, even if they only say 'fix the names' or 'label these'. Reads each pane's recent output and names the task, not the project and never the auto-generated terminal title. Needs to run inside Herdr (HERDR_ENV=1). Not for namin
Install
npx skills add petekp/claude-code-setup --skill herdr-namesgit clone --depth 1 https://github.com/petekp/claude-code-setup.git /tmp/claude-code-setup
mkdir -p ~/.claude/skills
cp -r /tmp/claude-code-setup/skills/herdr-names ~/.claude/skills/herdr-namesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Herdr names
## Why names go stale
Herdr's sidebar is only useful when each entry says what that session is for. Three things break that:
- A new tab is labeled with a number ("1") unless someone names it.
- Claude Code rewrites the terminal title on every prompt from the latest user message. A real session showed "Address findings" after the user typed "address the findings". Out of context it says nothing.
- Workspace names already carry the project, so a tab that repeats it ("zui" under zui) adds nothing.
This skill reads what each agent is actually doing and gives the tab, its pane, and the agent one short task name each. Run it end to end without asking for confirmation. Every rename is reversible, and the user invoked it to avoid doing this by hand.
## Steps
`SKILL_DIR` below is the base directory printed when this skill loaded.
1. Confirm you are inside Herdr with `test "${HERDR_ENV:-}" = 1`. If that fails, say you are not running inside Herdr and stop. The CLI can only see the session it runs in.
2. Take the snapshot:
```bash
python3 "$SKILL_DIR/scripts/herdr_names.py" snapshot
```Details
- Skill name
herdr-names- Repository
- petekp/claude-code-setup
- Path
skills/herdr-names/SKILL.md- License
- MIT
- Repo updated
- 26 October 2026
FAQ
What does the Herdr Names skill do?
Rename Herdr tabs, panes, and agents so each sidebar entry says in a few words what that session is doing. Use whenever the user mentions Herdr and wants tab, pane, or agent names renamed, relabeled, cleaned up, tidied, or made clearer; says a tab or agent name is confusing, meaningless, stale, or just a number; asks what a tab is; or wants the sidebar readable at a glance, even if they only say 'fix the names' or 'label these'. Reads each pane's recent output and names the task, not the project and never the auto-generated terminal title. Needs to run inside Herdr (HERDR_ENV=1). Not for namin
How do I install the Herdr Names skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add petekp/claude-code-setup --skill herdr-names. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Herdr Names popular?
It lives in petekp/claude-code-setup, which has 49 GitHub stars and 10 forks.
Related skills
Catch Up
49petekp/claude-code-setup
Give the human a fast, plain-English catch-up on what changed in the project: what the agents did, why, and what decisions need their input. Use when the user asks to "catch me up", "what changed", "where are we", "recap", "brief me", "give me the rundown", "what did you do", "summarize the session", or "fill me in", or otherwise wants to get back up to speed after being away.
Clean Copy
49petekp/claude-code-setup
Cut interface copy that should not exist. Captions that restate a label, hints that pre-empt a worry the user never had, warnings that are scar tissue from a fixed bug. Use when writing or reviewing any user-facing string (labels, hints, empty states, toasts, confirmations, button text), or when asked to clean up or tighten copy.
Code Comments
49petekp/claude-code-setup
Write, review, or remove code comments. Use when adding comments or doc comments, reviewing the comments in a diff, or cleaning up or removing comments.
Prompt
43analystacademy/claude-skills
Build a great prompt through a conversational interview. Use this skill whenever the user wants help writing, improving, or crafting a prompt — including phrases like "help me write a prompt", "I need a prompt for", "how do I prompt Claude to", "make me a prompt that", "I want to prompt an AI to", "create a prompt for", or any time the user describes a task they want an AI to do and seems to want help framing it. Even if they just describe a task vaguely and seem unsure how to ask for it — this skill applies. Trigger it early and often.
Clawhub
44iamclancyliang/nanobot-eino
Search and install agent skills from ClawHub, the public skill registry.
Executing Plans
49sodiumjoe/dotfiles
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.