add-module

Create a new module (bounded context) — runtime + Contracts projects, IModule, DbContext, permissions, migrations, and the four registration sites. Use when adding a distinct business domain. For a feature in an existing module, use add-feature.

Quality

94%

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

96%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 high-ceremony workflow documented with lean, executable templates, an explicit verification step, and a footgun callout. The only minor gap is progressive-disclosure structuring, which is limited by the absence of bundle files.

Suggestions

Add a one-line error-recovery hint to Step 7 (e.g. 'On build warnings or test failure, fix and re-run before proceeding') to make the feedback loop explicit rather than implied.

Consider extracting the load-order list and the Step 6 registration edits into a references/ file so the overview stays a pure checklist pointer, improving progressive disclosure.

Verify the referenced rule files (.agents/rules/architecture.md, .agents/rules/eventing.md) exist in the bundle and surface them under a named References section for clearer navigation.

Dimension	Reasoning	Score
Conciseness	Lean throughout — it assumes Claude knows C#/ASP.NET and never pads with concept explanations; every annotation (e.g. 'MUST be last — applies tenant + soft-delete filters') is load-bearing rather than filler.	5 / 5
Actionability	Provides copy-paste-ready C# templates, exact dotnet sln commands, and concrete file paths with a consistent {Name} placeholder convention covering the common cases.	5 / 5
Workflow Clarity	A clear 7-step sequence culminating in an explicit Verify step (build with '0 warnings', Architecture.Tests, full test run) and a closing checklist, with the Step 6 footgun calling out silent failure modes for the riskiest part.	5 / 5
Progressive Disclosure	Well-organized sections with one-level-deep, clearly signaled references (.agents/rules/architecture.md, .agents/rules/eventing.md, and the create-migration skill), but no bundle files exist and most detail is inline, so it is good rather than exemplary in cross-file structuring.	4 / 5
	Total	19 / 20 Passed

Description

92%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 states what the skill builds and when to use it, with explicit disambiguation against a sibling skill. Only slightly short of perfect on trigger-term breadth.

Dimension	Reasoning	Score
Specificity	Enumerates the concrete components to create — 'runtime + Contracts projects, IModule, DbContext, permissions, migrations, and the four registration sites' — giving comprehensive, multi-part coverage rather than a single vague action.	5 / 5
Completeness	Explicitly answers both 'what' (the created parts are listed) and 'when' ('Use when adding a distinct business domain'), with concrete trigger guidance and a disambiguation note.	5 / 5
Trigger Term Quality	Natural phrasings like 'adding a distinct business domain' and 'bounded context' appear, plus a disambiguating reference to add-feature, but it lacks the synonym/file-extension breadth (e.g. .csproj) that would mark full anchor-5 coverage.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (new bounded context) and explicitly redirects the overlapping case ('For a feature in an existing module, use add-feature'), minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: fullstackhero/dotnet-starter-kit
Path: .agents/skills/add-module/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.