CtrlK
BlogDocsLog inGet started
Tessl Logo

implement

Implements use cases for C# and Blazor (.NET 10) applications using a Vertical Slice Architecture. Takes a UC-XXX.md specification and generates feature-folder components, C# Commands/Queries, EF Core entities/configurations, and Blazor pages/components. Use when the user asks to "implement a use case in C#", "build a Blazor page", "create a Vertical Slice", or mentions Blazor, .NET 10, or C# implementation.

67

Quality

80%

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

SKILL.md
Quality
Evals
Security

Quality

Content

68%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-organized, actionable instruction skill with concrete conventions and a clear numbered workflow. The main gap is the absence of an explicit build/migration failure-recovery loop in a skill that performs destructive file operations, which limits workflow clarity.

Suggestions

Add an explicit feedback loop after the `dotnet build` verification step: if the build fails, read the errors, fix them, and re-run until it compiles cleanly.

Include a brief validation note for EF Core migrations (e.g., verify `dotnet ef database update` succeeds) since the skill instructs creating new migrations.

Tighten the styling bullets (e.g., "Use design tokens from wwwroot/app.css; include hover, loading, empty, and error states") to remove florid phrasing.

DimensionReasoningScore

Conciseness

Dense, directive guidance with no padding explaining C#/Blazor concepts Claude already knows; minor florid phrasing in the styling section ("curated harmonious color palettes", "subtle shadows") could be trimmed.

4 / 5

Actionability

Concrete file-naming conventions (UCXXX_Page.razor, UCXXX_Command.cs), exact attributes (@rendermode, [StreamRendering]), and a `dotnet build` command; instruction-only so absence of full code snippets is acceptable, though a small DbContext-factory usage example would help.

4 / 5

Workflow Clarity

Clear 8-step sequence plus a reconciliation subflow and a build verification checkpoint, but no explicit build-failure/migration feedback loop in a skill that performs destructive file operations (migration creation, sample-page removal), which the rubric caps at 3.

3 / 5

Progressive Disclosure

Self-contained and well-sectioned (## Goal, ## If an Implementation Already Exists, ## Workflow & Conventions) with no nested references and no need for bundle files; the long numbered workflow could arguably be split but is appropriately inline.

4 / 5

Total

15

/

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 strong, specific description that clearly states what it does and when to use it with concrete trigger phrases, tightly scoped to a C#/Blazor/.NET 10 Vertical Slice niche. Only minor gap is a few missing natural synonyms in the trigger list.

DimensionReasoningScore

Specificity

Lists multiple concrete generation actions — "feature-folder components, C# Commands/Queries, EF Core entities/configurations, and Blazor pages/components" — giving comprehensive coverage rather than a single generic action.

5 / 5

Completeness

Explicitly answers both what (implements use cases, generates named component types) and when ("Use when the user asks to..." with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ("implement a use case in C#", "build a Blazor page", "create a Vertical Slice") plus Blazor/.NET 10/C# terms, but omits a few natural variations like ".razor" or "EF Core".

4 / 5

Distinctiveness Conflict Risk

A clear niche — C#/.NET 10/Blazor Vertical Slice implementation — with distinct, technology-specific triggers that minimize overlap with other skills.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
AI-Unified-Process/marketplace
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.