CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

new-branch

Name and create a task branch from fresh origin/main, and rotate a task-owned worktree to a new branch after its PR merges. Use when asked for a fresh branch, when /ship needs a branch for detached work, and after a merge.

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 an excellent example of skill content: fully executable commands, a decision procedure with look-first checks, and unusually thorough validation before the risky rotation step. Its only flaw is a small duplicated explanation of squash-merge behavior across two sections.

DimensionReasoningScore

Conciseness

The body is lean and assumes git competence throughout, but the squash-merge explanation ("squash merges leave the source commits off `main`'s history") is stated twice — once in Create and again in After a merge — a minor duplication that could be trimmed.

4 / 5

Actionability

Every command is real and executable (the name-generation bash script is copy-paste ready), and runtime placeholders like <mergeCommit.oid> and <ship_merge_head_oid> each come with a documented source command (gh pr view --json mergeCommit / headRefOid).

5 / 5

Workflow Clarity

Create opens with look-first checks and a three-case decision procedure, and After a merge specifies explicit validation (mergeCommit ancestry, clean-tree check with path excludes, unpushed-commit check, headRefOid match, cat-file/merge-base proofs) plus error-recovery feedback ("wait a few seconds and fetch again", "keep the branch").

5 / 5

Progressive Disclosure

This is a compact single-purpose skill with no bundle files; its three sections (Name, Create, After a merge) are well organized, nothing that belongs in a separate file is inlined, and the one cross-skill pointer (babysit-pr) is clearly signaled.

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.

A strong description: concrete, comprehensive actions paired with an explicit "Use when" clause containing specific triggers. The only weakness is slight trigger-term coverage, as it misses common synonyms like "new branch".

DimensionReasoningScore

Specificity

"Name and create a task branch from fresh origin/main" and "rotate a task-owned worktree to a new branch after its PR merges" list three concrete actions that comprehensively cover the skill's scope, matching the top anchor rather than the minor-gaps level.

5 / 5

Completeness

The description explicitly answers what (name, create from fresh origin/main, rotate a worktree after merge) and when ("Use when asked for a fresh branch, when /ship needs a branch for detached work, and after a merge") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Triggers "fresh branch", "after a merge", and "when /ship needs a branch" are natural phrasings, but common variations such as "new branch" or "create a branch" are missing, fitting the good-coverage-with-a-few-gaps anchor.

4 / 5

Distinctiveness Conflict Risk

Terms like "task branch", "task-owned worktree", "/ship", and "after its PR merges" carve out a clear niche with minimal overlap risk against generic git or branch-management skills.

5 / 5

Total

19

/

20

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.

Validation — 13 / 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

BuilderIO/agent-native

Path

.agents/skills/new-branch/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.