CtrlK
BlogDocsLog inGet started
Tessl Logo

pr

Create or update Cataclysm-BN PRs with validated titles, terse bodies, related links, and reviewer-useful evidence.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

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.

The body is a tight, actionable PR-creation playbook: executable validation gates, a clear numbered workflow with error-recovery examples, and clean sectioning appropriate for a small single-purpose skill.

DimensionReasoningScore

Conciseness

The body is lean throughout: terse bullets in Title gate/Body gate, a numbered Workflow, and concrete before/after Repairs, with no explanation of concepts Claude already knows and every line earning its place.

3 / 3

Actionability

It gives executable commands ("conventional-prs --input '<title>'", "gh search issues", "gh search prs", "--body-file"), concrete required-scope mappings, and copy-paste-ready before/after repair examples.

3 / 3

Workflow Clarity

The six-step Workflow is clearly sequenced with an explicit validation checkpoint (run conventional-prs to gate the title), and the Repairs section supplies concrete error-recovery patterns for failed gates.

3 / 3

Progressive Disclosure

A single-purpose skill under 50 lines with no bundle files, organized into clearly signaled sections (Sources, Title gate, Body gate, Workflow, Repairs); the listed source files are one-level project references, not nested bundle hops.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific, third-person, and clearly niched to Cataclysm-BN PR work, but it omits an explicit 'Use when...' trigger and only covers one form of the core term, leaving completeness and trigger-term quality mid-band.

Suggestions

Append an explicit trigger clause, e.g. "Use when creating or updating Cataclysm-BN pull requests, PR titles, or PR bodies before running gh pr create/edit."

Add the full form "pull request" alongside "PRs" so the description matches both how users phrase the request and the gh subcommands.

DimensionReasoningScore

Specificity

"Create or update ... PRs with validated titles, terse bodies, related links, and reviewer-useful evidence" names multiple concrete actions (create/update, validate titles, terse bodies, link related work, attach evidence), matching the multiple-specific-actions anchor.

3 / 3

Completeness

The WHAT is explicit (create/update PRs with validated titles, terse bodies, etc.), but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Core natural term "PRs" appears alongside "titles", "bodies", "links", but common variations like "pull request" or "gh pr" are absent, fitting the some-relevant-keywords-but-missing-variations anchor rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

Scoping to "Cataclysm-BN PRs" with conventional-prs validation carves a clear, project-specific niche unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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
cataclysmbn/Cataclysm-BN
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.