CtrlK
BlogDocsLog inGet started
Tessl Logo

git-workflow

Defines branch naming conventions, PR template requirements, commit message format, discovered-issues escalation policy, task tracking conventions. Load when committing, pushing, or opening PRs.

74

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

An excellent, lean instruction-only skill: rules are expressed as dense tables and executable commands, the delivery workflow is unambiguous, and escalation/tracking policies are concrete. The only gap is the absence of a post-PR validation step in the checklist.

DimensionReasoningScore

Conciseness

The body uses dense tables and bold imperatives with zero padding; it assumes Claude's git knowledge and every rule is load-bearing, matching the lean-and-efficient anchor.

5 / 5

Actionability

Guidance is fully executable: a copy-paste-ready `gh pr create` heredoc snippet, the concrete branch command `git checkout -b <type>/<ticket-id>-<slug>`, an exact commit format example (`TAS-42: Fix token refresh`), and six named required fields for issue tracking.

5 / 5

Workflow Clarity

The numbered 5-step "Delivery Checklist (Every Task)" is clearly sequenced with concrete commands, but there is no explicit validation checkpoint (e.g., verify the PR opened or CI passed), leaving a minor validation gap.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clear sections (Branch & Commit Rules, Delivery Checklist, Discovered Issues Policy, Task Tracking), qualifying for the top score under the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

88%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: specific, third-person, comprehensive on the 'what', with an explicit 'Load when...' trigger clause. The only weaknesses are a few missing natural trigger synonyms and slight overlap with task-tracking skills.

DimensionReasoningScore

Specificity

The description lists five specific, distinct capabilities ("branch naming conventions, PR template requirements, commit message format, discovered-issues escalation policy, task tracking conventions"), comprehensively covering the delivery workflow rather than leaving minor gaps.

5 / 5

Completeness

It explicitly answers both what ("Defines branch naming conventions...") and when ("Load when committing, pushing, or opening PRs") with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

"Load when committing, pushing, or opening PRs" provides good natural trigger phrases, but common synonyms such as "pull request", "merge", or "commit message" are missing, so coverage falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The git-delivery niche is clearly distinct, but "task tracking conventions" creates minor overlap risk with a dedicated task-management skill, placing it at the mostly-distinct anchor rather than minimal conflict risk.

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
monkilabs/opencastle
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.