agentleFS
nesnilnehcnesnilnehc/ai-cortex/skills/rename-session/SKILL.md

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

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
  1. Distinctive:

    Use the current conversation to suggest or set a concise, recognizable title.

    line 10
  2. Distinctive:

    Follow the user's requested title or naming preferences.

    line 14
  3. Distinctive:

    Never place credentials or other sensitive information in the title or output.

    line 21
  4. Distinctive:

    If the subject is unclear, say so and offer a safe, general suggestion.

    line 22
  5. Distinctive:

    If the user requests suggestions only, return the suggestion without changing the session.

    line 23
  6. Distinctive:

    If the host cannot identify or rename the current session, provide the proposed title and explain the limitation.

    line 31
  7. Distinctive:

    Do not install tools, persist preferences or create schedules as part of naming.

    line 37

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.