CtrlK
BlogDocsLog inGet started
Tessl Logo

using-git-worktrees

当需要开始与当前工作区隔离的功能开发,或在执行实现计划之前使用——通过原生工具或 git worktree 回退机制确保隔离工作区存在

63

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/using-git-worktrees/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, clearly sequenced workflow with strong validation checkpoints, held back by repetition across the quick-reference/mistakes/red-lines sections and the absence of any file-based progressive disclosure.

Suggestions

De-duplicate the 快速参考 table, 常见错误, and 红线 sections — they restate the step guidance; consolidate into one compact reference to reclaim tokens.

Consider moving the 常见错误 / 红线 detail into a separate reference file (e.g., references/pitfalls.md) referenced once from the body, giving the overview a leaner one-level-deep structure.

DimensionReasoningScore

Conciseness

Mostly efficient and free of concept-explanation fluff, but the 快速参考 table, 常见错误, and 红线 sections restate the same guidance already in 步骤 0–3, adding length without new information; it is not a 1 because no basic concepts are over-explained.

2 / 3

Actionability

Provides copy-paste-ready, executable bash throughout — `git rev-parse`, `git check-ignore`, `git worktree add "$path" -b "$BRANCH_NAME"`, and concrete per-language setup commands — fully concrete rather than descriptive.

3 / 3

Workflow Clarity

Sequences 步骤 0→1a→1b→2→3 with explicit validation checkpoints (submodule guard, check-ignore before creation, baseline test verification) and feedback loops (report-and-ask on test failure, sandbox fallback), matching the score-3 anchor.

3 / 3

Progressive Disclosure

Well-organized into clear sections but the ~225-line body is a single monolithic file with no one-level-deep external references to split detail into, so it does not meet the score-3 'appropriately split / well-signaled references' bar; it is not a 1 because the sectioning itself is clean.

2 / 3

Total

10

/

12

Passed

Description

75%

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 clear, third-person description with explicit when/what guidance and a distinct niche, weakened only by trigger phrasing that is somewhat technical and a single-action rather than multi-action specificity.

Suggestions

Broaden natural trigger terms (e.g., add 'worktree', 'isolated branch', 'separate working directory', 'sandbox my changes') so the description matches how users actually phrase the request.

Spell out concrete actions the skill performs — 'detect existing isolation, create a worktree, run project setup, verify a clean test baseline' — to raise specificity from a single stated action to a multi-action list.

DimensionReasoningScore

Specificity

Names the domain (隔离工作区, git worktree) and two concrete mechanisms (原生工具, git worktree 回退), but states essentially one action ('确保隔离工作区存在') rather than listing multiple specific concrete actions like the score-3 anchor.

2 / 3

Completeness

Explicitly answers both what ('确保隔离工作区存在' via native tools/git worktree fallback) and when ('当需要...使用' / '执行实现计划之前'), with an explicit trigger clause that lifts it above the completeness cap of 2.

3 / 3

Trigger Term Quality

Contains relevant trigger phrases ('功能开发', '执行实现计划', '隔离工作区') a user might say, but leans technical/formal and omits common variations; not the broad natural-term coverage of the score-3 example.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (git worktrees / isolated workspaces for feature work) with distinct triggers unlikely to fire for unrelated skills; it is not a 2 because the wording is specific rather than overlapping.

3 / 3

Total

10

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
jnMetaCode/superpowers-zh
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.