CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-great-prs

PR descriptions that carry their own evidence, meaning short prose plus an embedded visual. Use when writing a PR body, adding a screenshot to a PR, or showing an invisible change (API, schema, migration, config).

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

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

90%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 tight, executable skill body that leads with concrete commands and pragmatic gotchas while preserving brevity. Its main limitation is that some validation and retry detail is handed off to sibling skills rather than spelled out, which slightly limits workflow clarity and self-contained navigation.

Suggestions

Add an explicit fix-and-retry loop for the verification steps (e.g., 'if the grep finds leftover placeholders, replace them and re-run before publishing') rather than delegating retry behavior to sibling skills.

State the check that the image reference was rewritten by gh --attach inline as a one-line verification, so the outward-facing publish step has a self-contained validation checkpoint.

Clarify upfront which steps require the sibling skills vs. which run standalone, so the reader can gauge self-sufficiency without reading to the Requirements section.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence ("A PR description is evidence", "Lean on the visual, not the prose"), with every explanatory line earning its place by conveying non-obvious concrete detail such as the 900px render width and the about:blank failure mode.

5 / 5

Actionability

It provides copy-paste-ready, executable commands covering the common cases (gh-attach shot, gh pr comment --attach, the placeholder grep, the bun add install lines), fully matching the 5 anchor.

5 / 5

Workflow Clarity

The sequence (point the camera → capture → attach and write → prose → requirements) is clear with real verification steps ("Look at every image before you upload it", grep for leftover placeholders, stop if a dependency is missing), but the fix-and-retry feedback loop is delegated to sibling skills rather than stated inline, leaving it just below a 5.

4 / 5

Progressive Disclosure

Content is well-organized into signaled sections and delegates detail one level deep to sibling skills ("Call the Skill tool with gh-attach", "That skill owns the rest") with no nested indirection; with no bundle files present and references being to external skills rather than bundled material, it sits at a strong 4 rather than a 5.

4 / 5

Total

18

/

20

Passed

Description

83%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 strong, third-person description that states both the capability and concrete usage triggers without padding. It is comprehensive on completeness and solid on specificity, triggers, and distinctiveness, with only marginal room for tighter keyword/coverage breadth.

DimensionReasoningScore

Specificity

The description names the domain and several concrete actions ("short prose plus an embedded visual", "writing a PR body", "adding a screenshot", "showing an invisible change"), with only minor coverage gaps relative to the comprehensive 5 anchor.

4 / 5

Completeness

It explicitly answers both what ("PR descriptions that carry their own evidence, meaning short prose plus an embedded visual") and when ("Use when writing a PR body, adding a screenshot to a PR, or showing an invisible change") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases a user would say appear ("PR body", "screenshot to a PR", "API, schema, migration, config"), giving good keyword coverage; it stops short of the comprehensive synonym/.extension breadth of a 5.

4 / 5

Distinctiveness Conflict Risk

The PR-description niche is clearly distinct with specific triggers, though the "invisible change (API, schema, migration, config)" clause is broad enough to create minor overlap with API/migration skills, keeping it just below a 5.

4 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
aabuhijleh/abed-hub
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.