CtrlK
BlogDocsLog inGet started
Tessl Logo

dotnet-vertical-slice

Scaffolding guide for building vertical slice features in FinanceHub (.NET 10), including Use Cases, Minimal API endpoints, Command/Query handlers, FluentValidation, and financial reconciliation endpoints.

62

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/dotnet-vertical-slice/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a highly actionable, executable scaffolding guide with a clear sequenced workflow and verification checklist. Its main weaknesses are a missing explicit fix-retry feedback loop for a batch financial operation and an all-inline structure with no reference files.

Suggestions

Add an explicit feedback loop to the Verification Checklist (e.g., 'If dotnet test fails, fix the failing case and re-run before proceeding').

Consider moving the full ReconcileTransactionsHandler implementation into a references/ template file and linking to it from SKILL.md to improve progressive disclosure.

Tighten the framing prose around Step 3 and the reconciliation guidelines to remove near-redundant explanatory sentences.

DimensionReasoningScore

Conciseness

Prose is lean and assumes Claude's competence ('Use immutable record types...', 'Inject domain repositories...'), with complete code earning its place; a few framing sentences and the full inline handler could be trimmed slightly, so not a 5.

4 / 5

Actionability

Provides fully executable, copy-paste-ready C# for command/query records, FluentValidation rules, the handler, and the Minimal API endpoint covering the common reconciliation case.

5 / 5

Workflow Clarity

A clear four-step sequence is paired with inline FluentValidation and a Verification Checklist (build, unit tests, integration test); the only gap is an explicit validate-fix-retry feedback loop for this batch/financial operation, which keeps it just below 5.

4 / 5

Progressive Disclosure

Content is well-organized into numbered sections (directory structure, scaffolding steps, reconciliation guidelines, verification) with inline code appropriate for a scaffolding template; no bundle files exist, so there are no buried or nested references, though the large inline handler example is content that could optionally live in a separate reference file.

4 / 5

Total

17

/

20

Passed

Description

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

The description is specific and clearly distinct to a narrow FinanceHub/.NET vertical-slice niche, but it omits any explicit 'Use when...' trigger guidance, which limits trigger quality and completeness. Adding a natural-language trigger clause would raise the weaker dimensions.

Suggestions

Append a 'Use when...' clause with natural trigger phrases (e.g., 'Use when scaffolding a new FinanceHub feature, adding a Use Case, or building a reconciliation endpoint').

Include user-natural synonyms beyond technical jargon (e.g., 'add a new API feature', 'create a CQRS handler').

Lead with the concrete action verbs (scaffold, build, wire up) rather than the passive 'Scaffolding guide for...'.

DimensionReasoningScore

Specificity

Lists several concrete components ('Use Cases, Minimal API endpoints, Command/Query handlers, FluentValidation, and financial reconciliation endpoints') alongside the scaffolding action, with only minor coverage gaps; not a 5 because it enumerates included parts rather than multiple distinct concrete actions.

4 / 5

Completeness

It clearly states what the skill does ('Scaffolding guide for building vertical slice features...including...') but provides no 'Use when...' trigger clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant but niche keywords ('vertical slice features', 'FinanceHub', '.NET 10', 'FluentValidation') are present, yet common natural variations or synonyms a user might say are missing, and the terms lean technical/proprietary.

3 / 5

Distinctiveness Conflict Risk

The FinanceHub/.NET 10 vertical-slice niche with financial reconciliation specifics is highly distinct with minimal overlap risk against other skills.

5 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
JoseMD12/finance-hub
Reviewed

Table of Contents

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.