sp-daily-brief-rename

Rename Claude Code sessions for scheduled tasks with formatted date strings.

1|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/mwolff328-stack/WolffClaude --skill sp-daily-brief-rename
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sp-daily-brief-rename
Source: https://github.com/mwolff328-stack/WolffClaude/tree/main/scheduled-tasks/sp-daily-brief-rename
Command: npx skills add https://github.com/mwolff328-stack/WolffClaude --skill sp-daily-brief-rename

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the limitation where Claude Code sessions cannot rename themselves while running, ensuring that automated daily tasks are organized with clear, date-stamped titles instead of generic default names.

Core Features & Use Cases

  • Automated Session Management: Identifies and renames specific scheduled task sessions based on their creation date.
  • Safety Guardrails: Includes logic to distinguish between the target session and the renaming task itself to prevent accidental modification of the runner.
  • Use Case: Use this to maintain a clean, searchable history of your daily SurvivorPulse briefs by automatically applying the format SurvivorPulse Daily Brief - YYYY-MM-DD to completed sessions.

Quick Start

Ask the assistant to run the sp-daily-brief-rename skill to update the titles of any recent daily brief sessions that are still using their default names.

Frequently Asked Questions about sp-daily-brief-rename

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically rename scheduled Claude Code sessions with a date stamp?

To automatically rename Claude Code sessions, this skill lists recent sessions, verifies the scheduled task ID, and applies a new title with a formatted date string via session management tools. It targets specific scheduled tasks to ensure organized, date-stamped session names.

Why can't a running Claude Code session rename itself during a scheduled task?

A running Claude Code session cannot rename itself due to a platform limitation that prevents active sessions from modifying their own metadata. This skill solves that problem by using a separate renaming task to update titles of completed daily brief sessions.

How do I prevent accidental renaming of the runner session instead of the target task?

To prevent accidental renaming of the runner session, this skill includes safety guardrails that distinguish between the target scheduled task session and the renaming task itself. It verifies the scheduled task ID before applying any new session title.

How do I keep a searchable history of automated daily tasks in Claude Code?

To keep a searchable history of automated daily tasks, this skill applies a standardized naming format like SurvivorPulse Daily Brief - YYYY-MM-DD to sessions. This replaces generic default names with clear, date-stamped titles for easy retrieval.

Does session renaming work with any scheduled task or only specific daily briefs?

Session renaming works specifically with scheduled tasks associated with daily briefs, such as SurvivorPulse. It identifies target sessions by verifying their scheduled task ID and creation date, ensuring only the intended daily brief sessions are renamed.

What are the limitations of automating session management for scheduled Claude Code tasks?

A key limitation of automating session management is that sessions cannot rename themselves while running, requiring a separate process. Additionally, the renaming skill requires access to session metadata and the ability to execute session renaming commands to function properly.