CtrlK
BlogDocsLog inGet started
Tessl Logo

github-worktree

须用户 @ 本 skill 或明确说要按 GitHub Issue worktree 流程执行时再读取。 在 master 上:确定关联的 GitHub Issue(默认关联已有,明确要建时才在上游建单)、生成分支名、git fetch、脚本同时创建新分支与 worktree、cursor --new-window 打开新窗口;细节与分支命名见正文。 不因泛泛提到 GitHub、issue、worktree、建分支等词而自动套用。

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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 tightly structured, executable workflow with concrete commands, clear sequencing, validation checkpoints, and well-organized external script references. Only minor conciseness trimming in the example tables would improve it further.

DimensionReasoningScore

Conciseness

Mostly efficient operational prose (commands, tables, MCP call blocks) with little concept padding, though the keyword-extraction examples and issue-title tables are somewhat verbose and could be tightened slightly.

4 / 5

Actionability

Provides copy-paste-ready executable guidance throughout — exact git/MCP commands with full arguments, OS-specific script invocations with concrete flags, and worked branch-naming examples covering the common cases.

5 / 5

Workflow Clarity

A clear 5-step sequence with explicit prerequisite checks (environment, branch, MCP availability), a hard no-modification constraint, and feedback loops for failure cases (branch-exists conflict, jOOQ/db failure exit) at the validation checkpoints.

5 / 5

Progressive Disclosure

SKILL.md serves as a clear overview with one-level-deep, well-signaled references to two real bundle scripts (git-worktree.ps1 / git-worktree.sh) summarized in a table, with implementation appropriately externalized and no nested references.

5 / 5

Total

19

/

20

Passed

Description

92%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 specific, trigger-aware, and distinct, clearly stating both the workflow's concrete actions and the precise conditions under which it should activate. Its main limitation is that trigger coverage leans on exclusion language rather than enumerating a wide range of inclusive natural synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — determine linked GitHub Issue, generate branch name, git fetch, script-driven branch+worktree creation, and cursor --new-window — giving comprehensive coverage of the workflow's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (master-branch issue→branch→worktree→new-window flow) and 'when' (only when @-invoked or explicitly requested), with concrete trigger guidance and the anti-auto-apply guard.

5 / 5

Trigger Term Quality

Includes natural trigger phrasing ('@ 本 skill', '明确说要按 GitHub Issue worktree 流程执行') plus an explicit anti-trigger clause, but coverage is framed mainly as exclusion criteria rather than a broad set of inclusive synonyms.

4 / 5

Distinctiveness Conflict Risk

Narrow niche (bk-ci GitHub Issue worktree flow on master) with explicit guard against firing on generic mentions of GitHub/issue/worktree/branch, minimizing conflict risk.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
TencentBlueKing/bk-ci
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.