rename-session
Skill8 starsChanged 2 months agoMITView on GitHub
Suggest or change the current AI agent session title using its actual topic and the user's preferences. Use when asked to name or rename the current conversation; do not organize other sessions.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- FooJiaYin/dev-skillstheir own version, first seen Sep 24, 2026
- Songhonglei/better-agent-skillstheir own version, first seen Jun 20, 2026
- Castrozan/claude-code-flaketheir own version, first seen Jan 22, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- Songhonglei/better-agent-skills★ 4same name
- FooJiaYin/dev-skills★ 2same name
- Castrozan/claude-code-flake★ 1same name
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 repository80 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- archive-milestoneSkill
- assess-product-opportunitySkill
- automate-testsSkill
- bump-versionSkill
- capture-work-itemsSkill
- clarify-product-requirementSkill
- commit-workSkill
- competitive-researchSkill
- consume-nats-messageSkill
- decontextualize-textSkill
- deep-researchSkill
- define-docs-normsSkill
- define-missionSkill
- define-north-starSkill
- define-roadmapSkill
- define-strategic-pillarsSkill
- define-visionSkill
- deliver-featureSkill
- design-strategic-goalsSkill
- eli5Skill
- establish-delivery-workflowSkill
- execute-delivery-workflowSkill
- generate-agent-entrySkill
- generate-github-workflowSkill
- generate-standard-readmeSkill
- inspect-artifact-stateSkill
- integrate-branchesSkill
- manage-secretSkill
- map-item-dependenciesSkill
- market-researchSkill
- orchestrate-code-reviewSkill
- orchestrate-governance-stepSkill
- orchestrate-repair-loopSkill
- orchestrate-repair-requirements-loopSkill
- orchestrate-roadmap-planningSkill
- plan-milestonesSkill
- plan-nextSkill
- policy-researchSkill
- ponytailSkill
- prepare-presales-responseSkill
- prepare-version-notesSkill
- prioritize-backlogSkill
- product-opportunity-analysisSkill
- promote-roadmap-itemsSkill
- publish-nats-messageSkill
- record-milestone-achievementSkill
- redeploy-localSkill
- refine-skill-designSkill
- review-architectureSkill
- review-codebaseSkill
- review-diffSkill
- review-dotnetSkill
- review-error-surfacingSkill
- review-functional-designSkill
- review-goSkill
- review-implementation-alignmentSkill
- review-javaSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use the current conversation to suggest or set a concise, recognizable title.
- Distinctive: line 14
Follow the user's requested title or naming preferences.
- Distinctive: line 21
Never place credentials or other sensitive information in the title or output.
- Distinctive: line 22
If the subject is unclear, say so and offer a safe, general suggestion.
- Distinctive: line 23
If the user requests suggestions only, return the suggestion without changing the session.
- Distinctive: line 31
If the host cannot identify or rename the current session, provide the proposed title and explain the limitation.
- Distinctive: line 37
Do not install tools, persist preferences or create schedules as part of naming.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Name the current session
Use the current conversation to suggest or set a concise, recognizable title. This skill covers the current session only; it does not scan, rename or organize other sessions.
- Follow the user's requested title or naming preferences. Otherwise, summarize
the main subject and concrete goal in the conversation's language. Consider
the conversation's sustained goal and a substantive change of direction;
a minor late follow-up need not replace the main topic. A useful
default is
project or domain: subject and goal, but omit any part that is uncertain or unwanted. A working directory alone does not establish the topic. For recurring work, include a period only when known and useful. - Never place credentials or other sensitive information in the title or output. If the subject is unclear, say so and offer a safe, general suggestion.
- If the user requests suggestions only, return the suggestion without changing the session. If the user asks to rename it, use an available supported host tool for the current session, subject to the host's authorization rules. Find a current-session rename capability among the host's available tools; do not assume a particular interface exists. If the current title is known and already matches, report it without writing. An explicit request to rename authorizes that action; do not add another approval step unless the host requires one.
- If the host cannot identify or rename the current session, provide the proposed title and explain the limitation. When the host supplies a documented manual rename method, include it. Do not modify internal databases or session files as a fallback. Report a rename as successful only when the host confirms it; if supported, verify the resulting title. Report failures and unverified outcomes.
Do not install tools, persist preferences or create schedules as part of naming.
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.

