CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

servicing-pr

Create EF Core PRs targeting servicing release branches (release/*). Use when working on a PR that targets a release branch, backporting a fix from main, or when the user mentions servicing, patch, or release branch.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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.

A dense, well-organized skill that captures genuinely non-obvious project conventions (servicing PR template, quirk switch pattern) with almost no waste. The only gaps are the underspecified branch-discovery/verification steps and the absence of an explicit feedback loop around the final validation.

Suggestions

Add a concrete command for finding and verifying the target branch, e.g., `git ls-remote --heads upstream 'release/*'` under 'Backport Target Branch'.

Turn the Validation section into a feedback loop: state that if any check fails, the PR description or quirk is corrected and the checklist re-run before opening the PR.

DimensionReasoningScore

Conciseness

Lean throughout: branch-selection rules, the title format, the complete PR description template, and the quirk code block are all project-specific knowledge Claude would not otherwise have. No padding and no explanation of concepts Claude already knows, matching the anchor-5 'every token earns its place' example.

5 / 5

Actionability

The title format, full description template, and quirk snippet are copy-paste ready. However, 'find the latest release/XX.0 branch' and 'Verify the branch exists' provide no concrete command (e.g., a git ls-remote invocation), leaving minor gaps that keep it below anchor 5.

4 / 5

Workflow Clarity

The sequence (determine target branch, verify it, apply title/description format, add quirk) is logical and there is a final Validation checklist. But steps are distributed across sections rather than an explicit workflow, and there is no feedback loop ('if validation fails, fix and re-check'), so it sits between anchors 4 and 5.

4 / 5

Progressive Disclosure

The body is under 50 lines with no external references needed, and is organized into clearly headed sections (Backport Target Branch, PR Title, PR Description Template, Quirk, Validation). Per the simple-skill guideline this scores 5 with well-organized sections alone.

5 / 5

Total

18

/

20

Passed

Description

90%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 description with an explicit 'Use when...' clause covering concrete, natural trigger phrases and a clearly scoped niche. The only weakness is that the 'what' names just one action, underselling the description-format and quirk guidance the body provides.

Suggestions

Add one or two more concrete capabilities to the description (e.g., 'apply the servicing PR description template and add an AppContext quirk switch') to raise specificity beyond a single action.

DimensionReasoningScore

Specificity

Names the domain ('EF Core PRs targeting servicing release branches (release/*)') with one concrete action (create PRs), but omits the description-template and quirk work the skill actually covers. Fits anchor 3 (domain + 1-2 concrete actions, not comprehensive); not 4 since there aren't several distinct actions.

3 / 5

Completeness

Explicitly answers both: what ('Create EF Core PRs targeting servicing release branches') and when ('Use when working on a PR that targets a release branch, backporting a fix from main, or when the user mentions servicing, patch, or release branch'). Matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

'backporting a fix from main', 'servicing', 'patch', and 'release branch' are precisely the natural phrases a user would say when they need this skill. Coverage is comprehensive for the niche, exceeding anchor 4's thinner keyword lists.

5 / 5

Distinctiveness Conflict Risk

Clear niche (EF Core servicing backports) with distinct triggers ('backport', 'servicing', 'release branch') that a general PR-creation or EF Core skill would not naturally claim. Minimal conflict risk.

5 / 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

dotnet/efcore

Path

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