CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-worktree-clean

Use when the user wants to audit local git worktrees against origin/x, choose by number or A, and decide whether stale worktree directories, already-merged worktrees, or no-delta worktrees can be cleaned up. Triggers on "worktree clean", "worktree 合并到 x", "检测哪些 worktree 已进 x".

79

Quality

100%

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%

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, executable orchestration guide with a clear sequenced workflow, strong validation/confirmation safeguards for destructive operations, and appropriate offloading of implementation detail to a single bundled script. It assumes Claude's competence and wastes few tokens.

DimensionReasoningScore

Conciseness

Lean, instruction-dense body with no concept tutorials or padding about git/worktrees; every section is actionable rule, command, or contract, with only minor reinforcing repetition across Rules and Output Contract.

3 / 3

Actionability

Provides fully executable commands — 'rtk proxy bash .../1k-worktree-clean.sh list|check|cleanup-candidates', 'rtk git fetch origin x', 'rtk git worktree remove <path>' — with concrete argument examples and clearly marked placeholders.

3 / 3

Workflow Clarity

Clear 5-step sequence (List, Sync, Check, Surface Candidates, Delete) with explicit validation checkpoints: fetch-before-check, sandbox-approval rerun loops, and a hard user-confirmation gate before any destructive deletion.

3 / 3

Progressive Disclosure

Well-organized into Rules, Steps, interpretation, and Output Contract, with heavy logic offloaded to a real one-level-deep bundle script (scripts/1k-worktree-clean.sh) referenced by actual path; no nested references or monolithic walls.

3 / 3

Total

12

/

12

Passed

Description

100%

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 specific, complete, and distinctive, naming concrete actions and explicit trigger phrases in both English and Chinese. It clearly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'audit local git worktrees against origin/x', 'choose by number or A', and deciding cleanup eligibility for stale/already-merged/no-delta worktrees — rather than vague domain naming.

3 / 3

Completeness

Explicitly answers both what (audit worktrees and judge cleanup eligibility) and when, via an explicit 'Use when...' clause plus a 'Triggers on...' list.

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would say, including 'worktree clean', 'worktree 合并到 x', and '检测哪些 worktree 已进 x', with bilingual coverage and no jargon-only terms.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (worktree cleanup auditing against origin/x) with distinct triggers, making overlap with general git skills unlikely.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
OneKeyHQ/app-monorepo
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.