CtrlK
BlogDocsLog inGet started
Tessl Logo

yeet

Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

A well-structured, executable, and concise workflow skill with clear sequencing, explicit validation/feedback checkpoints, and clean section organization throughout.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains git/PR concepts Claude already knows and uses terse bullets and concrete commands, so every token earns its place. There is minor overlap between the Overview hybrid bullets and step 7, but not enough to drop it to the 'mostly efficient but could be tightened' level.

3 / 3

Actionability

Fully executable, copy-paste-ready commands are given throughout — `git status -sb`, `git push -u origin $(git branch --show-current)`, `gh auth status`, `gh pr create --draft --fill --head $(git branch --show-current)` — matching the 'fully executable code/commands' anchor.

3 / 3

Workflow Clarity

An explicit 8-step sequence with validation checkpoints (auth check, pre-stage diff inspection, run checks) and a retry feedback loop (step 5: checks fail → install deps → rerun once), plus the Write Safety guardrails for the destructive push/commit operations. It is not a 2 because validation and feedback loops are explicit rather than implicit.

3 / 3

Progressive Disclosure

The content is self-contained and organized into clear sections (Overview, Prerequisites, Naming conventions, Workflow, Write Safety, PR Body Expectations) with no need for external references; the only bundle files are two icon assets, not reference docs. Per the simple-skills scoring note, well-organized sections without external references warrant a 3.

3 / 3

Total

12

/

12

Passed

Description

82%Weight 40%Scale 1-3

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 specific, well-triggered description with strong concrete actions and a distinct niche, weakened only by the absence of an explicit 'Use when...' trigger clause that caps completeness at 2.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user asks to publish, commit and push, or open a PR for local changes.'

Include common trigger variations such as 'pull request' alongside 'PR' to broaden natural keyword coverage.

Consider trimming the internal jargon ('connector coverage is insufficient', 'GitHub app from this plugin') which is implementation detail rather than user-facing trigger language.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "confirming scope, committing intentionally, pushing the branch, and opening a draft PR" — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It clearly answers 'what' (confirm scope, commit, push, open draft PR) but contains no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric guidelines cap at 2. It is not a 1 because the 'what' is explicit and concrete, and not a 3 because 'when' is entirely absent rather than stated.

2 / 3

Trigger Term Quality

Natural user-facing terms are well covered: "Publish local changes to GitHub", "committing", "pushing the branch", and "draft PR" are all phrases a user would actually say. The internal jargon ("connector coverage", "GitHub app from this plugin") is secondary and does not displace the natural trigger terms, so this is not the level below.

3 / 3

Distinctiveness Conflict Risk

The full publish-to-GitHub flow with a hybrid gh/connector draft-PR approach is a clear niche with distinct triggers, unlikely to fire for unrelated skills. It is not a 2 because the scope is narrow and specific rather than broadly overlapping.

3 / 3

Total

11

/

12

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
openai/plugins
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.