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

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/temporal-python-testing/SKILL.md

Quality

Content

50%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 provides solid executable quick-start examples and a clear resource map, but it is weakened by redundant boilerplate sections, the absence of an explicit validated workflow, and dead progressive-disclosure references to missing bundle files.

Suggestions

Remove the generic "Instructions" boilerplate and the low-value "Do not use this skill when" / "Key Testing Principles" sections, which restate content already covered elsewhere, to tighten token efficiency.

Add an explicit step-by-step testing workflow with validation checkpoints (e.g., choose test type -> set up environment -> write test -> run pytest -> interpret failure output), rather than only topical sections.

Provide the referenced resources/*.md bundle files, or remove the dead references, since the "Available Resources" section points to files that are not present in the skill bundle.

Dimension	Reasoning	Score
Conciseness	Several padded/redundant sections add little: the generic "Instructions" boilerplate ("Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes."), "Do not use this skill when", the "Key Testing Principles" rehash of the Testing Philosophy, and "How to Use Resources" which repeats the "Available Resources" file mappings.	2 / 5
Actionability	Two concrete, mostly copy-paste-ready code examples (a full WorkflowEnvironment fixture + Worker execute_workflow test, and an ActivityEnvironment test) plus explicit coverage targets give executable guidance; gaps are the placeholder symbols (YourWorkflow, your_activity, args) and the detailed integration/replay guidance existing only as bullet teasers.	4 / 5
Workflow Clarity	The content is organized topically (philosophy, test types, quick start, coverage) with an implied rough order, but there is no explicit sequenced testing workflow and validation checkpoints are only vaguely implied by the generic "validate outcomes" boilerplate.	3 / 5
Progressive Disclosure	The "Available Resources" section clearly signals one-level-deep references with per-file 'When to load' and 'Contains' annotations, but the referenced files (resources/unit-testing.md, integration-testing.md, replay-testing.md, local-setup.md) do not exist in the bundle, so the progressive disclosure is promised but not delivered.	3 / 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 is strong: it concisely states concrete capabilities, uses an explicit 'Use when' trigger clause with natural terms, and carves out a distinct Temporal-testing niche. Minor gains are possible by broadening the trigger-term synonyms and distinguishing the testing actions more sharply.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete testing approaches ("unit testing, integration testing, replay testing, and local development setup") plus tools (pytest, time-skipping, mocking), but the actions all collapse into variants of "testing" rather than distinct operations, leaving minor coverage gaps versus a fully comprehensive action list.	4 / 5
Completeness	Explicitly answers both what ("Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup.") and when ("Use when implementing Temporal workflow tests or debugging test failures.") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ("Temporal workflow tests", "debugging test failures", "pytest", "time-skipping") with good coverage, but a few natural variations (e.g. "mock activities", "replay/determinism") are absent from the description.	4 / 5
Distinctiveness Conflict Risk	The Temporal + pytest + workflow-testing niche is clearly scoped with distinct triggers, creating minimal conflict risk with other skills; the domain qualifier strongly narrows activation.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: 3eff4af

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.