CtrlK
BlogDocsLog inGet started
Tessl Logo

open-draft-pr

Prepare local changes for review with an intentional commit, push, and ready PR for fallow. Use when the user wants to publish work, open a PR, or turn local changes into a reviewable branch.

71

Quality

86%

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

86%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 body is a tight, well-structured instruction skill with a clear sequenced workflow and concrete examples. Adding an explicit validation feedback loop and one or two literal commands would round out actionability and workflow clarity.

Suggestions

Add an explicit validate-fix-retry loop, e.g. 'If validation fails, fix the issue and re-run before committing.'

Include one concrete command example for the key step, such as `gh pr create --title "..." --body "..."` without --draft, to lift actionability.

Spell out the post-push verification (confirm the PR opened in 'ready' state) as a final checkpoint.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding; the compatibility note earns its place by delivering a real behavioral instruction, and it assumes Claude's competence throughout.

5 / 5

Actionability

Concrete branch-name examples and explicit edge-case handling (empty coordination commit) give mostly executable guidance, though no literal git/gh commands are shown.

4 / 5

Workflow Clarity

A clear six-step sequence includes a validation checkpoint (step 2) and an honest-validation requirement, but lacks an explicit validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

A single-purpose skill under 50 lines with no external references and well-organized Workflow/Requirements sections meets the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

87%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 well-constructed: third-person voice, concrete actions, and an explicit 'Use when' trigger clause answering both what and when. Minor synonym coverage in trigger terms is the only weakness.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('intentional commit, push, and ready PR'), matching the anchor for several specific actions with minor coverage gaps.

4 / 5

Completeness

Explicitly states both what it does (prepare changes with commit/push/ready PR) and when to use it via concrete 'Use when...' trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases like 'publish work', 'open a PR', and 'reviewable branch' map to what users would say, though a few synonyms (e.g. 'submit pull request') are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (opening review PRs) with distinct triggers and minimal overlap risk with unrelated skills.

5 / 5

Total

18

/

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
fallow-rs/fallow
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.