CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

half-clone

Clone the later half of the current conversation, discarding earlier context to reduce token usage while preserving recent work.

62

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/half-clone/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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, fully executable workflow: concrete commands, an explicit verification step before the irreversible clone, and precise guidance on passing the project path. Its only weaknesses are the redundant opening line and the absence of an explicit error-recovery branch when the preview verification fails.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (exact shell commands, no concept explanations); the only trim candidate is the opening line, which restates the frontmatter description verbatim. Not 5 because that duplicated sentence costs tokens without adding information; not 3 because there is no over-explanation.

4 / 5

Actionability

Every step is copy-paste ready: the exact `tail -1 ~/.claude/history.jsonl | jq -r ...` command, a version-sorted `find` for the script, preview/run invocations, and the exact `claude --resume <new-session-id>` command. The `<script-path>` placeholder is resolved by step 2, so the guidance is fully executable and covers the common cases.

5 / 5

Workflow Clarity

Clear numbered sequence with an explicit validation checkpoint (step 3: preview and 'Check that the first and last messages match the current conversation'), plus a fallback path for resuming. Not 5 because there is no error-recovery branch for what to do when the preview does not match; not 3 because a concrete checkpoint is explicitly present.

4 / 5

Progressive Disclosure

A single-task skill under 50 lines with no bundle files (no references/, scripts/, or assets/ directories) and no need for external references; the well-organized numbered steps and the dynamic script-lookup note with rationale satisfy the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

58%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 communicates a clear, specific capability in a lean third-person sentence, but it lacks any 'Use when...' trigger guidance and misses common user phrasings like 'compact' or 'trim the conversation'. It is distinct from other skills yet would benefit from explicit trigger conditions to improve discoverability.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the conversation has grown long, the user asks to compact/trim/clone the conversation, or token usage from earlier context is high.'

Include common user-facing synonyms for the operation (compact, trim, truncate, shrink context) in the description so natural trigger phrases match.

State the outcome the user receives (a new session ID to resume that contains the recent half), completing the 'what' with how the result is delivered.

DimensionReasoningScore

Specificity

Names several concrete actions ('Clone the later half of the current conversation', 'discarding earlier context', 'reduce token usage', 'preserving recent work'), though coverage has minor gaps (e.g., no mention of how the cloned session is delivered or resumed). Not 5 because it is not a comprehensive multi-action list; not 3 because more than 1-2 specific actions are stated.

4 / 5

Completeness

Has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance; the purpose clause ('to reduce token usage while preserving recent work') only weakly implies 'when'. Per the judging guideline, a missing 'Use when...' caps completeness at 3.

3 / 5

Trigger Term Quality

'clone', 'conversation', 'token usage', and 'context' are relevant natural keywords, but common variations users would say are missing ('compact', 'trim', 'truncate the conversation', 'context window'). Not 4 because several natural trigger phrases are absent; not 2 because more than one or two generic keywords are present.

3 / 5

Distinctiveness Conflict Risk

Conversation half-cloning is a distinct niche with specific triggers ('clone', 'later half', 'current conversation'), with only minor overlap risk against context-compaction/summarization skills. Not 5 because those closely related skills share trigger territory; not 3 because the niche is well carved out.

4 / 5

Total

14

/

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

ykdojo/claude-code-tips

Path

skills/half-clone/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.