CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

branch-pr

Trigger: creating, opening, or preparing PRs. Follow the destination repository's contribution policy.

Quality

74%

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 ./internal/assets/skills/branch-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 lean, well-structured governance skill: concrete rules, a sequenced workflow with evidence-based checkpoints, and proper delegation of detail to a single clearly-labeled reference. Its main weakness is undefined project-specific jargon ("native RDD consent", "chain strategy/exception", "Gentle AI" references) that a portable skill should define or drop.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no basic-concept padding — and every section carries rules ("never substitute Gentle AI's rules", "Never stash/pop for this purpose"). Minor repetition keeps it from a 5: label-mutation authority is stated three times ("Never invent a label...", "never infer mutation authority from a discovered label", "Apply labels only through the canonical workflow...") and authorization rules recur across Hard Rules and Execution Steps. Not 3 because nothing explains concepts Claude already knows and the ~40 lines could not be cut substantially without losing rules.

4 / 5

Actionability

Most guidance is concrete and executable: "Read the destination's `CONTRIBUTING.md`, agent instructions, PR template", "Closes/Fixes/Resolves #N" vs "Refs #N", "`viewerPermission` `MAINTAIN` or `ADMIN`", and explicit prohibitions like "Never stash/pop". Not 5 because several terms are never defined — "native RDD consent", "chain strategy/exception", "Gentle AI's Go/Docker examples" — leaving those instructions non-executable without external context. Not 3 because the bulk of the guidance names exact files, permission levels, and actions.

4 / 5

Workflow Clarity

Execution Steps 1–5 give a clear sequence with explicit checkpoints: "run the project's applicable checks", baseline verification ("the same failing command/environment on a comparable isolated clean base"), "Mark checkboxes only after observed evidence", and "one bounded attempt and target-host readback". Not 5 because there is no fix-and-retry feedback loop — failures are reported ("Report failures honestly") rather than iterated — and the Decision Gates table conditions are not all resolvable procedurally. Not 3 because validation checkpoints are explicit at nearly every step.

4 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections (Activation Contract, Hard Rules, a Decision Gates table, Execution Steps, Output Contract) and a single clearly-signaled, one-level-deep reference: "`../issue-creation/SKILL.md` — canonical action authority", which appropriately delegates the detailed label-mutation workflow. No bundle files exist to inline, and nothing that belongs in a separate file is inlined. Not 4 because there are no organization gaps — the split between overview and delegated detail is exactly right for a lean skill.

5 / 5

Total

17

/

20

Passed

Description

57%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 has an explicit trigger clause and a clear, distinct niche, but it undersells the skill's actual capabilities and uses imperative voice instead of third person. Trigger coverage relies on a single abbreviation ("PRs") without the spelled-out "pull request" or related branch/submit terms.

Suggestions

Rewrite in third person and enumerate the distinct capabilities, e.g.: "Prepares branches and pull requests under the destination repository's contribution policy — reads CONTRIBUTING.md and PR templates, classifies types and labels, drafts PR descriptions, and runs required checks."

Add natural trigger synonyms and phrasing: "Use when creating, opening, or submitting pull requests (PRs), preparing branches for PRs, or when asked to open a PR against a fork or upstream repository."

Spell out 'pull request' at least once alongside 'PRs' so the description matches users who type the full term.

DimensionReasoningScore

Specificity

The description names the domain and actions ("creating, opening, or preparing PRs"), but the three verbs are near-synonyms for one operation, matching the anchor 'names domain and 1-2 concrete actions, but not comprehensive' (base 3). The second sentence "Follow the destination repository's contribution policy" is imperative (implied second person) rather than third person, so the 1-point voice penalty applies, giving 2. Not 1 because the domain and actions are concretely named.

2 / 5

Completeness

"Trigger: creating, opening, or preparing PRs" is an explicit when-clause (so the missing-'Use when' cap does not apply), and "Follow the destination repository's contribution policy" states the what. Both are present but the when lacks user-scenario phrasing and the what is thin about what the skill actually does — matching 'has both what and when; when could be more explicit or specific'. Not 5 because neither half is concrete or comprehensive; not 3 because explicit trigger guidance exists.

4 / 5

Trigger Term Quality

"PRs" is a natural term users say, and "creating, opening" match real user phrasing, but the spelled-out synonym "pull request" plus related terms like "branch" or "submit" are absent — fitting 'some relevant keywords but missing common variations or synonyms'. Not 4 because key synonym coverage is missing; not 2 because the core term and natural verbs are present.

3 / 5

Distinctiveness Conflict Risk

The niche is clear — PR preparation governed by the destination repo's rules ("destination repository's contribution policy", "PRs") — with only minor overlap risk against closely related commit-message or issue-management skills. Not 5 because "PRs"/"contribution policy" could still collide with generic git-workflow skills; not 3 because the policy-focused framing is distinctive.

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

Gentleman-Programming/gentle-ai

Path

internal/assets/skills/branch-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.