CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pr-open-for-review

Mark the current branch's draft PR as ready for review

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/pr-open-for-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is an excellent example of a lean, simple command skill: fully executable gh commands, explicit stop conditions and checkpoints at each step, and a well-organized section structure with no padding or unnecessary references. The only minor improvement is trimming the small amount of purpose duplication between the title, intro, and Command Template heading.

DimensionReasoningScore

Conciseness

The body is lean with fully executable gh commands and no explanation of concepts Claude already knows. It stops short of anchor 5 only because the title, intro sentence, and "Command Template" heading all restate the same purpose, which is minor duplication that could be trimmed.

4 / 5

Actionability

Every step uses copy-paste-ready commands ("gh pr view --json ... --jq ...", "gh pr ready <number>") with exact stop-condition and report messages, and the common cases (no PR exists, already ready, success, reversal) are all covered. This fully matches the anchor for executable, example-covered guidance.

5 / 5

Workflow Clarity

The four steps are clearly sequenced with explicit checkpoints: step 1 validates a PR exists (with a stop-and-report path), step 2 checks isDraft and stops if already open, and step 4 defines the success report. This is a simple, single-purpose, non-destructive skill where the action is unambiguous, so the simple-skill exception applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines, requires no external references (none exist in the bundle), and is organized into clear sections (Find the PR, Check Draft State, Mark Ready, Report Result, Notes). Per the guidelines, a short, single-file skill with well-organized sections scores 5.

5 / 5

Total

19

/

20

Passed

Description

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

The description is concise and names one concrete, well-scoped action, but it omits any "when to use" trigger guidance and covers only a single action with limited natural keyword variation. Adding a "Use when..." clause and common synonyms (e.g., publish PR, un-draft) would raise completeness, trigger term quality, and distinctiveness.

Suggestions

Add a "Use when..." clause to the description, e.g., "Use when the user asks to publish, un-draft, or mark a PR as ready for review."

Include natural trigger synonyms such as "publish PR", "un-draft", and "open PR for review" so users' phrasing matches the description.

Consider mentioning the reversal capability (convert a ready PR back to draft) to make the action coverage more comprehensive.

DimensionReasoningScore

Specificity

"Mark the current branch's draft PR as ready for review" names one concrete action (marking a draft PR ready), matching the anchor for 1-2 concrete actions that are not comprehensive. It is above score 2 because the action is specific rather than generic, but below score 4 because only a single action is described.

3 / 5

Completeness

It clearly answers "what" (mark a draft PR ready for review) but contains no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. The "when" is only stated in the body, not in the description.

3 / 5

Trigger Term Quality

The description includes relevant keywords like "draft PR", "ready for review", and "current branch", but misses common natural variations users would say such as "publish", "un-draft", or "open PR". Coverage is partial, matching anchor 3 rather than the fuller coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

"draft PR" and "ready for review" describe a narrow niche that is mostly distinct from other skills, with only minor overlap risk against other PR-management skills. It falls short of anchor 5 because the description lacks explicit trigger phrases that would fully distinguish it.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

phatblat/dotfiles

Path

.agents/skills/pr-open-for-review/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.