prename
Generate a meaningful session name based on the overall session theme, not just the last action. Use when asked to "name this session", "rename session", "prename", "give this session a name", "what should I call this session", or when the user invokes /prename. Outputs a concise session title, with a platform-specific rename command only when the current agent supports one. Boundary: not for renaming files, variables, or git branches.
What this skill does
# Prename Generate a session name that captures the **overall theme and purpose**, not just the last action. ## Process 1. Review the conversation's key themes 2. Generate a name following the naming style below 3. Output the title in the platform's supported form ## Naming Style `<emoji> <topic>` - **Emoji** — reflects session nature, freely chosen - **Topic** — the essence of the session; can be a noun, a phrase, or include a verb when it clarifies (e.g., `fix CI: node version mismatch`) - **Reference-driven sessions** — when the session revolves around a specific reference (PR, issue, ticket), use its title: `#42 Fix auth timeout`, `PROJ-123 User onboarding flow` - **Language** — match the user's language or the natural fit for the context; mixing is fine - **Keep it scannable** — aim for 1-5 words after the emoji ## Examples ``` 🔌 vp-prename 🐛 fix CI: node version mismatch ⬆️ React 19 upgrade ⏪ revert abc123 auth regression 📚 MCP server: stdio vs SSE 🔧 #42 Fix auth timeout 🔀 auth middleware refactor 🎫 PROJ-123 User onboarding flow 🧪 session naming 🔌 vp-deps-shift improvements 💬 architecture decisions ``` ## Anti-patterns - Last action only: `fix README typo` when the session built an entire plugin - Too generic: `coding session`, `work` - Too specific: `add handleTimeout to auth/middleware.ts line 42` ## Output If the current agent supports a session rename command, output only that command: ``` /rename <emoji> <topic> ``` Otherwise output only the title: ``` <emoji> <topic> ```
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.