push

Push current branch changes to origin and create or update the corresponding pull request; use when asked to push, publish updates, or create pull request.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

This is a well-structured, actionable skill with clear workflow sequencing and proper validation checkpoints. Its main weakness is moderate redundancy between the Steps narrative and the Commands block, which inflates token usage without adding new information. The error handling distinctions (sync vs auth problems) and PR lifecycle management (create/update/new branch for closed PRs) are particularly well done.

Suggestions

Consolidate the Steps and Commands sections into a single annotated command workflow to eliminate redundancy and improve conciseness.

Remove the Notes section and integrate its constraints directly into the relevant step where they apply, since they repeat information already in Steps.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient and avoids explaining concepts Claude already knows, but there's some redundancy between the Steps section and the Commands section (essentially restating the same workflow twice). The notes section also partially repeats constraints already stated in the steps.	2 / 3
Actionability	The skill provides concrete, executable shell commands for every step, including branch identification, pushing, PR creation/editing, body validation, and URL retrieval. The commands are copy-paste ready with clear conditional logic for different scenarios.	3 / 3
Workflow Clarity	The multi-step process is clearly sequenced with explicit validation checkpoints (make -C elixir all before push, mix pr_body.check for PR body), error recovery paths (pull skill for non-fast-forward, stop for auth errors), and feedback loops (fix and re-validate). The handling of closed/merged PRs and force-push scenarios is well-specified.	3 / 3
Progressive Disclosure	The skill references the `pull` skill appropriately and mentions `.github/pull_request_template.md`, but the content is somewhat monolithic with the Steps and Commands sections covering overlapping ground inline. No bundle files are provided, so there's no external structure to leverage, but the skill could benefit from separating the detailed command reference.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 is a well-crafted skill description that concisely covers what the skill does and when to use it. It uses third person voice, includes natural trigger terms, and clearly defines a distinct scope around pushing changes and managing pull requests. The description is concise without being vague.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'push current branch changes to origin', 'create or update the corresponding pull request'. These are clear, actionable operations.	3 / 3
Completeness	Clearly answers both what ('Push current branch changes to origin and create or update the corresponding pull request') and when ('use when asked to push, publish updates, or create pull request') with explicit triggers.	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'push', 'publish updates', 'create pull request'. These are terms developers naturally use when they want this functionality.	3 / 3
Distinctiveness Conflict Risk	Has a clear niche focused on pushing and PR creation/updating. The combination of git push + pull request management is distinct and unlikely to conflict with other skills like general git operations or code review skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/symphony
Commit: 4cbe3a9

Reviewed: 2 days 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.