add-full-slice

Build a capability end-to-end — backend vertical slice (Contracts→handler→validator→endpoint) AND the React page wired to it. Use when delivering a user-facing feature across API + UI. Composes add-feature + add-react-page.

Quality

91%

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 tight, highly actionable skill body with concrete paths, patterns, and verify commands, plus a clear sequenced workflow and checklist. The only gap is an explicit error-recovery loop in the verification steps.

Suggestions

Add an explicit feedback loop after 'Build + test backend green' (e.g. 'if red, fix and re-run until green before touching the frontend').

Spell out the error-recovery path in the 'Verify end-to-end' section (what to do when lint or e2e fails).

Dimension	Reasoning	Score
Conciseness	Lean ~45-line body that assumes Claude's competence — no explaining of what handlers/validators are, and detail is delegated to composed skills via tight references rather than duplicated.	5 / 5
Actionability	Gives concrete file paths (Modules.{X}.Contracts/v1/{Area}/), class patterns (public sealed, internal static Map…Endpoint, .RequirePermission(...)), and copy-paste verify commands (dotnet build src/FSH.Starter.slnx && dotnet test ...; npm run lint && npm run test:e2e).	5 / 5
Workflow Clarity	Clear numbered 5-step sequence with checkpoints ('Build + test backend green', 'Lock the contract') and a closing checklist, but lacks an explicit fix-and-retry feedback loop for failed builds/tests.	4 / 5
Progressive Disclosure	Well-organized sections (Order of operations, The contract, Verify, Checklist) with one-level-deep, clearly signaled references to add-feature/add-react-page/add-entity/add-permission rather than inlining their detail.	5 / 5
	Total	19 / 20 Passed

Description

88%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, concrete description that clearly states what the skill does and when to use it, with specific sub-actions and a natural trigger phrase. Its only weakness is slight overlap with the two skills it composes.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'backend vertical slice (Contracts→handler→validator→endpoint)' and 'the React page wired to it' — with comprehensive coverage of the end-to-end capability.	5 / 5
Completeness	Explicitly answers both 'what' (build backend slice + React page, composing add-feature + add-react-page) and 'when' ('Use when delivering a user-facing feature across API + UI') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Natural phrases like 'delivering a user-facing feature across API + UI' and 'end-to-end' are present, but a few common synonyms (e.g. 'full-stack', 'feature') are not surfaced.	4 / 5
Distinctiveness Conflict Risk	Clear niche (end-to-end API+UI slice) with distinct triggers, but minor overlap risk with the two skills it composes (add-feature, add-react-page) for users wanting only one half.	4 / 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-full-slice/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.