CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-mr

Creates and updates pull requests and merge requests for cloudflare-docs changes. Covers title conventions, branch naming, request body structure, and documentation checklist templates. Load when asked to open, create, submit, update, or edit a PR or MR, or write a PR or MR title or description.

73

Quality

89%

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

88%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 well-crafted, actionable PR/MR workflow with explicit validation checkpoints, concrete git commands, and real examples that assume Claude's competence. The main improvement space is progressive disclosure — the long title-example and checklist material could be moved into reference files to slim the main body.

Suggestions

Move the large block of title examples (Step 2 'Title examples') into a references file (e.g. references/title-examples.md) and link to it, keeping only a few representative examples inline in SKILL.md.

Extract the full documentation-checklist guidance (Step 3 'Documentation checklist' and 'What not to do') into a references file and summarize the decision rules inline, reducing body length and improving progressive disclosure.

Tighten the few explanatory sentences (e.g., the 'production' vs 'main' rationale) to one line each to push conciseness toward the lean anchor 5.

DimensionReasoningScore

Conciseness

Dense and actionable with no padding of concepts Claude already knows; minor explanatory prose (e.g., why 'production' not 'main') is justified repo-specific knowledge but could be trimmed slightly, keeping it below the lean anchor 5.

4 / 5

Actionability

Provides concrete executable git commands ('git diff <base>...HEAD --stat', 'git log --oneline <base>..HEAD'), concrete title-format blocks, and real summary examples with tables; the provider-tool step is intentionally abstract for provider-agnosticism, which the rubric exempts for actionable instruction skills.

5 / 5

Workflow Clarity

Clear Steps 1–4 sequence with explicit validation checkpoints — ask about uncommitted files, check for an existing open request before duplicating, ask before pushing, and a post-push title/body accuracy check — plus a documentation checklist, matching the anchor 5 with feedback loops.

5 / 5

Progressive Disclosure

A single well-organized file with clear section headers and easy navigation, but at ~200 lines with no reference splitting the extensive title-example block and full checklist guidance are inlined rather than externalized, so it does not reach the well-signaled one-level-deep reference structure of anchor 5.

4 / 5

Total

18

/

20

Passed

Description

91%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, well-structured description that clearly states both capabilities and explicit load triggers with good synonym coverage. It is scoped to a distinct niche but the PR/MR trigger verbs still carry minor overlap with generic PR skills.

DimensionReasoningScore

Specificity

Names the domain and several specific capabilities ('Creates and updates pull requests and merge requests', 'Covers title conventions, branch naming, request body structure, and documentation checklist templates'), but only two action verbs appear with the rest as covered topics, leaving minor gaps versus the comprehensive multi-verb anchor 5.

4 / 5

Completeness

Explicitly answers both what ('Creates and updates... Covers title conventions, branch naming, request body structure, and documentation checklist templates') and when ('Load when asked to open, create, submit, update, or edit a PR or MR...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms with synonyms — 'open, create, submit, update, or edit a PR or MR, or write a PR or MR title or description' — matching the terms a user would naturally say.

5 / 5

Distinctiveness Conflict Risk

Scoped to cloudflare-docs with specific conventions gives a clear niche, but PR/MR creation triggers ('open, create, update, or edit a PR or MR') overlap with general PR/merge-request skills, leaving minor conflict risk.

4 / 5

Total

18

/

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
cloudflare/cloudflare-docs
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.