CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

temporal-python-testing

Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.

Quality

76%

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 ./skills/temporal-python-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 skill has a solid Quick Start with executable pytest patterns and a well-formatted resource index, but four filler/boilerplate sections pad the token budget, the testing workflow is never explicitly sequenced, and all progressive-disclosure references point to files that do not exist in the bundle, leaving mocking and replay guidance unavailable. Tightening the body and shipping (or inlining) the referenced resources would address the main weaknesses.

Suggestions

Create the four referenced resource files (resources/unit-testing.md, resources/integration-testing.md, resources/replay-testing.md, resources/local-setup.md) or inline their key content — currently every progressive-disclosure reference is dangling, so the promised mocking strategies, replay patterns, and setup guidance are unreachable.

Add an explicitly ordered testing workflow with validation checkpoints (e.g., 1. write test with time-skipping fixture → 2. run and assert → 3. mock activities for integration cases → 4. replay production histories before deploy) instead of distributing the approach across Philosophy, Quick Start, and Coverage sections.

Trim the tautological 'Do not use this skill when' bullets and the generic 'Instructions' boilerplate, and state the ≥80% coverage target and time-skipping benefit once instead of repeating them across three sections.

DimensionReasoningScore

Conciseness

Mostly efficient (Testing Philosophy, Quick Start, resource listings are tight), but it includes unnecessary padding: the tautological 'Do not use this skill when' bullets ('The task is unrelated to temporal python testing strategies'), generic boilerplate Instructions ('Clarify goals, constraints, and required inputs'), and repetition of the ≥80% coverage target across three sections and the time-skipping benefit across two.

3 / 5

Actionability

The Quick Start provides structurally complete, executable pytest code (WorkflowEnvironment.start_time_skipping fixture, Worker context, execute_workflow with assert; ActivityEnvironment example), which meets 'mostly executable guidance with minor gaps'. It falls short of 5 because of placeholders (YourWorkflow, args, expected), no pytest-asyncio configuration shown, and mocking/error-injection guidance being entirely deferred to resource files.

4 / 5

Workflow Clarity

A rough approach is implied (Testing Philosophy list plus Quick Start code) but the testing workflow (write test → run with time-skipping → mock activities → replay before deploy) is distributed across sections rather than explicitly sequenced, and validation checkpoints are implicit in asserts only. Not 2 because structure and a rough sequence are present; not 4 because no explicit checkpoints or ordered steps are given.

3 / 5

Progressive Disclosure

The body references 'resources/unit-testing.md', 'resources/integration-testing.md', 'resources/replay-testing.md', and 'resources/local-setup.md', but none of these files exist in the bundle (no resources/ directory), so every reference is dangling and the promised detail is unreachable. The per-resource signaling format (File/When to load/Contains) is good, but scored against the actual bundle structure the navigation is broken, which fits 'minimal structure / references buried' better than the clearly-signaled anchors at 4-5.

2 / 5

Total

12

/

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.

The description clearly and explicitly states what the skill does and when to use it, with a specific framework niche (Temporal), natural trigger terms, and third-person voice. Only minor gaps in action concreteness and synonym coverage keep specificity and trigger term quality at 4.

DimensionReasoningScore

Specificity

'Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup' lists several specific capabilities with only minor gaps. Not 5 because the actions are category labels rather than fully concrete operations (e.g., 'mocking strategies' rather than mocking activities); not 3 because coverage goes well beyond 1-2 actions.

4 / 5

Completeness

Both parts are explicit: the what ('Test Temporal workflows with pytest, time-skipping, and mocking strategies...') and the when ('Use when implementing Temporal workflow tests or debugging test failures') with concrete trigger phrases, matching the 5-anchor pattern. It is not 4 because the when-clause is already explicit and specific, not merely present-but-imprecise.

5 / 5

Trigger Term Quality

Natural terms users would say are present: 'Temporal workflows', 'pytest', 'unit testing', 'integration testing', 'replay testing', 'debugging test failures'. A few natural variations are missing (e.g., 'mock activities', 'test coverage', 'CI'), so it fits 'good keyword coverage; a few natural terms missing' rather than comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

'Temporal' explicitly scopes the skill to a specific workflow framework with distinct triggers ('Temporal workflow tests'), giving it a clear niche with minimal conflict risk against general Python-testing skills. It is not 4 because no meaningful overlap with a closely related skill is identifiable from what is stated.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/temporal-python-testing/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.