clean-copy

Reimplement the current branch on a new branch with a clean, narrative-quality git commit history. Use when asked to make a clean copy branch, clean up commit history by replaying work, or rebuild a branch as reviewable commits.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

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.

The body is a tight, well-sequenced git workflow with explicit validation and verification checkpoints appropriate to a destructive history-rebuilding task. Its only relative weakness is actionability, limited by the inherent unpredictability of the 'reimplement the work' step rather than by poor writing.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's git competence, with terse steps like 'Source branch: `git branch --show-current`' and no padding explaining git concepts, so every token earns its place.	5 / 5
Actionability	Step 1 gives concrete executable commands and later steps give specific flags (`git commit --no-verify`), but the core 'Recreate the final changes step by step' step is inherently user-specific and not copy-paste ready, leaving minor gaps.	4 / 5
Workflow Clarity	The 9-step sequence has explicit validation checkpoints (step 2 validates the source branch; step 8 verifies the final state matches the original and runs the final commit without `--no-verify`), providing a clear feedback loop for this history-rebuilding operation.	5 / 5
Progressive Disclosure	At under 50 lines with a single purpose and no need for external references, the well-organized Workflow and Rules sections meet the simple-skill exception for a top score on progressive disclosure.	5 / 5
	Total	19 / 20 Passed

Description

78%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 well-constructed: it clearly states the capability and provides explicit, natural trigger phrases covering what and when. Specificity is its weakest dimension because it names only a couple of concrete actions rather than enumerating the full set of operations the skill performs.

Dimension	Reasoning	Score
Specificity	Names the git-branch domain and the concrete actions 'Reimplement the current branch on a new branch' and 'rebuild...reviewable commits', but covers only 1-2 actions rather than a comprehensive list of sub-operations, matching the anchor for 1-2 concrete actions.	3 / 5
Completeness	It explicitly answers both what ('Reimplement the current branch on a new branch with a clean, narrative-quality git commit history') and when ('Use when asked to make a clean copy branch, clean up commit history by replaying work, or rebuild a branch as reviewable commits') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user phrases like 'clean copy branch', 'clean up commit history', and 'rebuild a branch as reviewable commits' provide good keyword coverage with synonyms, though a few common variants like 'rewrite history' or 'squash' are missing.	4 / 5
Distinctiveness Conflict Risk	The clean-copy/replay-history niche is clearly distinct from generic git or commit-message skills, with only minor overlap risk against closely related history-rewriting skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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: tldraw/tldraw
Path: skills/clean-copy/SKILL.md
Commit: 91878fe

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.