push
Pushes the current branch to the remote repository.
72
60%
Does it follow best practices?
Impact
93%
1.22xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/push/SKILL.mdQuality
Discovery
32%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 concise and identifies a specific git operation, but it is too minimal to be effective for skill selection. It lacks a 'Use when...' clause, misses common trigger term variations, and describes only a single action without enough context for Claude to confidently choose this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to push code, sync with remote, git push, or upload changes to the repository.'
Include common trigger term variations such as 'git push', 'push to origin', 'upload commits', 'sync remote', or 'publish branch'.
Expand the capability description slightly to cover edge cases, e.g., 'Pushes the current branch to the remote repository, including setting upstream tracking and force-push options.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a specific domain (git) and a single concrete action (pushes current branch to remote), but only describes one action rather than listing multiple specific capabilities. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also minimal, warranting a 1. | 1 / 3 |
Trigger Term Quality | Contains relevant terms like 'push', 'branch', and 'remote repository' that users might say, but misses common variations like 'git push', 'upload code', 'sync', or 'origin'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to git push operations, but could overlap with broader git workflow skills or deployment skills. The narrow scope helps but the lack of explicit boundaries creates some conflict risk. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise, well-structured skill for a simple task. The commands are concrete and the workflow is straightforward. The main weakness is the lack of error handling guidance for common push failures (rejected pushes, authentication errors, diverged branches), which would make this more robust.
Suggestions
Add error recovery guidance for common push failures (e.g., rejected push due to remote changes: pull/rebase then retry).
Consider adding a brief note on what to do if `git push` is rejected (e.g., `git pull --rebase origin <branch>` then retry).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It doesn't explain what git push does or how git works—it assumes Claude's competence and only provides the specific steps needed. | 3 / 3 |
Actionability | Provides concrete, executable git commands (`git status`, `git push`, `git push -u origin <branch-name>`) with clear conditions for when to use each variant. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced, but there's no error handling or validation. What if `git push` fails due to diverged branches, authentication issues, or rejected pushes? A feedback loop for common push failures is missing. | 2 / 3 |
Progressive Disclosure | This is a simple, single-purpose skill under 50 lines with no need for external references. The content is well-organized with clear numbered steps. | 3 / 3 |
Total | 11 / 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
- MetaMask/ocap-kernel
- Commit
a3eff0e
- 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.