CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

testcontainers-integration-tester

Ativado ao configurar ou modificar testes de integração de banco de dados e cache usando Testcontainers (PostgreSQL e Redis) + xUnit + FluentAssertions.

Quality

62%

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 ./plugins/dotnet-clean-arch/skills/testcontainers-integration-tester/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%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 concise, well-organized set of project-specific policies (stack, isolation, retry, real-flow validation) that avoids over-explanation. Its weakness is that none of the guidance is executable — no code examples, no test skeleton, no retry configuration sample — and there is no verification step for the resulting tests.

Suggestions

Add a minimal executable example: a xUnit fixture that spins up PostgreSQL/Redis Testcontainers with a concrete retry/wait strategy, so the isolation and resiliency rules become copy-paste ready.

Include a validation checkpoint at the end, e.g. 'Após escrever os testes, execute-os e confirme que os containers iniciam e o fluxo ponta a ponta passa antes de concluir', to add a feedback loop appropriate for database operations.

Show a concrete test-class skeleton demonstrating the per-class isolated database/context required by guideline 2, since 'contexto isolado' is currently left to interpretation.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — four short guidelines with no concept explanations Claude already knows. The only trimmable padding is the intro sentence, which restates the frontmatter description. Not 5 because that restatement means not every token earns its place; well above anchor 3.

4 / 5

Actionability

Guidance is entirely abstract: 'garanta que as configurações de conexão dos containers tenham políticas de retry automáticas' names a requirement but gives no retry policy example, no Testcontainers module/fixture code, and no test-class skeleton. Anchor 2 (concrete stack named, but nothing executable) rather than 1, since the stack and isolation policy are specifically stated.

2 / 5

Workflow Clarity

The body is a list of policies, not a sequenced workflow — no steps for creating a test and no validation checkpoint (e.g., run the tests and confirm containers start). Per the rubric's scoring notes, database operations without feedback loops cap at 3; with no sequence at all this sits at anchor 2. Not 1 because the four guidelines are coherent and organized, not incoherent.

2 / 5

Progressive Disclosure

Under 50 lines with no external references needed; the skill has well-organized sections (heading + numbered guidelines), which per the rubric's simple-skill exception earns a 5. No bundle files exist and none are referenced.

5 / 5

Total

13

/

20

Passed

Description

56%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 has a distinctive, well-targeted trigger clause with excellent technology keywords, but it is only a 'when' statement. It never tells Claude what the skill actually does, which leaves its core purpose implicit.

Suggestions

Add a 'what' clause before the trigger, e.g. 'Gera e mantém testes de integração de ponta a ponta com instâncias efêmeras de PostgreSQL e Redis via Testcontainers. Ativado ao configurar ou modificar...' so the description answers both what and when.

Include a few more natural trigger variations users might say, such as 'docker', 'containers efêmeros', or 'testes e2e', to broaden keyword coverage.

State the concrete capability actions (e.g. 'criar fixtures de container', 'configurar políticas de retry') instead of only naming the stack.

DimensionReasoningScore

Specificity

Names the domain and an exact tech stack ('testes de integração de banco de dados e cache usando Testcontainers (PostgreSQL e Redis) + xUnit + FluentAssertions'), but the only verbs ('configurar ou modificar') describe the user's task rather than the skill's capabilities. Sits between anchor 2 (generic actions) and anchor 3 (1-2 concrete actions); the highly concrete stack pulls it to 3.

3 / 5

Completeness

Matches anchor 2 exactly: a specific 'when' ('Ativado ao configurar ou modificar...') is present, but there is no 'what' — the description never states what the skill does. Not 3 because anchor 3 requires a clear 'what'; not 1 because the 'when' clause is concrete, not extremely vague.

2 / 5

Trigger Term Quality

Includes strong natural keywords users would say ('testes de integração', 'banco de dados', 'cache', 'Testcontainers', 'PostgreSQL', 'Redis', 'xUnit'), but misses common variations such as 'docker', 'containers', or 'e2e tests'. Good coverage with a few natural terms missing — anchor 4, not 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Testcontainers-based PostgreSQL/Redis integration testing with xUnit) with distinct trigger terms; very unlikely to fire for unrelated skills. Minimal conflict risk.

5 / 5

Total

14

/

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/testcontainers-integration-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.