CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rename-chat

Rename the current chat to match its focus. Use only when the user invokes /rename-chat. Optional text after the command steers the title.

Quality

91%

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

92%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.

An exemplary short-form skill body: exact tool name, concrete worked example, tight constraints, and honest failure handling with zero padding. The only nit is a slight redundancy in hint semantics and an unnecessary definition of sentence case that could be trimmed to save a handful of tokens.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence ("Slash-only. Text after `/rename-chat` is an optional naming hint, not a verbatim title."), but two minor trims exist: "first letter uppercase, rest lowercase except acronyms and proper nouns" re-explains sentence case, and "Hint steers wording only" restates the hint semantics already given in the first paragraph. This matches anchor 4 ("minor instances of over-explanation that could be trimmed") rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Fully actionable for an instruction-only skill: the exact tool call is named ("Call `cursor-app-control.rename_chat` once with that title"), a worked example is given ("hint `billing retries` → `Billing retries`"), and precise constraints cover the common case (3-5 words, sentence case, "At most 200 characters", avoid-list, single call, no confirmation).

5 / 5

Workflow Clarity

A simple single-task skill whose single action is unambiguous: derive the title, call the tool once, and handle failure ("If the tool is missing or fails, say so plainly and do not claim the chat was renamed"). The operation is non-destructive and non-batch, so the validation cap does not apply, and the simple-skill guideline allows a 5.

5 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained, and needs no external references (no references/, scripts/, or assets/ exist, and none are called for). Content is organized into logically ordered paragraphs — title rules, then invocation, then error handling — which satisfies the simple-skill exception for a top score.

5 / 5

Total

19

/

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 model description for a narrow slash-command skill: concrete capability, explicit exclusive trigger, and hint semantics all stated in three lean sentences. The only improvement space is broader natural-language synonym coverage (e.g., conversation, chat name), which matters little given the skill is invocation-restricted.

DimensionReasoningScore

Specificity

"Rename the current chat to match its focus" is a fully concrete action, and "Optional text after the command steers the title" specifies input handling. It lists one action rather than the several required for anchor 5, but unlike anchor 3 the coverage is complete for this single-purpose skill, placing it above the anchor-3 example ("Processes PDF files and extracts content").

4 / 5

Completeness

Explicitly answers both questions: what ("Rename the current chat to match its focus") and when ("Use only when the user invokes /rename-chat") with a concrete trigger phrase. The 'when' clause is fully explicit, so this is not the anchor-4 case where the trigger could be more specific.

5 / 5

Trigger Term Quality

Natural terms present: "rename", "chat", "title", and the exact command "/rename-chat" with an explicit trigger clause ("Use only when the user invokes /rename-chat"). Common variations such as "conversation" or "change the chat name" are absent, so it falls short of anchor 5's comprehensive synonym coverage but clearly exceeds anchor 3.

4 / 5

Distinctiveness Conflict Risk

The exclusive trigger "Use only when the user invokes /rename-chat" makes accidental activation essentially impossible, and chat renaming is a clear niche with no overlap with other skills — a direct match for anchor 5's "clear niche with distinct triggers; minimal conflict risk".

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

saski/arnesto

Path

.cursor/skills-cursor/rename-chat/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.