CtrlK
BlogDocsLog inGet started
Tessl Logo

push-to-pr

Push commits to an existing GitHub PR's source branch. NEVER create new branches. Use when the user says "push to PR

80

Quality

100%

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%

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

The body is token-efficient and highly actionable, with a clear sequenced workflow, validation checkpoints, an error-recovery loop, and a checklist of critical rules. As a compact single-purpose skill it needs no external references and is well organized.

DimensionReasoningScore

Conciseness

Lean body with a one-line intro, four workflow steps of executable commands, and terse critical rules; no padding or explanation of concepts Claude already knows.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands — the curl+python3 one-liner to resolve the head branch, plus git remote/fetch/rebase/push invocations with concrete syntax.

3 / 3

Workflow Clarity

Clear four-step sequence with explicit validation (maintainer_can_modify must be true) and a feedback loop (non-fast-forward rejection → fetch and rebase), backed by a critical-rules checklist.

3 / 3

Progressive Disclosure

A simple, single-purpose skill under 50 lines with no external references; content is cleanly split into a numbered workflow and a Critical Rules section, which is well-organized per the simple-skills note.

3 / 3

Total

12

/

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.

The description is specific, trigger-rich, and complete, naming concrete actions and giving explicit natural-language triggers including variations. It uses third-person voice and clearly distinguishes the skill's niche with a hard negative constraint.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "finding the PR's head branch via GitHub API", "setting up the correct remote", and "pushing with HEAD:<branch> syntax" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (push commits to an existing PR's source branch with the listed sub-actions) and when ("Use when the user says...").

3 / 3

Trigger Term Quality

Covers natural phrases a user would actually say, including "push to PR #N", "push到PR", and "any variation meaning to push local commits onto an existing pull request".

3 / 3

Distinctiveness Conflict Risk

Clear niche of pushing to existing PRs, sharply bounded by "NEVER create new branches", making overlap with other skills unlikely.

3 / 3

Total

12

/

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
Project-N-E-K-O/N.E.K.O
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.