triage

Use this skill to triage an incoming issue on the EF Core repo (bug report or feature request). Sets the issue type (bug/feature), assigns EF area labels, attempts to arrive at a minimal repro reproducing the bug, checks whether it represents a regression, finds possible duplicates, etc.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%

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

A dense, actionable triage skill with an executable repro template, concrete commands, and a well-sequenced workflow including security-exit and regression-confirmation checkpoints; the main gap is the absence of progressive disclosure into separate reference files.

Suggestions

Split the 'Database providers used in the bug report and repro' and 'Posting your findings' detail into a separate REFERENCES.md (or similar) and link to it from a concise overview, moving progressive_disclosure toward a one-level-deep structure.

Consider extracting the full C# repro template into a bundled script (e.g. scripts/repro-template.cs) referenced by path, keeping the body focused on the minimalization and triage workflow.

The intro paragraph could be tightened (e.g. 'forcing you to try to fill in the missing information in the effort to create a minimal repro') to further improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Lean, EF-specific guidance that assumes Claude knows C#/EF — no generic concept explanations — and every section (repro template, minimalization rules, provider porting) earns its place; it is not a 2 because there is no padding or unnecessary library background.	3 / 3
Actionability	Provides a full copy-paste C# repro template, the executable `gh label list --search "area-" --repo dotnet/efcore` command, exact label prefixes, and precise comment-formatting instructions ('AI Triage' heading, collapsible <details> block), matching the copy-paste-ready top anchor.	3 / 3
Workflow Clarity	A numbered 'High-level steps' sequence (1–7) with explicit checkpoints — a security assessment that mandates immediate exit (step 2) and a regression feedback loop testing the repro on both failing and previous versions (step 5.iii) — meeting the clear-sequence-with-validation top anchor.	3 / 3
Progressive Disclosure	Well-organized into clear sections but all content is inline in a single ~98-line file with no one-level-deep bundle references; it is not a 3 because the top anchor requires signaled separate-file references, and not a 1 because the body is sectioned rather than a monolithic wall of text.	2 / 3
	Total	11 / 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.

A strong, specific, third-person description with an explicit trigger and a clear EF Core niche; it names concrete actions rather than vague capabilities and is unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Sets the issue type (bug/feature)', 'assigns EF area labels', 'attempts to arrive at a minimal repro', 'checks whether it represents a regression', 'finds possible duplicates' — matching the top anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (sets type, assigns labels, repro, regression, duplicates) and when via the 'Use this skill to triage an incoming issue' trigger, satisfying the explicit-trigger requirement that would otherwise cap completeness at 2.	3 / 3
Trigger Term Quality	Uses natural triage-domain terms a user would say — 'triage', 'incoming issue', 'bug report', 'feature request', 'minimal repro', 'regression', 'duplicates' — giving good coverage rather than abstract jargon.	3 / 3
Distinctiveness Conflict Risk	Scoped to 'the EF Core repo' with EF-specific labels and repro workflow, a clear niche unlikely to trigger for unrelated skills; capability verbs are third person ('Sets', 'assigns', 'attempts').	3 / 3
	Total	12 / 12 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/triage/SKILL.md
Commit: 61317c9

Reviewed: 5 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.