yeet

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

1.69x

Quality

92%

Does it follow best practices?

Impact

95%

1.69x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

85%

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

A tight, well-sequenced, mostly executable workflow with good validation checkpoints and clean section organization. Its one weak spot is the PR-body step, which sketches a temp-file approach but omits the command that actually applies the body to the PR.

Suggestions

Specify the command that attaches the PR body temp file to the PR (e.g. `gh pr edit --body-file pr-body.md`), since `--fill` populates from commit messages and won't use the custom body, and the current "run pr-body.md" is ambiguous.

Replace the "pr-body.md ... EOF" sketch with a concrete copy-paste-ready heredoc example so the body-writing step is fully executable.

Dimension	Reasoning	Score
Conciseness	The body is lean and terse — short bullet points with concrete commands and no explanation of git/gh concepts Claude already knows, so every token earns its place.	3 / 3
Actionability	Most steps are concrete executable commands, but the PR-body step ("e.g. pr-body.md ... EOF" and "run pr-body.md") is incomplete: it never specifies the command that attaches the temp file to the PR, and `--fill` will not consume a custom body, leaving a missing key detail.	2 / 3
Workflow Clarity	The multi-step flow is clearly sequenced with a pre-stage checkpoint ("Confirm status, then stage everything") and explicit feedback loops (check-fail→install→rerun once; push-fail→pull→retry), matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	This is a simple, single-purpose skill under 50 lines with well-organized sections (Prerequisites, Naming conventions, Workflow); the unreferenced assets are decorative icons, not nested references, so the simple-skills note applies.	3 / 3
	Total	11 / 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.

A strong, concise description with an explicit trigger clause, four concrete actions, and a distinctive one-flow niche. It clearly answers both what the skill does and when to use it without padding or over-claims.

Dimension	Reasoning	Score
Specificity	The description lists four concrete actions — "stage, commit, push, and open a GitHub pull request" — plus the explicit tool ("GitHub CLI (`gh`)"), matching the anchor for multiple specific concrete actions rather than the partial anchor below.	3 / 3
Completeness	It answers both what (stage/commit/push/open a PR in one flow via gh) and when via the explicit trigger "Use only when the user explicitly asks to...", matching the both-what-and-when anchor.	3 / 3
Trigger Term Quality	It uses natural terms a user would actually say ("stage, commit, push, pull request, GitHub CLI, gh"), giving good coverage of common phrasings rather than jargon-only or generic terms.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow — requiring an explicit user request plus the all-four-steps-in-one-flow combo via gh — so it is clearly distinguishable and unlikely to trigger for the wrong skill.	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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/yeet/SKILL.md
Commit: f627ab5

Reviewed: about 11 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.