CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ce-commit-push-pr

Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.

Quality

90%

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

85%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 tightly written orchestrator skill: a lean body of operational rules, concrete commands and flags inline, a clearly sequenced 5-step workflow with explicit re-verification checkpoints around the risky external writes, and well-signaled one-level references that all exist in the bundle. The only room for improvement is trimming a few meta-explanatory sentences and slightly richer inline command coverage.

DimensionReasoningScore

Conciseness

The ~50-line body is dense operational rules with zero padding about concepts Claude already knows, but a few sentences could be trimmed — e.g. the meta-explanation "Presence in the current tool list is proof the tool exists" and re-stating rules from references ("Two of its rules belong here too"). This fits the efficient-with-minor-trims anchor at 4 rather than the every-token-earns-its-place anchor at 5.

4 / 5

Actionability

Gives concrete, executable guidance: "Pass the body via `--body-file <path>`, never stdin", "Never use `git add -A` or `git add .`", "target the base with `-R` and pass the branch name only", plus exact `gh pr edit` / `gh pr create` usage and match-head-owner-branch resolution. As an instruction-only skill this is highly actionable, but the full probe recipes are delegated to references, leaving minor gaps that keep it below the copy-paste-complete anchor at 5.

4 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with mode dispatch, and validation checkpoints are explicit for the external-write operations: "Re-verify branch, remote, and PR state right before each consequential action", "Before `gh pr create`, re-check PR presence... non-zero blocks", the pre-publish gate ("otherwise stop before the external write"), and unknown-state blocking ("stop until presence is known"). This matches the anchor with explicit validation and error-recovery handling.

5 / 5

Progressive Disclosure

The body is a lean overview that signals each reference load with when and why ("Read `references/context.md` before Step 1. It defines...", "load `references/stack-submit.md` before Step 3"), and all cited paths exist in the bundle; the two uncited files (visual-evidence.md, gh-stack-cli.md) are reachable via lateral cross-links from cited references, so nothing nests beyond one level from SKILL.md. This matches the clear-overview, well-signaled one-level-deep anchor.

5 / 5

Total

18

/

20

Passed

Description

92%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 concise, third-person description that states concrete capabilities and an explicit 'Use when' clause with natural trigger phrases for both the full ship-a-PR flow and description-only flows. The only weakness is modest synonym coverage (no "pull request" or "create a PR" variants).

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Commit, push, and open a PR" plus "writing, rewriting, or describing a PR body" — covering the full workflow and its description-only variants. It matches the comprehensive-coverage anchor rather than the score-4 anchor, which expects minor gaps in coverage.

5 / 5

Completeness

Explicitly answers both: what ("Commit, push, and open a PR") and when ("Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body") with concrete trigger phrases. Clearly matches the top anchor, not the score-4 anchor where the 'when' is only loosely specified.

5 / 5

Trigger Term Quality

Natural phrases like "ship/open a PR" and "writing, rewriting, or describing a PR body" are exactly what users would say. Not 5 because common variations such as "pull request" spelled out, "create a PR", or "draft a PR description" are missing; not 3 because the present terms are natural rather than jargon-only.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (git commit/push/PR shipping plus PR-description flows) with distinct triggers like "open a PR" and "write a PR description". Overlap risk with adjacent skills (e.g., commit-message generation) is minimal, fitting the clear-niche anchor rather than the minor-overlap anchor at 4.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

EveryInc/compound-engineering-plugin

Path

skills/ce-commit-push-pr/SKILL.md

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.