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.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 tight, highly actionable instruction skill: copy-paste-ready template and quirk code, an implied workflow, and a closing validation checklist. Only minor conciseness trims and an explicit numbered workflow would improve it.

Suggestions

Trim the explanatory sentence 'A quirk lets users opt out of the fix at runtime, reducing patch risk.' to a shorter clause, since the value of the quirk is implicit from context.

Add a short numbered workflow (1. Determine target branch, 2. Set title, 3. Fill description template, 4. Add quirk if applicable, 5. Validate) to make the sequence explicit rather than implied by section order.

Tighten the Validation section into an explicit checklist format so the verification gate is visually unmistakable before PR creation.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes EF Core/git competence — no padding about what PRs or AppContext are — with only minor explanatory phrasing (e.g., 'A quirk lets users opt out of the fix at runtime, reducing patch risk') that could be trimmed, fitting 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	Provides copy-paste-ready artifacts: an exact title format ('[release/XX.0] <original PR title>'), a concrete branch-mapping example ('backport to 10' -> 'release/10.0'), a full description template, and an executable C# quirk snippet, matching 'fully executable; copy-paste ready'.	5 / 5
Workflow Clarity	Sections imply a clear sequence (target branch -> title -> description -> quirk -> validation) and an explicit Validation checklist closes the loop, but steps are not enumerated as a numbered sequence and there is no error-recovery feedback loop, fitting 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	A self-contained, single-purpose skill (~60 lines) with no external references needed and clear section headers; per the simple-skills exception, well-organized sections with no need for bundle files score 5.	5 / 5
	Total	18 / 20 Passed

Description

82%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-scoped description that explicitly covers both what and when with concrete trigger phrases. Trigger-term coverage is good but not exhaustive, and the action list is narrow because the skill itself is single-purpose.

Dimension	Reasoning	Score
Specificity	Names the domain ('EF Core PRs targeting servicing release branches (release/*)') and a concrete action ('Create ... PRs') plus the sub-case 'backporting a fix from main', but lists only 1-2 concrete actions rather than a comprehensive set, matching the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	Clearly states what it does ('Create EF Core PRs targeting servicing release branches (release/*)') and gives an explicit 'Use when ...' clause with concrete trigger phrases, matching the 'clearly and explicitly answers both what AND when' anchor.	5 / 5
Trigger Term Quality	Good natural-term coverage with explicit triggers ('servicing, patch, or release branch') plus 'backport' and 'release/*'; synonyms are present, but it sits just short of fully comprehensive coverage, fitting 'good keyword coverage; a few natural terms missing'.	4 / 5
Distinctiveness Conflict Risk	A clear niche (EF Core servicing/release-branch PRs) with distinct, domain-specific triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	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: dotnet/efcore
Path: .agents/skills/servicing-pr/SKILL.md
Commit: 3772265

Reviewed: 3 days 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.