add-entity

Add a domain entity/aggregate with EF configuration and a migration to an existing FSH module. Use when adding a new database-backed entity. Pairs with add-feature and create-migration.

Quality

85%

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

83%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 dense, highly actionable template skill with executable code and exact commands that assumes Claude's competence. The main weakness is the absence of an explicit validation feedback loop for the database migration step, which limits workflow clarity.

Suggestions

Add an explicit validation feedback loop around the migration step (e.g., 'run `dotnet build`; if it fails, fix errors and rebuild before migrating') to satisfy the database-operation feedback-loop expectation.

Spell out the post-migration verification (e.g., inspect the generated `Up`/`Down` and confirm the new table/columns) as a checkpoint in the Migration section, not only in the final checklist.

Consider noting what to do if `dotnet ef migrations add` fails (wrong `--context`, missing DbSet) so the retry path is explicit rather than implied.

Dimension	Reasoning	Score
Conciseness	Lean directive prose ('Rich domain model: sealed aggregate, private EF ctor, static factory...') assumes C#/EF competence and avoids explaining concepts Claude already knows; every line is substantive template or justified guidance.	5 / 5
Actionability	Provides fully executable, copy-paste-ready templates for the entity, domain event, EF configuration, DbSet registration, and the exact `dotnet ef migrations add` command with concrete project paths, covering the common cases.	5 / 5
Workflow Clarity	Sections are clearly sequenced (Entity -> Domain event -> EF config -> Register -> Migration -> Checklist) with a build checkpoint, but for a database-schema operation there is no explicit validate->fix->retry feedback loop, which caps this dimension per the rubric's database-operation guidance.	3 / 5
Progressive Disclosure	Well-organized into clearly headed sections with one-level-deep, clearly signaled references (`.agents/rules/database.md` and the create-migration skill); all templates are inline with no bundle files, so structure is good but not split across files.	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 well-crafted, third-person description that concretely names the entity/EF/migration actions, provides an explicit 'Use when' trigger, and cleanly delineates its niche from related skills. Minor synonym coverage is the only gap.

Dimension	Reasoning	Score
Specificity	Names three concrete actions — 'Add a domain entity/aggregate', 'EF configuration', and 'a migration' — plus the target 'existing FSH module'; coverage is solid but stops short of the comprehensive multi-action list that defines a 5.	4 / 5
Completeness	Explicitly states both what ('Add a domain entity/aggregate with EF configuration and a migration') and when ('Use when adding a new database-backed entity') with a concrete trigger phrase, matching the anchor for clearly answering both.	5 / 5
Trigger Term Quality	Includes natural domain terms a user would say ('domain entity', 'aggregate', 'migration', 'database-backed entity') with a clear 'Use when' trigger, though common synonyms like 'model', 'table', or 'record' are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear FSH-specific niche and explicitly distinguishes itself from sibling skills via 'Pairs with add-feature and create-migration', minimizing conflict risk.	5 / 5
	Total	18 / 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-entity/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.