CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

80

Quality

100%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tightly written, fully actionable guide: it sequences the servicing-PR workflow, ships an executable description template and AppContext-switch code, and closes with an explicit validation checklist. Organization is clean and self-contained with no need for split-out reference files.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence; it avoids explaining basic concepts, and the only explanatory line ("A quirk lets users opt out of the fix at runtime, reducing patch risk") is domain-specific EF Core context that earns its tokens, matching the score-3 anchor.

3 / 3

Actionability

It provides copy-paste-ready, fully executable guidance: a concrete PR-title format, a complete description template, and runnable C# (AppContext.TryGetSwitch ...) for the quirk, matching the score-3 anchor for fully executable code and specific examples.

3 / 3

Workflow Clarity

The sections are sequenced (branch → title → description → quirk → validation) with an explicit Validation checklist and a "Verify the branch exists before creating the PR" checkpoint, matching the score-3 anchor for clear sequence with explicit validation steps.

3 / 3

Progressive Disclosure

Content is well-organized into clearly headed sections with no nested or multi-level references; for a single-purpose skill with no need for external reference files, well-organized sections alone justify the score-3 per the rubric's simple-skills note.

3 / 3

Total

12

/

12

Passed

Description

100%

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 excellent: it states concrete capabilities, includes a clear "Use when" trigger with natural keywords, and occupies a distinct niche unlikely to conflict with other skills. Voice is imperative ("Create ..."), consistent with the good-example style and not the penalized first/second-person forms.

DimensionReasoningScore

Specificity

"Create EF Core PRs targeting servicing release branches (release/*)" and "backporting a fix from main" list multiple concrete actions, matching the score-3 anchor that lists specific actions rather than a single vague verb.

3 / 3

Completeness

It explicitly answers both halves: the "what" ("Create EF Core PRs targeting servicing release branches") and the "when" via an explicit "Use when ..." clause, matching the score-3 anchor for both what and when with explicit triggers.

3 / 3

Trigger Term Quality

Natural user-facing terms are well covered — "servicing, patch, or release branch" and "backporting a fix from main" — giving good coverage of the phrasings a user would actually say, matching the score-3 anchor.

3 / 3

Distinctiveness Conflict Risk

The niche is narrow and distinct (EF Core servicing on release/* branches) with specific triggers (servicing, patch, release branch, backport), making mis-activation for unrelated skills unlikely per the score-3 anchor.

3 / 3

Total

12

/

12

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
dotnet/efcore
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.