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.
83
78%
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 ./tests/ext_conformance/artifacts/agents-wshobson/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 concrete capabilities (pytest, time-skipping, mocking, multiple testing types), and provides explicit trigger guidance. The description is concise, uses third-person voice, and contains 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', 'test failures', 'local development setup'. These cover the terms a developer working with Temporal would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of 'Temporal workflows' with specific testing strategies (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
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured for progressive disclosure, with clear pointers to detailed resources. However, the main body is somewhat redundant (repeating key points across multiple sections) and leans more descriptive than actionable—the Quick Start code is helpful but the rest is mostly organizational scaffolding. Adding more concrete, executable guidance in the main body and eliminating repeated content would significantly improve it.
Suggestions
Remove redundant sections: 'Key Testing Principles' largely duplicates 'Testing Philosophy', and 'How to Use Resources' restates 'Available Resources'—consolidate these to save tokens.
Add a concrete sequenced workflow section (e.g., 'First run unit tests, then integration tests, verify coverage with `pytest --cov`, then run replay tests before deployment') with explicit validation checkpoints.
Include a concrete mocking example in the Quick Start (e.g., a minimal activity mock pattern) since mocking is a core use case mentioned repeatedly but never demonstrated.
| 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 summaries that could be more terse. The 'How to Use Resources' section 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, much of the skill is descriptive rather than instructive—it tells you what the resource files contain rather than providing concrete, actionable guidance directly. The main body lacks specific commands for setup, mocking patterns, or error handling. | 2 / 3 |
Workflow Clarity | The skill identifies three test types and provides a testing philosophy, but lacks a clear sequenced workflow for how to approach testing a Temporal project end-to-end. There are no validation checkpoints or feedback loops (e.g., what to do when tests fail, how to debug determinism issues). The progression from unit → integration → replay is implied but not explicitly sequenced with verification steps. | 2 / 3 |
Progressive Disclosure | This is the skill's strongest dimension. It provides a clear overview with well-signaled, one-level-deep references to four specific resource files. Each resource is clearly described with when to load it and what it contains, making navigation straightforward. | 3 / 3 |
Total | 9 / 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
- Dicklesworthstone/pi_agent_rust
- Commit
6e3d68c
- 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.