CtrlK
BlogDocsLog inGet started
Tessl Logo

integration-test-generator

Generate integration tests for multiple interacting components in Python. Use when testing interactions between: (1) Multiple services or APIs (REST/GraphQL endpoints, microservices), (2) Database operations with repositories/ORMs (SQLAlchemy, Django ORM), (3) External services (payment gateways, email services, third-party APIs), (4) Message queues and event-driven systems, (5) Full stack workflows (API + database + business logic). Provides test structure templates, fixtures, test data builders, and patterns for pytest-based integration testing.

84

1.02x
Quality

78%

Does it follow best practices?

Impact

91%

1.02x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/integration-test-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An actionable, well-organized skill with strong executable examples and clean delegation to two real reference files. Its main weaknesses are repeated fixture examples, mild over-explanation of pytest basics, and the absence of an explicit generate-then-verify workflow.

Suggestions

Remove the duplicate `db_session` fixture definitions: keep one canonical version and reference it from Best Practices and Quick Reference instead of re-inlining it.

Add a short end-to-end generation workflow with a validation checkpoint (e.g., "after writing tests, run `pytest tests/integration/` and fix failures before proceeding") to satisfy the database-operation feedback-loop expectation.

Trim introductory prose that restates pytest/fixture fundamentals ("Integration tests verify...", "Use fixtures to set up and tear down") since Claude already knows these concepts.

DimensionReasoningScore

Conciseness

Mostly efficient code-focused content, but the `db_session` fixture is repeated across "Test Fixtures Pattern", "Best Practices #1", and "Quick Reference", and prose like "Integration tests verify that multiple components work correctly together" explains pytest basics Claude already knows.

3 / 5

Actionability

Concrete, mostly copy-paste-ready code and pytest commands throughout; minor gaps such as omitted imports (create_engine, Base, sessionmaker, User) in several fixture examples keep it just below fully executable.

4 / 5

Workflow Clarity

Provides templates and patterns rather than an explicit end-to-end generation sequence, and lacks a run-the-tests verification checkpoint; the database-operation context with no validate→fix→retry feedback loop caps this at 3 per the rubric.

3 / 5

Progressive Disclosure

Well-signaled one-level-deep references to the real `references/patterns.md` and `references/test_data.md` files with an itemized delegation section, though the main body is somewhat heavy with inlined examples that could partly live in the references.

4 / 5

Total

14

/

20

Passed

Description

96%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 capabilities and provides an enumerated "Use when" trigger list covering five interaction scenarios. Only marginal overlap risk with adjacent testing skills prevents a perfect distinctiveness score.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Generate integration tests", "Provides test structure templates, fixtures, test data builders, and patterns" — giving comprehensive coverage rather than a single generic verb.

5 / 5

Completeness

Explicitly answers both what ("Generate integration tests... Provides test structure templates, fixtures...") and when ("Use when testing interactions between: (1)...(5)") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural terms users would say — "integration tests", "REST/GraphQL endpoints", "microservices", "SQLAlchemy", "Django ORM", "payment gateways", "message queues", "pytest" — including synonyms and framework names.

5 / 5

Distinctiveness Conflict Risk

Clear integration-testing niche with specific triggers, but "testing"/"pytest" framing carries minor overlap risk with a hypothetical unit-test-generation skill.

4 / 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
ArabelaTso/Skills-4-SE
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.