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.
81
75%
Does it follow best practices?
Impact
87%
1.12xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/backend-development/skills/temporal-python-testing/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies its domain (Temporal workflow testing), lists specific capabilities and testing strategies, and provides explicit trigger guidance. It uses proper third-person voice and includes natural keywords that developers would use when seeking help with Temporal testing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Test Temporal workflows with pytest, time-skipping, and mocking strategies' and enumerates specific testing types: 'unit testing, integration testing, replay testing, and local development setup.' | 3 / 3 |
Completeness | Clearly answers both 'what' (test Temporal workflows with pytest, time-skipping, mocking, covering unit/integration/replay testing and local dev setup) and 'when' (explicit 'Use when implementing Temporal workflow tests or debugging test failures'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Temporal workflows', 'pytest', 'time-skipping', 'mocking', 'unit testing', 'integration testing', 'replay testing', 'workflow tests', 'test failures', 'local development setup'. These cover a good range of terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of 'Temporal workflows' with specific testing strategies (pytest, time-skipping, replay testing) creates a clear niche that is unlikely to conflict with general testing skills or other workflow engine skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable overview of Temporal Python testing with clear organization and some executable code examples. Its main weakness is heavy reliance on resource files that don't exist in the bundle, making much of the actionable content inaccessible. There is also notable redundancy across sections (Testing Philosophy, Key Testing Principles, and How to Use Resources overlap significantly).
Suggestions
Eliminate redundant sections: merge 'Key Testing Principles' into 'Testing Philosophy' and remove the 'How to Use Resources' section since the 'Available Resources' section already provides this mapping.
Either provide the referenced resource files (resources/unit-testing.md, etc.) or inline the most critical patterns directly in the skill body so it's actionable without external files.
Add a troubleshooting/validation workflow: what to check when tests fail, common determinism errors, and how to debug time-skipping issues.
Make code examples more concrete — replace 'YourWorkflow' and 'your_activity' with a minimal but realistic example (e.g., a simple order processing workflow) to make the Quick Start truly copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some redundancy — the 'Key Testing Principles' section largely repeats information from 'Testing Philosophy', and the resource descriptions repeat content listings that could be more terse. The 'How to Use Resources' section at the bottom restates what's already clear from the 'Available Resources' section. However, it's not egregiously verbose. | 2 / 3 |
Actionability | The Quick Start Guide provides executable code examples for basic workflow and activity tests, which is good. However, the bulk of the skill defers to resource files that are not provided, meaning most concrete guidance is promised but not delivered in the skill itself. The code examples are functional but generic (YourWorkflow, your_activity placeholders). | 2 / 3 |
Workflow Clarity | The skill outlines three test types and a testing philosophy with a clear progression, and the Quick Start shows a basic test workflow. However, there are no explicit validation checkpoints, error recovery steps, or feedback loops for the testing process itself (e.g., what to do when tests fail, how to debug determinism issues). | 2 / 3 |
Progressive Disclosure | The skill clearly signals four resource files with descriptions of when to load each and what they contain, which is good structure. However, no bundle files are provided, so the referenced resources don't actually exist, making the progressive disclosure structure aspirational rather than functional. The main file also contains some content that could be trimmed given the resource structure. | 2 / 3 |
Total | 8 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
112197c
- 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.