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 capabilities and testing strategies, and provides explicit trigger guidance. It uses third-person voice correctly 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', '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) and 'pytest' creates a very clear niche that is unlikely to conflict with general testing or general workflow 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 excels at progressive disclosure with well-organized references to detailed resource files, and provides useful executable quick-start examples. However, it suffers from redundancy across sections (testing principles repeated in multiple places) and defers too much actionable content to resource files, leaving the main skill somewhat descriptive. The workflow for how to approach testing lacks explicit sequencing and validation checkpoints.
Suggestions
Remove redundant sections - consolidate 'Key Testing Principles', 'Testing Philosophy', and 'Coverage Targets' into a single concise section to reduce repetition
Add a concrete sequenced workflow for setting up and running tests (e.g., '1. Set up environment → 2. Write unit tests → 3. Run and validate coverage → 4. Add integration tests → 5. Run replay tests before deploy') with explicit validation checkpoints
Include at least one concrete mocking example in the main skill (e.g., a minimal activity mock pattern) rather than deferring all mocking guidance to resource files
| 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, the bulk of the skill is descriptive rather than instructive - it tells you what the resource files contain rather than providing concrete, actionable guidance directly. The actual testing patterns, mocking strategies, and replay testing are deferred entirely to resource files. | 2 / 3 |
Workflow Clarity | The skill identifies three test types and provides a testing philosophy, but lacks explicit sequencing for multi-step testing workflows. There are no validation checkpoints (e.g., 'run unit tests before integration tests', 'validate replay tests pass before deploying'). The CI/CD integration is mentioned but entirely deferred to a resource file with no concrete steps. | 2 / 3 |
Progressive Disclosure | This is the skill's strongest dimension. It provides a clear overview with well-organized, one-level-deep references to four specific resource files. Each resource is clearly signaled with when-to-load guidance, file paths, and content summaries. The 'How to Use Resources' section provides clear navigation patterns. | 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
47823e3
- 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.