push

Pushes the current branch to the remote repository.

1.22x

Quality

66%

Does it follow best practices?

Impact

93%

1.22x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/push/SKILL.md

Quality

Content

80%Weight 40%Scale 1-5

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

The body is admirably lean and gives concrete, executable git commands organized into a clear numbered workflow. Its main weakness is the absence of any validation or feedback loop for the remote push itself, which the rubric caps at workflow clarity 3 for outward-facing operations.

Suggestions

Add a validation step after the push, e.g. check `git push` exit status and surface rejection/non-fast-forward errors to the user before retrying with `--force-with-lease` if appropriate.

Show how to obtain the current branch name (e.g. `git branch --show-current`) so the no-upstream command is copy-paste ready rather than relying on a placeholder.

Clarify the pre-check by noting what to do if `git status` shows uncommitted changes or nothing to push.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's git competence ('Run `git status`', 'Run `git push`', 'git push -u origin <branch-name>') with no padding or explanation of concepts Claude already knows, matching the score-5 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	It provides concrete, executable commands covering both the normal and no-upstream cases, but uses a placeholder branch name and gives no example of how to determine the branch, fitting the score-4 'mostly executable guidance with minor gaps' anchor rather than fully copy-paste-ready at 5.	4 / 5
Workflow Clarity	The status -> push -> report sequence is clear and includes a pre-check ('verify there are commits to push'), but pushing to a remote is an outward-facing operation with no validation that the push succeeded or feedback loop for rejection/conflict/auth failure, so per the destructive-operation cap workflow clarity is held at 3.	3 / 5
Progressive Disclosure	This is a simple, single-purpose skill under 50 lines with no need for external references, and its numbered steps are well-organized, so per the simple-skills scoring note progressive disclosure scores 5 on well-organized sections alone.	5 / 5
	Total	17 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 uses correct third-person voice to state a clear, distinct capability, but it lacks any 'when to use' trigger guidance and offers only a single action with limited keyword variations. Adding a 'Use when...' clause and a synonym or two would lift the completeness and trigger_term_quality dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to push commits, upload a branch, or sync local changes to the remote.'

Include a synonym or natural variation beyond 'push' (e.g. 'sync' or 'upload') to broaden trigger-term coverage.

Optionally note the no-upstream case in the description to add a second concrete action and improve specificity.

Dimension	Reasoning	Score
Specificity	The phrase 'Pushes the current branch to the remote repository' names the domain and one concrete action clearly, but offers only a single action with no breadth, matching the score-3 anchor of naming the domain plus 1-2 concrete actions without being comprehensive.	3 / 5
Completeness	It clearly states what the skill does ('Pushes the current branch to the remote repository') but provides no 'Use when...' trigger guidance, so per the judging guidelines completeness is capped at 3 for a clear 'what' with missing 'when'.	3 / 5
Trigger Term Quality	'push', 'branch', and 'remote repository' include the single natural keyword a user would say, but the description omits common variations/synonyms (upload, sync, publish), fitting the score-3 anchor of some relevant keywords missing common variations rather than the fuller coverage at 4.	3 / 5
Distinctiveness Conflict Risk	'Pushes the current branch to the remote repository' targets a distinct git niche with minimal conflict risk, but could slightly overlap with a broader git or deploy skill, placing it at the score-4 'mostly distinct, minor overlap' anchor rather than the fully-distinct 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: MetaMask/ocap-kernel
Path: .claude/skills/push/SKILL.md
Commit: 37db357

Reviewed: about 20 hours ago

Table of Contents

Discovery Implementation Validation

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.