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.
Install with Tessl CLI
npx tessl i github:wshobson/agents --skill temporal-python-testingOverall
score
86%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 87%
↑ 1.12xAgent success when using this skill
Validation for skill structure
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 well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms users would actually use, explicitly states both what the skill does and when to use it, and targets a clear niche (Temporal workflow testing) that distinguishes it from general testing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Test Temporal workflows with pytest, time-skipping, and mocking strategies' and explicitly covers 'unit testing, integration testing, replay testing, and local development setup'. | 3 / 3 |
Completeness | Clearly 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'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Temporal workflows', 'pytest', 'time-skipping', 'mocking', 'unit testing', 'integration testing', 'replay testing', 'test failures', 'local development setup'. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Temporal workflows specifically, with distinct triggers like 'Temporal', 'replay testing', 'time-skipping' that are unlikely to conflict with general testing or other workflow skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent progressive disclosure and actionable code examples. The main weaknesses are some verbosity in meta-sections (when to use, how to use resources) and missing workflow clarity around test debugging/iteration cycles. The core technical content is solid and immediately usable.
Suggestions
Remove or condense the 'When to Use This Skill' and 'How to Use Resources' sections - the resource descriptions already make usage clear
Add a brief troubleshooting section with common test failure patterns and debugging steps to improve workflow clarity
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanation like the 'When to Use This Skill' section listing obvious use cases, and the 'How to Use Resources' section that restates what's already clear from the resource descriptions. | 2 / 3 |
Actionability | Provides fully executable pytest code examples for both workflow and activity testing that are copy-paste ready. The code includes proper fixtures, async patterns, and complete test structure. | 3 / 3 |
Workflow Clarity | The skill describes testing types and philosophy but lacks explicit validation checkpoints or feedback loops for the testing process itself. No guidance on what to do when tests fail or how to iterate on test failures. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview and well-signaled one-level-deep references to specific resource files. Each resource is clearly described with 'When to load' guidance and content summaries, making navigation easy. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- 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.