estack-better-title - SKILL.md Agent Skill

name: estack-better-title version: 1.0.3 description: (better-title) Suggest better chat session titles and rename the session disable-model-invocation: true allowed-tools: Bash, AskUserQuestion

Better Title

The current session ID is: ${CLAUDE_SESSION_ID}

Your task

Suggest 3 descriptive titles for this chat session based on the conversation so far. The goal is to make sessions easy to find later.

Before drafting, do this quick mental pass

Ask yourself:

What were the goals going in?
What got built / decided / fixed that the user might reference later?
What was noise — mistakes, abandoned approaches, things they had to redirect you on, dead ends? (These do NOT belong in the title.)
What's temporary vs. lasting? Temporary states should be mentioned briefly, not led with.

Write the title from those answers, NOT from a chronological recap of the chat.

Good titles

Summarize what was accomplished, not what was attempted
Title the outputs, not the journey — exclude mistakes, dead ends, and abandoned approaches. They're not searchable and not useful context for future-you.
Use plain language a future-you would search for. Avoid jargon like "passthrough," "edge cases," "toggle logic," "auto-cd," "refactored," "overhaul." Say what it does in normal words.
Weight by long-term reference value. If something will stop mattering in weeks or months (temporary fixes, current-state notes, "until X is available" workarounds), mention it briefly but don't lead with it.
List key outputs separated by dashes, commas, or similar (e.g. "Reverse-Engineering /rename, PR #33165 Comment, and Building /estack-better-title Skill")
Cover 2-4 main outputs. Resist cramming everything in — first-pass attempts tend to over-include.
Are detailed enough that someone skimming a session list can tell exactly what they'd find inside
Typically 8-20 words — longer is fine if it adds useful detail

Format

Present the 3 options using AskUserQuestion with a single-select question (multiSelect: false):

Each option's label is the full title text
Each option's description is a brief rationale for why it's a good title
The user can also select "Other" (provided automatically) to give feedback

Interaction loop

If the user selects one of the 3 titles, use that title.
If the user selects "Other" and provides feedback (e.g. "shorter", "more specific", "mention X"), generate 3 new suggestions incorporating their feedback and present again via AskUserQuestion.
Keep iterating until the user selects a title or gives you an exact title.

Renaming

Once the user has chosen a title, run the rename script using a quoted heredoc to pass the title safely:

bash "${CLAUDE_SKILL_DIR}/scripts/rename.sh" "${CLAUDE_SESSION_ID}" <<'__CLAUDE_TITLE__'
<chosen title>
__CLAUDE_TITLE__

Replace <chosen title> with the actual chosen title. The quoted heredoc (<<'__CLAUDE_TITLE__') prevents the shell from interpreting any special characters in the title — quotes, apostrophes, dollar signs, backticks, etc. are all passed through literally. After running, confirm the rename succeeded.

Important: The live UI border won't update until the next session resume — the persisted title will show in the session list and on next /resume.

Skill Feedback

If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:

If gh is installed (gh --version succeeds), create the issue directly:

gh issue create \
  --repo ElliotDrel/e-stack \
  --title "estack-better-title: <concise summary>" \
  --body "<description from user feedback — expected vs. actual behavior and context>"

If gh is not installed, build a pre-filled URL:

python3 -c "
import urllib.parse
title = 'estack-better-title: <concise summary>'
body = '<description from user feedback — expected vs. actual behavior and context>'
base = 'https://github.com/ElliotDrel/e-stack/issues/new'
print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
"

Share the printed URL with the user and offer to open it in their browser.

They can also click it directly, review the pre-filled title and body, and click Submit new issue.