CtrlK
BlogDocsLog inGet started
Tessl Logo

git-master

Git expert for atomic commits, rebasing, and history management

64

Quality

75%

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

Quality

Content

100%

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

The content is a tight, well-structured routing skill: it states the command, the exact routing directive, and a concise capability list with no filler. For a simple single-purpose skill it hits the bar on conciseness, actionability, workflow clarity, and organization.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no concept explanation Claude already knows, and every line (usage command, routing directive, capability bullets) earns its place, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It gives a concrete usage command '/git-master <git task>' and an exact routing directive 'Use /prompts:git-master with the user task.' that is copy-paste ready, matching the fully executable guidance anchor.

3 / 3

Workflow Clarity

This is a simple single-action routing skill whose single action (route via /prompts:git-master) is unambiguous, which per the simple-skills scoring note can score 3 without a multi-step workflow.

3 / 3

Progressive Disclosure

The skill is well under 50 lines, needs no external references, and is organized into clear sections (Usage, Routing, Capabilities), satisfying the <50-line note that well-organized sections alone can score 3.

3 / 3

Total

12

/

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 states a clear git-focused purpose with several recognizable capability terms, but it lacks an explicit 'when to use' trigger clause and relies on topic labels rather than comprehensive concrete actions. It is functional but stops just short of being fully specific or trigger-complete.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to rebase, write atomic commits, manage branches, or clean up git history.'

Expand capability terms with natural user phrasings like 'commit messages', 'branches', and 'rebase' to improve trigger term coverage.

Replace the vague label 'Git expert' with a concrete verb-led action statement (e.g. 'Writes atomic commits, rebases branches, and manages git history').

DimensionReasoningScore

Specificity

Phrases 'atomic commits, rebasing, and history management' name the git domain and several actions, matching the anchor that lists domain and some actions but is not comprehensive; it does not reach 3 because the actions are topic labels rather than a fuller set of concrete operations.

2 / 3

Completeness

It clearly states what the skill does ('Git expert for atomic commits, rebasing, and history management') but provides no 'Use when...' or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Terms like 'commits', 'rebasing', and 'history management' are relevant and somewhat natural, but common user variations ('commit messages', 'branches', 'rebase') are missing, matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The git-focused niche with atomic commits and rebasing is specific, but the description could still overlap with other general git skills, matching the 'somewhat specific but could still overlap' anchor rather than a clearly distinct niche.

2 / 3

Total

8

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Yeachan-Heo/oh-my-codex
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.