peon-ping Rename Session
Give the current Claude session a custom name shown in notification titles and the terminal tab.
The skill (peon-ping-rename) writes to a local state file (.state.json) and modifies terminal tab title, no sensitive data or external side effects. However, the documentation does not explicitly state what data is written (only session ID and name mentioned) and lacks a delete or rollback mechanism (only manual removal). No malicious behavior detected, but permission and confirmation mechanisms are incomplete, with unexplained write operations.
The skill's description is clear, provides steps and manual fallback, but lacks automated tests or verification of key paths. The execution environment (Claude Code hook) may vary with version, affecting reliability. Documentation mentions hooks can fail but does not provide sufficient error feedback or debugging details. Static review cannot execute, so reliability scoring is limited.
The skill has clear use cases and trigger conditions (when user requests rename), and provides reset functionality. But it does not declare non-fit scenarios (e.g., non-Claude Code environments or custom config) nor mention China reachability. Since it is local operation, not dependent on overseas networks, deduction is minimal.
The skill includes name, description, version, license metadata, and well-structured documentation. However, it lacks changelog, known limitations, or maintenance responsibility. The manual fallback hardcodes path to ~/.claude, possibly conflicting with other install methods. Overall readable, but versioning and maintenance info incomplete.
The core functionality (rename session) is clearly described and easy to implement manually, but no automated verification evidence provided. The output is command-line modification, may be limited by terminal environment. Marginal value is limited as users can edit state file directly, but the skill provides convenient slash command interface. Static review cannot execute, relying solely on documentation.
Static review cannot verify the skill's actual execution. Documentation describes workflow but no test code or CI coverage for this skill. Related CI workflow (release.yml) only generates checksums, no tests. Thus, key claims lack verifiable evidence.
- Skill relies only on documentation; static review cannot execute verification, actual effect needs testing in Claude Code.
- No rollback or deletion mechanism provided, may leave residual state file entries.
- Manual fallback hardcodes path, may be inconsistent with other installation methods.
- Publisher unverified, limited identity info, affects trust assessment.
What does this skill do, and when should you use it?
This skill sets a custom name for the current Claude Code session, displayed in desktop notification titles and the terminal tab title. It intercepts the /peon-ping-rename command via a UserPromptSubmit hook, stores the session name in .state.json, and immediately updates the terminal tab title using an ANSI escape sequence, consuming zero tokens. The name takes priority over other auto-detection methods and can be reset to auto-detect at any time.
When the user types /peon-ping-rename <name>, the skill intercepts the command via a UserPromptSubmit hook, extracts the session ID and name, writes session_names[session_id] = name to .state.json, and immediately updates the terminal tab title via ANSI escape sequence, returning confirmation with zero tokens used. It also provides a manual fallback: get the session ID, write the name to .state.json, and trigger a hook event to refresh the tab title.
- A user wants to give the current Claude Code session a custom name to clearly identify it in notifications.
- A user runs multiple sessions in the same repo and wants independent names for each tab.
- A user wants the terminal tab title to reflect a meaningful project or task name instead of the auto-detected one.
- A user wants to reset the session name to auto-detect again.
What are this skill's strengths and limitations?
- Works instantly with zero token cost.
- Name appears in both notification titles and terminal tab for better visibility.
- Supports per-session naming for multiple tabs.
- Provides manual fallback steps in case the hook fails.
- Specifically designed for Claude Code; may not work in other IDEs.
- Requires installing the full peon-ping collection; cannot be used standalone.
- Manual fallback requires knowing the session ID and editing JSON files, which may be a barrier for less technical users.
How do you install this skill?
Install the entire peon-ping collection using one of the official installation methods: Homebrew (brew install PeonPing/tap/peon-ping), the install.sh script (macOS/Linux/WSL2), or install.ps1 for Windows. The skill (skills/peon-ping-rename/SKILL.md) is included with the installation.
How do you use this skill?
In a Claude Code session, type /peon-ping-rename followed by the desired name (e.g., /peon-ping-rename Auth Refactor) to set a custom name. To reset to auto-detect, type /peon-ping-rename with no arguments.