pr

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

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

93%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 content is lean, actionable, and well-structured, with concrete commands and repair examples. The only gap is the absence of an explicit error-recovery feedback loop in the workflow.

Suggestions

Add a feedback-loop step to the Workflow (e.g., 'If conventional-prs fails, adjust scope/title and re-run until it passes') to reach a 5 on workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean and bullet-driven ("Use before `gh pr create`...", terse gates, before/after Repairs) with no padding or explanation of concepts Claude already knows, matching the 5 anchor 'every token earns its place'.	5 / 5
Actionability	Concrete executable commands (`conventional-prs --input '<title>'`, `gh search issues/prs`, `--body-file`) plus copy-paste-ready before/after examples in Repairs match the 5 anchor of fully executable guidance covering common cases.	5 / 5
Workflow Clarity	A clear 6-step numbered Workflow includes a validation checkpoint (running conventional-prs on the title), but lacks an explicit 'if validation fails, fix and retry' feedback loop, fitting the 4 anchor rather than 5.	4 / 5
Progressive Disclosure	The body is under 50 lines with no bundle files and is organized into well-signaled sections (Sources, Title gate, Body gate, Workflow, Repairs), matching the simple-skill exception allowing a 5.	5 / 5
	Total	19 / 20 Passed

Description

75%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 specific and highly distinct within its niche, but it lacks an explicit 'when to use' trigger clause, which caps its completeness.

Suggestions

Append an explicit 'Use when...' clause (e.g., before running gh pr create/edit or when drafting PR titles/bodies) to lift completeness beyond 3.

Add the synonym 'pull request' alongside 'PRs' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	"Create or update Cataclysm-BN PRs with validated titles, terse bodies, related links, and reviewer-useful evidence" lists multiple concrete deliverables (titles, bodies, links, evidence) with comprehensive coverage of its niche, matching the 5 anchor's 'multiple specific concrete actions'.	5 / 5
Completeness	The "what" is explicit, but there is no "Use when..." clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	"PRs", "titles", "bodies", "related links" are natural terms a user would say, but the synonym "pull request" is absent, fitting the 4 anchor of good coverage with a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	"Cataclysm-BN PRs" is a narrow, project-specific niche with distinct triggers and minimal overlap risk, matching the 5 anchor's 'clear niche with distinct triggers'.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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: cataclysmbn/Cataclysm-BN
Path: .agents/skills/pr/SKILL.md
Commit: b782646

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.