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

85%

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

82%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-structured, actionable triage skill with a complete repro template, explicit security and regression checkpoints, and clear sectioning. The main gaps are minor: a slightly padded intro and the absence of an explicit fix-and-retry loop in the repro-creation sub-process.

Suggestions

Tighten the opening paragraph and trim explanatory prose (e.g. the 'User-submitted bug reports frequently provide only fragmentary information...' sentence) to improve token efficiency.

Add an explicit validate-fix-retry loop to the 'Creating a minimal repro' section (e.g. 'compile and run; if it does not reproduce the reported error, adjust the repro and retry') to strengthen the workflow's feedback loop.

Consider extracting the dense 'Database providers used in the bug report and repro' guidance into a reference file to keep the main SKILL.md leaner.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with a complete executable repro template and concrete commands, but the opening paragraph and a few prose passages ('User-submitted bug reports frequently provide only fragmentary information...') could be trimmed without losing clarity.	4 / 5
Actionability	It provides a complete, copy-paste-ready C# repro template plus a concrete `gh label list` command and an exact posting format (heading text, collapsible <details> block), covering the common cases fully.	5 / 5
Workflow Clarity	The seven-step sequence includes explicit checkpoints — a security 'exit immediately' gate (step 2) and a regression confirmation step (5.iii) — but the minimal-repro iteration lacks an explicit validate-fix-retry feedback loop, leaving a minor validation gap.	4 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-organized into clearly signaled sections (High-level steps, Area labels, Creating a minimal repro, Posting your findings) with no nested references, though some sections (e.g. provider guidance) are fairly dense inline.	4 / 5
	Total	17 / 20 Passed

Description

87%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, specific description that clearly conveys both the triage actions and the triggering context, scoped tightly to the EF Core repo. The only notable issue is second-person voice ('Use this skill'), which slightly reduces the specificity score per the rubric.

Dimension	Reasoning	Score
Specificity	The description lists several concrete triage actions ('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') — comprehensive but penalized one point for second-person voice ('Use this skill').	4 / 5
Completeness	It explicitly answers both 'what' (sets type, assigns labels, repro, regression, duplicates) and 'when' ('Use this skill to triage an incoming issue on the EF Core repo') with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Natural maintainer phrases are present ('triage', 'incoming issue', 'EF Core repo', 'bug report', 'feature request'), giving good keyword coverage, though a few synonyms or repo-shorthand variants are missing.	4 / 5
Distinctiveness Conflict Risk	The scope is tightly bound to triaging issues on the EF Core repo, a distinct niche with minimal overlap risk against other skills.	5 / 5
	Total	18 / 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/triage/SKILL.md
Commit: 92b26f9

Reviewed: about 1 hour 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.