new-branch

Only when explicitly asked for /new-branch or a fresh git branch: stash local changes, update main, and create it. Do not auto-run for normal coding, PR, Builder.io, or Fusion branch workflows.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

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

An actionable, well-sequenced skill with strong validation and recovery feedback loops appropriate to its destructive-adjacent git operations. Its main weakness is conciseness: several rationale phrases are repeated verbatim across sections and could be consolidated without losing clarity.

Suggestions

Consolidate the repeated 'orphans are how we've lost work' phrasing into a single stated rationale and reference it by name, rather than restating it in Pre-flight, Steps, After-creation, and Post-flight.

Trim the repeated warnings about never stashing silently into one canonical statement in the activation guard, since the gated command already enforces it.

Shorten the prose around 'Why the gate' to the essential invariant (only pop a stash we just created) and move the detailed git-exit-code reasoning to a brief parenthetical.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and actionable, but repeats the same rationale phrases multiple times ("orphans are how we've lost work in the past" appears ~4 times, and the stashing-silently warning recurs), so it could be tightened; not 3 because some explanatory prose does not earn its place on repeat, and not 1 because the content is genuinely non-obvious git behavior rather than padding about concepts Claude already knows.	2 / 3
Actionability	Provides a fully executable chained bash command plus concrete recovery commands (git checkout --merge, git branch -D, git stash list) and a copy-paste branch-numbering command; only the <branch-name> placeholder is left to fill.	3 / 3
Workflow Clarity	Clear sequenced workflow (guard -> pre-flight verify main -> chained steps -> naming -> conflict recovery -> post-flight) with explicit validation (compare merge-commit SHA before branching) and feedback loops (conflict => abort and surface; orphaned stash => surface); not 2 because checkpoints and recovery are explicit.	3 / 3
Progressive Disclosure	Single self-contained SKILL.md with no bundle files, organized into clearly labeled sections; per the simple-skills note, a single-file skill with well-organized sections scores 3 without external references.	3 / 3
	Total	11 / 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.

A highly specific, well-triggered description that clearly states both what it does and when to use it, with explicit anti-triggers that sharply reduce conflict risk. Voice is third person throughout, so no specificity penalty applies.

Dimension	Reasoning	Score
Specificity	Names three concrete actions — "stash local changes, update main, and create it" — matching the anchor for listing multiple specific concrete actions; not below because the actions are explicit and operational, not abstract.	3 / 3
Completeness	Explicitly answers both what (stash, update main, create branch) and when ("Only when explicitly asked for /new-branch or a fresh git branch"), with an explicit trigger clause; not 2 because the 'when' is directly stated rather than implied.	3 / 3
Trigger Term Quality	Covers natural trigger terms ("asked for /new-branch", "fresh git branch") plus common anti-triggers users would say ("normal coding, PR, Builder.io, or Fusion"); good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Has a clear niche and explicitly carves out non-applicable workflows (PR, Builder.io, Fusion), making it unlikely to trigger for the wrong skill; not 2 because the exclusion list removes the main overlap risks.	3 / 3
	Total	12 / 12 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Commit: c1ee18b

Reviewed: 5 days 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.