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

93%

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

92%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.

An exemplary scaffold skill: dense with project-specific knowledge, correctly sequenced with validation and a checklist, and focused on the real footgun (four registration sites). The only soft spot is the thin permissions step and placeholder endpoint mapping, which keep actionability just below fully executable.

Suggestions

Add a minimal {Name}Permissions skeleton (one resource class + All collection) to Step 2 so the permissions step is executable without opening CatalogPermissions.

Show one concrete endpoint registration example (e.g. a MapGet with the version-set group) instead of only the commented `// group.MapCreate{Entity}Endpoint();` placeholder.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: no basic concepts are explained, code comments carry only non-obvious rules ("MUST be last — applies tenant + soft-delete filters"), and every section adds project-specific knowledge (e.g. the module load-order table).	5 / 5
Actionability	Mostly executable guidance: full copy-paste-ready code for the module class and DbContext, exact `dotnet sln` and `dotnet test` commands, and a concrete copy-don't-write rule for the .csproj files. Minor gaps remain — the permissions section is a one-line pointer with no example shape, and endpoint mapping is left as a commented placeholder (`// group.MapCreate{Entity}Endpoint();`).	4 / 5
Workflow Clarity	Seven clearly sequenced steps with an explicit verification step (`dotnet build` expecting 0 warnings, Architecture.Tests "must pass"), a closing checklist, and failure-mode diagnosis for the riskiest operation ("Miss the Mediator marker → handlers silently undiscovered"). The destructive/batch validation cap does not apply since validation is present.	5 / 5
Progressive Disclosure	No bundle files exist, and the ~130-line body is appropriately kept in a single file: well-organized sections, with detail delegated one level deep via clearly signaled pointers to `create-migration`, `.agents/rules/architecture.md`, and `.agents/rules/eventing.md`, plus "mirror the shape of `CatalogPermissions`" instead of inlining an example.	5 / 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 dense, well-constructed description: it states what is built, when to use it, and how it differs from the related add-feature skill, all in third person with no padding. The only room for improvement is broader synonym coverage in the trigger terms.

Dimension	Reasoning	Score
Specificity	The description enumerates the concrete artifacts created — "runtime + Contracts projects, IModule, DbContext, permissions, migrations, and the four registration sites" — giving comprehensive, specific coverage of the module-creation scope with no vague filler.	5 / 5
Completeness	It explicitly answers both questions: what ("Create a new module (bounded context) — runtime + Contracts projects, IModule, DbContext, permissions, migrations...") and when ("Use when adding a distinct business domain"), with a concrete trigger phrase in third-person imperative voice.	5 / 5
Trigger Term Quality	Natural terms include "new module", "bounded context", "adding a distinct business domain", and "feature in an existing module" — phrases a user would plausibly say. A few natural synonyms (e.g. "add a domain", "new service area") are missing, so it stops just short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	It carves out a clear niche (creating a new bounded context/module) and explicitly disambiguates against the sibling skill ("For a feature in an existing module, use add-feature"), minimizing wrong-skill triggering.	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: 0bd98e3

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