CtrlK
BlogDocsLog inGet started
Tessl Logo

pull-request

Draft and review durable GitHub pull request titles and bodies for Epicenter. Use when creating a PR, running gh pr create, drafting or editing a PR body, writing changelog entries, linking issues, choosing merge strategy, or reviewing PR text. For local commits and branches use the git skill; for issue replies use github-issues. Never include Testing, Test Plan, or Verification sections in PR bodies unless explicitly requested.

79

Quality

100%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-crafted instruction skill body: lean, concrete, and properly progressive-disclosed. The decision table and hard rules give actionable guidance while templates and patterns are correctly offloaded to clearly labeled references.

DimensionReasoningScore

Conciseness

The ~42-line body is lean and assumes Claude's competence — a decision table, concrete hard rules, and a signaled reference list — with no padding explaining what a PR is or how tooling works.

3 / 3

Actionability

Concrete, actionable guidance for an instruction skill: a change→shape decision table and exact directives ("Do not include `## Summary`…", "Add a `## Changelog` section only for `feat:` and `fix:` PRs with user-visible changes") rather than vague direction; code absence is not penalized per the instruction-skill note.

3 / 3

Workflow Clarity

Clear sequenced flow — match the change to a shape, open that shape's reference, then draft — with a default fallback ("default to the focused fix"); the Hard Rules list serves as the verification checklist, and no destructive/batch operation requires an explicit feedback loop.

3 / 3

Progressive Disclosure

A concise overview points to five well-signaled, one-level-deep references (body-patterns, visual-patterns, examples, changelog-entries, github-pr-operations), each described by purpose; all referenced files exist and content is appropriately split.

3 / 3

Total

12

/

12

Passed

Description

100%

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 concrete capabilities, lists natural trigger terms, includes an explicit 'Use when' clause, and actively routes overlapping tasks to other skills. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Draft and review durable GitHub pull request titles and bodies", "running gh pr create", "writing changelog entries", "linking issues", "choosing merge strategy" — rather than vague language, matching the comprehensive anchor.

3 / 3

Completeness

Explicitly answers both what ("Draft and review durable GitHub pull request titles and bodies") and when via an explicit "Use when…" clause, so it is not capped at 2 for a missing trigger.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — "creating a PR", "gh pr create", "drafting or editing a PR body", "writing changelog entries", "reviewing PR text" — with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Actively disambiguates from adjacent skills ("For local commits and branches use the git skill; for issue replies use github-issues") and scopes to Epicenter PRs, giving a clear niche unlikely to conflict.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository
EpicenterHQ/epicenter
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.