CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dupe

No-op workflow for when the user says they duplicated the chat/session into another tab. Use when invoked as `$dupe` or when the user says this tab was duplicated and no action is needed.

Quality

93%

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 a model of minimal, unambiguous instruction for a no-op skill: it states the action, the acknowledgment behavior, and explicit prohibitions in three lines. There is no padding, no ambiguity, and no missing structure for a skill of this size.

DimensionReasoningScore

Conciseness

The body is three lean lines: 'Do nothing' followed by one sentence of boundary guidance. Every token earns its place, nothing over-explains, and it fully assumes Claude's competence.

5 / 5

Actionability

For an instruction-only skill the guidance is fully actionable: it names the single action ('Acknowledge briefly if needed, then stop') and concrete prohibitions ('without changing files, running commands, or continuing stale work'). This matches the copy-paste-ready top anchor for an instruction skill.

5 / 5

Workflow Clarity

The simple-skill exception applies: single task, under 50 lines, and the single action is unambiguous with explicit guardrails. There are no destructive or batch operations, so no validation checkpoint is required.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in the bundle), and the content is well organized under a single heading. Per the rubric's guidance this earns the top score with just well-organized sections.

5 / 5

Total

20

/

20

Passed

Description

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

The description is a strong, honest fit for its purpose: it declares the no-op behavior explicitly and gives precise, natural triggers including the `$dupe` alias. Its only ceiling is specificity, which is inherently limited for a do-nothing skill, and a few missing synonyms like 'cloned' or 'forked'.

Suggestions

Add common synonyms for the trigger, e.g. 'cloned', 'copied the conversation', or 'forked the session', to widen natural-term coverage.

Optionally state the expected outcome in one clause (e.g. 'acknowledge briefly, then stop') to enrich the 'what' beyond 'No-op workflow'.

DimensionReasoningScore

Specificity

The description states the domain and the concrete behavior ('No-op workflow', acknowledge, take no action), which is as much action surface as a no-op skill can enumerate. It does not reach 'several specific actions' (4) because there is little more to list, and it is well above 'actions minimal or generic' (2) since the behavior is stated precisely.

3 / 5

Completeness

Both parts are explicit: the 'what' ('No-op workflow... no action is needed') and a concrete 'Use when' clause with specific trigger phrases ('invoked as `$dupe` or when the user says this tab was duplicated'). This matches the anchor that clearly answers both what and when with concrete triggers.

5 / 5

Trigger Term Quality

Natural phrases a user would actually say are present: 'duplicated the chat/session into another tab', 'this tab was duplicated', and the invocation alias '$dupe'. A few natural variants (cloned, copied the conversation, forked) are missing, keeping it below the comprehensive-synonym level (5).

4 / 5

Distinctiveness Conflict Risk

The niche is very distinct — tab/session duplication and the `$dupe` invocation — so it is unlikely to trigger for unrelated skills. It sits clearly at the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

17

/

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

phatblat/dotfiles

Path

.agents/skills/dupe/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.