CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pr

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

Quality

82%

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

86%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 an exemplary terse, instruction-only skill: concrete validation commands, specific scope mappings, before/after repair examples, and a numbered workflow with a title-validation checkpoint. Its only soft spots are the absence of a full gh pr create/edit example invocation and no explicit post-edit validation loop.

DimensionReasoningScore

Conciseness

Lines like "Use the smallest valid scope; do not invent scopes" and "Keep the body terse. Include only reviewer-useful context" are lean, assume Claude's competence, and contain no concept explanations or padding — every token earns its place.

5 / 5

Actionability

Concrete commands appear throughout ("conventional-prs --input '<title>'", "gh search issues / gh search prs", "--body-file", "do not rely on unchecked --fill") plus copy-paste repair examples like "fix: UI bug" → "fix(UI): prevent item repair menu from hiding refittable items"; the minor gap is that no full gh pr create/edit invocation is shown, keeping it below fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

The 6-step Workflow has a clear sequence with an explicit title-validation checkpoint (step 4) and a Repairs section covering error recovery, but there is no explicit re-validation loop after body edits or validation of the final PR state, matching 'clear sequence with most checkpoints; minor validation gaps'.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no external bundle references needed (no references/, scripts/, or assets/ exist), and its sections (Sources, Title gate, Body gate, Workflow, Repairs) are well-organized — meeting the simple-skill exception for a top progressive-disclosure score.

5 / 5

Total

18

/

20

Passed

Description

70%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 clearly niche-scoped to Cataclysm-BN PR creation, with concrete artifacts (titles, bodies, links, evidence) named. Its main weakness is the absence of any 'Use when...' trigger clause, which caps completeness and leaves natural trigger phrases like 'pull request' or 'gh pr' unused.

Suggestions

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

Include the spelled-out synonyms "pull request" and "gh pr" alongside "PRs" so users phrasing the need either way match the skill.

Mention the linking/searching behavior ("find and link related issues/PRs") as a capability so users asking for related-issue lookup trigger it too.

DimensionReasoningScore

Specificity

"Create or update Cataclysm-BN PRs with validated titles, terse bodies, related links, and reviewer-useful evidence" lists several concrete actions (create/update, title validation, terse bodies, related links, evidence), matching the 'several specific actions with minor gaps' anchor rather than the comprehensive multi-action anchor 5.

4 / 5

Completeness

The 'what' is clear (create or update PRs with validated titles, terse bodies, links, evidence) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms like "PRs", "titles", "bodies", "links", and "evidence" are present, but common variations users would say — "pull request", "gh pr create", "PR body/title edit" — are missing, fitting 'good keyword coverage; a few natural terms missing' rather than comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

"Cataclysm-BN PRs" is a clearly scoped niche with distinct triggers (specific project, PR titles/bodies), giving minimal conflict risk with other skills — matching the anchor-5 example's clear-niche pattern.

5 / 5

Total

16

/

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

cataclysmbn/Cataclysm-BN

Path

.agents/skills/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.