CtrlK
BlogDocsLog inGet started
Tessl Logo

git-workflow

Use this skill when working with git — making commits, creating branches, resolving merge conflicts, opening pull requests, or reviewing diffs. Apply whenever the user asks about version control operations.

75

Quality

93%

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

87%Weight 40%Scale 1-3

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

The body is concise and actionable with concrete commands and clean section organization. Its only weakness is workflow clarity: it offers advisory best practices rather than a sequenced, checkpointed procedure.

Suggestions

Add a short sequenced workflow for a representative task (e.g., commit → branch → push → open PR) with an explicit validation checkpoint such as running tests or 'git status' before committing, to lift workflow_clarity above 2.

For destructive operations already flagged in the 'Never' section (force-push, --no-verify), include a one-line verification or recovery note so risky actions carry a feedback step.

Consider a brief 'Verify before pushing' checklist (e.g., 'git diff --cached', 'git log') to turn the commit guidance into a checkpointed procedure.

DimensionReasoningScore

Conciseness

Lean bullet lists with no concept-padding or unnecessary explanation; every token earns its place and it assumes Claude's competence, matching the lean-and-efficient anchor.

3 / 3

Actionability

Provides concrete, executable commands ('git add <file>', 'git checkout -b feature/my-change', 'Closes #123', '--no-verify') rather than vague direction, satisfying actionable guidance for an instruction-oriented skill.

3 / 3

Workflow Clarity

Content is organized into clear categories (Commits/Branches/PRs/Never) but presents parallel best-practice lists rather than a sequenced multi-step workflow, and includes no validation or feedback checkpoints. It is not score 1 because the organization is clear, but lacks the explicit checkpoints required for score 3.

2 / 3

Progressive Disclosure

Under 50 lines with no external references needed and well-organized sections, meeting the simple-skill allowance for a top progressive-disclosure score; no bundle files exist to require deeper structuring.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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-rich, and complete with an explicit 'Use when' clause, all scoped to a distinct git niche. It matches the rubric's good examples closely.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('making commits, creating branches, resolving merge conflicts, opening pull requests, or reviewing diffs'), matching the anchor for multiple specific concrete actions; the imperative 'Use this skill when...' mirrors the rubric's good examples rather than the penalized 'You can use this' form.

3 / 3

Completeness

Explicitly answers both what (the five git operations) and when ('Use this skill when working with git ... Apply whenever the user asks about version control operations'), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Covers natural terms users actually say — 'git', 'commits', 'branches', 'merge conflicts', 'pull requests', 'diffs', 'version control operations' — giving good coverage rather than just a few relevant keywords.

3 / 3

Distinctiveness Conflict Risk

A clearly git-specific niche with distinct version-control triggers, unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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
aiming-lab/MetaClaw
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.