CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

xunit-moq-fluentassertions-tester

Ativado ao gerar testes de unidade para entidades do Domain ou handlers da Application usando a stack xUnit + Moq + FluentAssertions.

Quality

81%

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

78%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 concise, well-organized set of project-specific testing conventions that avoids over-explaining general concepts and covers naming, mocking, assertions, and file organization. The main gap is the absence of one complete executable test example that ties all conventions together and gives an explicit verify step.

Suggestions

Add one complete executable xUnit test example (class + AAA method) that demonstrates the naming convention, Moq setup, and FluentAssertions together.

Include a brief final step to run the tests (e.g., 'dotnet test') and fix failures, closing the workflow loop.

DimensionReasoningScore

Conciseness

The body is lean with concrete, project-specific rules, but the opening line "Esta habilidade orienta a criação de testes unitários rápidos, isolados e focados nas regras de negócios" and assertion examples Claude already knows ("result.Should().BeTrue()") are minor over-explanations that could be trimmed.

4 / 5

Actionability

Concrete guidance is present throughout — semantic naming examples ("Deve_LancarExcecao_Quando_ChamadoJaFinalizado"), specific assertion calls ("act.Should().Throw<DomainException>()"), and explicit isolation prohibitions — but there is no complete, copy-paste-ready test example showing the conventions assembled into a full test method or class.

4 / 5

Workflow Clarity

As a simple single-purpose skill its rules are unambiguous and no destructive/batch validation is needed, but the guidelines are presented as an unordered list of conventions with no explicit sequence for producing a test (e.g., identify behavior → write AAA test → run and verify), leaving the overall flow implicit.

4 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained, and needs no external references; content is well organized into a header and numbered guideline sections, which per the simple-skill scoring note earns full marks with no bundle files required.

5 / 5

Total

17

/

20

Passed

Description

73%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 distinctive, well-targeted trigger description that names the exact tech stack and architectural targets, with an explicit activation clause. Its main weakness is that it phrased purely as a trigger condition — the skill's own action is embedded in the 'when' clause rather than stated separately, and only one action is described.

Suggestions

State the skill's action explicitly before the trigger clause, e.g. 'Gera testes unitários rápidos e isolados seguindo o padrão AAA. Ativado ao criar testes para entidades do Domain ou handlers da Application com xUnit + Moq + FluentAssertions.' so both 'what' and 'when' are independently explicit.

Add natural trigger synonyms users might say, such as 'testes', 'cobertura de testes', 'TDD', or '.cs', to broaden keyword coverage.

Mention the concrete guidance the skill provides (AAA structure, semantic test naming, mocking rules) to raise specificity beyond a single action.

DimensionReasoningScore

Specificity

"Ativado ao gerar testes de unidade para entidades do Domain ou handlers da Application usando a stack xUnit + Moq + FluentAssertions" names the domain, targets, and stack precisely, but describes only one concrete action (generating unit tests), matching the 'names domain and 1-2 concrete actions' anchor rather than the 'several specific actions' level.

3 / 5

Completeness

"Ativado ao gerar..." is an explicit trigger clause answering 'when', and the 'what' (unit test generation with the named stack for the named targets) is stated within the same phrase — both are present, but the 'what' is not independently declared as the skill's action, keeping it below the fully explicit level 5.

4 / 5

Trigger Term Quality

Natural terms a user would say are present ("testes de unidade", "xUnit", "Moq", "FluentAssertions", "Domain", "Application"), giving good keyword coverage, but common variations like "TDD", "cobertura de testes", or file extensions (.cs) are missing, so it falls short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The exact stack (xUnit + Moq + FluentAssertions) combined with DDD/Clean-Architecture layer names (Domain entities, Application handlers) carves a clear niche with distinct triggers and minimal risk of firing for the wrong skill.

5 / 5

Total

16

/

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

JoseMD12/testing-tessl

Path

plugins/dotnet-clean-arch/skills/xunit-moq-fluentassertions-tester/SKILL.md

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.