CtrlK
BlogDocsLog inGet started
Tessl Logo

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`).

83

1.69x
Quality

75%

Does it follow best practices?

Impact

95%

1.69x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/yeet/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A concise, highly actionable workflow with strong validation checkpoints for the risky git/PR operations. Weakest on progressive disclosure, since everything is inlined and the provided asset files are not referenced or navigated from the body.

Suggestions

Either reference the yeet.png/yeet-small.svg assets from the body or remove them, so the bundle structure is intentionally navigated rather than orphaned.

Clarify the 'Run checks' step with the specific command(s) to run and what 'fail due to missing deps/tools' should install, since the current bullet is vague for a destructive/batch flow.

Add an explicit final verification step (e.g. confirm the draft PR URL was created and title/body are set) to close the validation loop.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands and minimal padding, though a few lines like 'Confirm status, then stage everything' and the run-checks bullet could be tightened.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands for each step (gh --version, gh auth status, git add -A, git push -u, gh pr create --draft --fill) with specific flags and variables.

5 / 5

Workflow Clarity

A clear sequenced workflow with several explicit validation checkpoints (gh auth status, git status -sb, push-failure retry), but the 'Run checks' and PR-body steps are slightly underspecified and the destructive batch push-to-PR flow lacks an end-to-end validation step.

4 / 5

Progressive Disclosure

Content is organized into named sections (Prerequisites, Naming conventions, Workflow) and stays one level deep with no nested references, but all guidance is inlined into SKILL.md with no bundle references beyond unused assets, and the assets are never signaled from the body.

3 / 5

Total

16

/

20

Passed

Description

71%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.

A strong, specific description with clear what/when guidance and low conflict risk. Trigger term coverage is slightly narrow because it leans on technical phrasing rather than the full range of natural user synonyms.

Suggestions

Broaden trigger terms to include natural synonyms users say, such as 'open a PR', 'ship it', or 'create a pull request'.

Consider enumerating branch creation and checks as part of the action list so the scope is fully comprehensive.

DimensionReasoningScore

Specificity

Lists several concrete actions ('stage, commit, push, and open a GitHub pull request') tied to the GitHub CLI, with minor gaps in coverage (e.g. branch creation, checks, draft handling are implied but not enumerated).

4 / 5

Completeness

Explicitly answers both what ('stage, commit, push, and open a GitHub pull request') and when ('Use only when the user explicitly asks ... in one flow'), with the 'when' clause being concrete and specific.

4 / 5

Trigger Term Quality

Uses 'stage, commit, push, and ... pull request' which are natural terms, but relies on the exact phrase 'in one flow' and the jargon 'GitHub CLI (`gh`)' while missing common synonyms a user might say like 'ship', 'PR', or 'open a PR'.

3 / 5

Distinctiveness Conflict Risk

The bundled-one-flow GitHub CLI PR trigger is a clear niche with minimal overlap risk, and the 'Use only when ... in one flow' qualifier sharply distinguishes it from generic git/PR skills.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
foryourhealth111-pixel/Vibe-Skills
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.