CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

peon-ping-rename

Rename the current Claude session for peon-ping notifications and terminal tab title. Use when user wants to give this session a custom name like "/peon-ping-rename Auth Refactor". Call with no argument to reset to auto-detect.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exemplary lean skill document: it explains the hook mechanism concisely, provides concrete usage examples with input constraints, includes a fully executable manual fallback, and closes with the exact name-resolution priority chain. Structure is clean and appropriately sized for the content with no need for external reference files.

DimensionReasoningScore

Conciseness

The 63-line body is lean and operational throughout: no explanations of hooks, ANSI escapes, JSON, or other concepts Claude already knows, and every section earns its place (the only nit is the Reset section restating the usage line). Matches the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Fully executable guidance: concrete usage examples ('/peon-ping-rename Auth Refactor', reset form), 'echo "$CLAUDE_SESSION_ID"', and a complete copy-paste-ready python3 snippet for the manual fallback, with only clearly marked placeholders (SESSION_ID_HERE) to substitute. Covers the common cases (set name, reset name).

5 / 5

Workflow Clarity

The automatic path is a clear 4-step sequence (extract ID, write state, update tab title, confirm) and the manual fallback is three well-sequenced steps ending in an explicit refresh action ('Submit any prompt — peon.sh will pick up the new name'). This is a simple single-purpose skill with an unambiguous action and no destructive/batch operation, so the simple-skill exception applies.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed; all content fits comfortably in SKILL.md. The body is well organized into clearly signaled sections (How it works, Usage, Manual fallback, Reset, Priority), which per the scoring note earns a 5 for a small skill with well-organized sections.

5 / 5

Total

20

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states what the skill does, gives an explicit 'Use when...' clause with a concrete example invocation, and covers the reset behavior. It is highly distinctive thanks to the peon-ping domain and named command. The only improvements are minor: broader natural trigger synonyms and slightly fuller action coverage.

Suggestions

Add one or two natural trigger synonyms users might say, such as 'name this tab', 'label the session', or 'session title', to lift trigger term coverage from good to comprehensive.

Mention that names appear independently per terminal tab (a distinctive capability) to round out the specificity of the listed actions.

DimensionReasoningScore

Specificity

Lists several concrete actions — renaming the session for 'peon-ping notifications and terminal tab title' and 'Call with no argument to reset to auto-detect' — with only minor gaps in coverage (e.g., manual fallback and multi-tab independence are not mentioned). It is not a 5 because coverage is not comprehensive, and clearly above 3 because the actions are specific rather than generic.

4 / 5

Completeness

Explicitly answers both what ('Rename the current Claude session for peon-ping notifications and terminal tab title') and when ('Use when user wants to give this session a custom name like "/peon-ping-rename Auth Refactor". Call with no argument to reset to auto-detect.') with concrete trigger phrases. This matches the top anchor exactly; a 4 would require the 'when' clause to be less explicit or specific, which it is not.

5 / 5

Trigger Term Quality

Includes natural trigger phrases a user would say — 'rename', 'give this session a custom name', 'peon-ping notifications', 'terminal tab title' — plus a concrete example invocation ('/peon-ping-rename Auth Refactor'). A few natural synonyms are missing (e.g., 'name this tab', 'label the session'), so it falls short of the comprehensive coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — session naming for the peon-ping notification system with a uniquely named command ('peon-ping-rename') — so it is unlikely to trigger for the wrong skill. No overlap risk with generic skills; matches the top anchor.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

PeonPing/peon-ping

Path

skills/peon-ping-rename/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.