mediator-reference

CQRS interface reference for FSH. This project uses the Mediator source generator, NOT MediatR. Reference when implementing commands, queries, and handlers.

Quality

82%

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 crisp, well-structured reference that is token-efficient and highly actionable, with strong error-recovery guidance via the common-errors table. Its main limitation is the templated placeholders and the hand-off to add-module for the complete registration workflow.

Suggestions

Add a brief inline validation step after registration (e.g. 'build the API and DbMigrator; a missing handler at runtime means an assembly was omitted') to close the workflow loop without forcing a jump to add-module.

Provide one fully-substituted concrete example (e.g. a real module name) alongside the templated pattern so a snippet is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Lean and table-driven; assumes C# / CQRS competence and explains only the non-obvious Mediator-vs-MediatR distinctions and project conventions, with every line earning its place.	5 / 5
Actionability	Concrete, copy-paste-shaped code with exact interface names, file paths, and rules (ValueTask<T>, .ConfigureAwait(false), public sealed); the templated {X}/{Entity} placeholders are a minor gap from literal executability.	4 / 5
Workflow Clarity	The registration section gives a clear sequenced procedure (two markers + moduleAssemblies entry in both Program.cs files) and the common-errors table provides symptom→cause→fix feedback loops, but it delegates the full procedure to the add-module skill rather than embedding explicit validate-then-proceed checkpoints.	4 / 5
Progressive Disclosure	Short, well-sectioned reference (Interfaces, Pattern, Registration, Common errors) with a clearly signaled one-level pointer to the add-module skill for the full procedure; no bundle files exist to misorganize.	5 / 5
	Total	18 / 20 Passed

Description

78%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 tight, specific description that pinpoints the project niche and disambiguates Mediator from MediatR, with an explicit use-when clause. It could enumerate a few more trigger variations to reach the top level.

Suggestions

Expand the 'when' clause to surface more natural triggers, e.g. 'Use when implementing commands/queries/handlers, wiring up module registration, or seeing MediatR compilation errors in FSH.'

Mention file extensions or concrete artifacts (e.g. 'ICommand/IQuery handlers, AddMediator registration') to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('CQRS interface reference for FSH') and several concrete items (commands, queries, handlers, Mediator vs MediatR); minor coverage gaps keep it just below a 5.	4 / 5
Completeness	Clearly states what it is ('CQRS interface reference for FSH ... Mediator source generator, NOT MediatR') and gives an explicit 'Reference when implementing commands, queries, and handlers' trigger, but the 'when' is terse and could spell out more scenarios.	4 / 5
Trigger Term Quality	Natural trigger terms a developer would say ('implementing commands, queries, and handlers', 'Mediator', 'MediatR', 'FSH') are present with good coverage, though a few common phrasings (e.g. 'CQRS handler') are not enumerated.	4 / 5
Distinctiveness Conflict Risk	Highly specific niche (FSH project, Mediator source generator) with an explicit MediatR disambiguation, giving it distinct triggers and minimal conflict risk.	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: fullstackhero/dotnet-starter-kit
Path: .agents/skills/mediator-reference/SKILL.md
Commit: 3f2959e

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