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 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 broader context of when this skill should be chosen over other git-related skills.
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 origin.'
Include common natural language variations users might say, such as 'git push', 'push to origin', 'push commits', 'upload changes', or 'sync with GitHub/GitLab'.
Expand the 'what' portion to cover edge cases or related capabilities, 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 keywords 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 triggers reduces distinctiveness. | 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 logically sequenced. The main weakness is the lack of error handling guidance for common push failures (rejected pushes, authentication issues), which would improve robustness.
Suggestions
Add error handling for common push failures, e.g., 'If push is rejected, run `git pull --rebase` then retry' to create a feedback loop.
Consider adding guidance for force-push scenarios and when they are/aren't appropriate, as this is a common edge case.
| 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 for each step. The conditional for upstream branch handling is specific and actionable. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced, but there's no error handling or validation. Missing guidance for push failures (e.g., rejected push due to remote changes, authentication errors) and no feedback loop for error recovery. | 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
052f4d4
- 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.