git-master
Git expert - atomic commits, branching, version control
56
Quality
43%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/git-master/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too terse and abstract to effectively guide skill selection. It reads more like a tag list than a functional description, lacking concrete actions the skill performs and completely missing trigger guidance for when Claude should use it. The git domain provides some distinctiveness, but the vague language undermines its utility.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when the user asks about git workflows, branch management, merge conflicts, or commit strategies'
Replace abstract concepts with concrete actions: 'Creates atomic commits, manages branches, resolves merge conflicts, reviews git history' instead of 'Git expert'
Include more natural trigger terms users would say: 'merge', 'rebase', 'pull request', 'PR', 'checkout', 'git log', 'diff'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language ('Git expert', 'version control') without listing concrete actions. It names concepts but doesn't describe what actions the skill actually performs. | 1 / 3 |
Completeness | Only weakly addresses 'what' (vague concepts) and completely missing 'when' - no 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords users might say ('git', 'commits', 'branching', 'version control') but missing common variations like 'merge', 'rebase', 'pull request', 'push', 'checkout', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | The git/version control domain is somewhat specific, but 'atomic commits' could overlap with commit message skills, and the vague framing could conflict with other development-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable git guidance with good examples and executable commands. However, it includes some unnecessary persona framing and lacks validation checkpoints for workflows that could benefit from them (especially around rebasing and conflict resolution). The structure is adequate but could benefit from better progressive disclosure for the reference material.
Suggestions
Remove the persona introduction and closing quote to improve conciseness - Claude doesn't need to be told it's 'Git Master'
Add validation checkpoints to workflows, e.g., 'git status' after staging, 'git log --oneline -3' after committing to verify
Include error recovery guidance for common issues like merge conflicts, failed rebases, or accidental commits to wrong branch
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary elements like the persona introduction ('You are Git Master'), the closing quote, and explanatory text that Claude already knows (e.g., 'Future you will thank you'). The core content is reasonably tight. | 2 / 3 |
Actionability | Provides fully executable bash commands, concrete commit message examples with proper format, and copy-paste ready workflows for feature branches and hotfixes. The examples are specific and immediately usable. | 3 / 3 |
Workflow Clarity | Workflows are listed with clear sequences (feature branch, hotfix), but lack validation checkpoints. No mention of verifying commits worked, checking branch state, or handling merge conflicts. For git operations that can be destructive (rebase), no recovery guidance is provided. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but everything is inline in one file. For a skill of this size (~80 lines), some content like the full commit type reference or detailed workflows could be split into separate files. No external references are provided. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- TurnaboutHero/oh-my-antigravity
- Commit
fab464f
- 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.