add-feature

Add a vertical-slice feature (command/query + handler + validator + endpoint) to an existing FSH module. Use when adding an API endpoint or business operation to a module that already exists.

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

93%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 well-structured, executable vertical-slice recipe with concrete code, a verify step, and a checklist, deferring detail to external conventions appropriately. The only gap is an explicit error-recovery loop after the verify step.

Suggestions

In Step 6, add an explicit feedback loop: "If build/test fails, fix the reported errors and re-run until 0 warnings and tests pass."

Show a one-line query example alongside the create-command example, or note explicitly that queries follow the same handler/validator shape via the query-patterns reference.

Dimension	Reasoning	Score
Conciseness	Lean and efficient; it assumes C#/Mediator competence and reserves prose for non-obvious project facts (no IRepository, auto-stamped audit fields) that Claude could not infer.	5 / 5
Actionability	Provides copy-paste-ready C# for the common create-command case plus concrete build/test commands, with template placeholders clearly delimited.	5 / 5
Workflow Clarity	Six numbered steps with an explicit Verify checkpoint and a closing checklist, but the build/test failure feedback loop (fix then re-run) is implied rather than stated.	4 / 5
Progressive Disclosure	A clear overview body that defers full conventions to .agents/rules/api-conventions.md and related patterns to query-patterns / testing-guide — one-level, well-signaled references.	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 tight, third-person description that pairs a concrete component breakdown with an explicit Use-when trigger, well-scoped to its FSH niche. Only minor keyword-synonym coverage is missing.

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates four concrete slice components — "command/query + handler + validator + endpoint" — giving comprehensive coverage of what adding the feature entails.	5 / 5
Completeness	Explicitly answers both what ("Add a vertical-slice feature ...") and when ("Use when adding an API endpoint or business operation to a module that already exists").	5 / 5
Trigger Term Quality	Natural phrases a user would say are present ("adding an API endpoint", "business operation", "module"), but a few common synonyms (e.g. "service", "operation") are absent.	4 / 5
Distinctiveness Conflict Risk	Scoped to an existing FSH module with a vertical-slice trigger, a clear niche that is unlikely to fire for unrelated skills.	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-feature/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.