CtrlK
BlogDocsLog inGet started
Tessl Logo

git-workflow

Squad branching model: dev-first workflow with insiders preview channel

56

Quality

65%

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 ./.copilot/skills/git-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The content is lean, executable, and well-sequenced, providing copy-paste-ready git/gh commands for the Squad model. Its main gaps are missing validation checkpoints around destructive operations and no progressive disclosure to split the longer worktree/multi-repo sections into reference files.

Suggestions

Add explicit validation/verification checkpoints before destructive steps (e.g., confirm the build is green and the PR is merged before deleting a branch or removing a worktree).

Split the worktree and multi-repo sections into one-level-deep reference files (e.g., WORKTREES.md, MULTI-REPO.md) referenced from the main body to improve progressive disclosure.

Add a brief verification step in the issue workflow (e.g., run tests, confirm gh pr checks passes) before marking the PR ready.

DimensionReasoningScore

Conciseness

The body assumes Claude knows git/gh and only adds Squad-specific conventions, using compact tables and copy-paste commands with no padding or explanation of basic concepts.

3 / 3

Actionability

It provides fully executable, specific commands throughout (git checkout -b, gh pr create --base dev, git worktree add, npm link) with clearly templated placeholders, making the guidance copy-paste ready.

3 / 3

Workflow Clarity

Steps are clearly sequenced (numbered issue workflow, worktree setup, cleanup), but destructive/batch operations (branch deletion, git push --delete, worktree remove) lack explicit validation checkpoints, capping this at 2.

2 / 3

Progressive Disclosure

Sections are well-organized with clear headers, but the skill exceeds 50 lines and keeps worktree and multi-repo material entirely inline with no one-level-deep references to separate files.

2 / 3

Total

10

/

12

Passed

Description

50%

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 conveys a clear, project-specific branching model but reads as a structural label rather than an action-oriented, trigger-rich summary. Adding concrete actions and an explicit "Use when..." clause would lift specificity and completeness.

Suggestions

Add an explicit "Use when..." trigger clause (e.g., when the user needs to branch, open PRs, or publish under the Squad model).

List concrete actions the skill performs (e.g., create squad branches, open draft PRs to dev, publish --tag preview/insiders).

Include natural user-facing keywords (branching, PRs, merging, preview/insiders release) alongside the project jargon.

DimensionReasoningScore

Specificity

The description names the domain and specifics ("dev-first workflow", "insiders preview channel") but does not list multiple concrete actions; it describes a model rather than operations like branching, merging, or publishing.

2 / 3

Completeness

It states what the skill covers but provides no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

It contains some relevant natural keywords ("branching model", "workflow") but leans on Squad-specific jargon ("insiders preview channel") and misses common user variations and explicit trigger phrasing.

2 / 3

Distinctiveness Conflict Risk

The "Squad" qualifier and insiders channel give it a niche, but without explicit triggers it could still overlap with a generic git-branching workflow skill.

2 / 3

Total

8

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
bradygaster/squad
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.