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

86%

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

90%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 code-template skill: lean, entirely project-specific, and immediately executable. The only refinements are making build validation an explicit inline step (or short feedback loop) before the migration command and promoting the database.md reference to a clearly signaled pointer.

Dimension	Reasoning	Score
Conciseness	Every line is project-specific convention Claude cannot know (opt-in marker interfaces, Guid.CreateVersion7(), no manual query filter, ValueGeneratedNever() gotcha); there is no padding or explanation of known concepts. Matches the 5-anchor.	5 / 5
Actionability	Complete, copy-paste-ready C# templates with placeholders and an exact migration command including project paths and --context. Matches the 5-anchor's fully executable guidance.	5 / 5
Workflow Clarity	Sections clearly sequence the work (Entity → event → EF config → DbSet → migration) and close with a checklist, with build validation required ('build first', 'build green'). Not 5: validation is implicit in checklist items rather than explicit inline checkpoints or a fix-and-retry feedback loop, which matters for database operations.	4 / 5
Progressive Disclosure	Well-organized single file where all inline code is core template material; one clearly signaled one-level reference (database.md) plus delegation to the create-migration skill. Not 5: the body exceeds the simple-skill threshold and the database.md pointer is a bare inline mention rather than a well-signaled section-level link to a file that lives outside the skill bundle.	4 / 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 strong description with a clear what-and-when structure, explicit sibling-skill boundaries, and concrete domain language. Its main limitation is a single narrow trigger phrase and some missing natural synonyms that would broaden recall.

Suggestions

Broaden the trigger clause with common user phrasings, e.g. 'Use when adding a new database-backed entity, table, or aggregate to a module'.

Add one or two natural synonyms (e.g. 'DbSet', 'EF Core model') to the description so users describing the task in EF terms still match.

Mention the domain-event piece of the workflow so the description's capability list matches the body's steps.

Dimension	Reasoning	Score
Specificity	Names the domain ('existing FSH module', 'EF configuration') and several concrete actions (add entity/aggregate, EF configuration, migration). Not 5: coverage has minor gaps — DbSet registration and domain-event creation from the body are not mentioned in the description.	4 / 5
Completeness	Both 'what' and 'when' are explicitly present ('Use when adding a new database-backed entity'). Not 5: the 5-anchor requires multiple concrete trigger phrases, and this has a single, narrow trigger clause comparable to the 4-anchor example.	4 / 5
Trigger Term Quality	Natural terms like 'domain entity', 'aggregate', 'EF', 'migration', and 'database-backed entity' are present. Not 5: common user variations such as 'table', 'DbSet', or 'model' are missing.	4 / 5
Distinctiveness Conflict Risk	'Pairs with add-feature and create-migration' explicitly delimits sibling skills and delegates migration away, giving a clear niche (FSH domain entities) with minimal overlap risk. Matches the 5-anchor.	5 / 5
	Total	17 / 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: 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.