CtrlK
BlogDocsLog inGet started
Tessl Logo

testing-guide

Write tests for an FSH feature — xUnit + Shouldly + NSubstitute + AutoFixture, with naming and AAA conventions. Use when adding unit/handler/validator/entity tests. Full rules in .agents/rules/testing.md + integration-testing.md.

71

Quality

86%

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

86%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, well-structured testing guide that assumes competence and provides actionable examples across the common test types. The main gap is template placeholders in the handler example that prevent fully copy-paste-ready code.

Suggestions

Replace '_db = /* in-memory or test DbContext */' with a concrete in-memory DbContext setup snippet so the handler example is copy-paste ready.

Add a brief 'verify' loop after the Run section (e.g., run the new test, fix failures, keep Architecture.Tests green) to make the workflow feedback loop explicit.

Briefly justify the {Entity}/{X} placeholder convention so the template flexibility is documented rather than inferred.

DimensionReasoningScore

Conciseness

Lean throughout: it states the stack, lists conventions, gives code examples, and run commands without explaining concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Provides concrete, mostly executable code for handler/validator/entity/service-dep tests and real dotnet commands, but template placeholders like {Entity}, {X}DbContext, and '_db = /* in-memory or test DbContext */' require filling in.

4 / 5

Workflow Clarity

Clear structure from conventions to per-type examples to architecture guardrails and a Run section with verification, but lacks an explicit write-test -> run -> fix-failures feedback loop.

4 / 5

Progressive Disclosure

Well-organized sections keep the quick-reference inline while offloading detailed rules to clearly signaled one-level-deep references (.agents/rules/testing.md and integration-testing.md).

5 / 5

Total

18

/

20

Passed

Description

87%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 that clearly states the task, scopes it to a specific stack and project, and provides an explicit 'Use when' trigger. It is concise and distinct, with only minor room for more synonyms and additional action verbs.

DimensionReasoningScore

Specificity

Names the domain, exact stack (xUnit + Shouldly + NSubstitute + AutoFixture), AAA/naming conventions, and four test categories, but centers on a single 'Write tests' verb rather than multiple distinct actions.

4 / 5

Completeness

Explicitly answers both what (write tests with the named stack and conventions) and when ('Use when adding unit/handler/validator/entity tests') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases like 'Write tests' and 'adding unit/handler/validator/entity tests' match what a user would say, with good coverage but few synonyms or variations.

4 / 5

Distinctiveness Conflict Risk

Pinned to the FSH project and a specific stack with explicit exclusions ('Not Moq, not FluentAssertions'), giving it a clear niche with minimal overlap risk.

5 / 5

Total

18

/

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
fullstackhero/dotnet-starter-kit
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.