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:Dicklesworthstone/pi_agent_rust --skill temporal-python-testing88
Quality
86%
Does it follow best practices?
Impact
87%
1.12xAverage score across 3 eval scenarios
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 (pytest, time-skipping, mocking, multiple test types), includes natural trigger terms developers would use, explicitly states both capabilities and usage triggers, and carves out a distinct niche around Temporal workflow testing that won't conflict with 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', 'unit testing', 'integration testing', 'replay testing', 'test failures', 'mocking' - these are terms developers naturally use when working with Temporal testing. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting 'Temporal workflows' testing specifically - unlikely to conflict with general testing skills or other workflow tools due to explicit Temporal focus and specific testing methodologies mentioned. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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 lack of explicit validation/debugging workflows when tests fail. 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 or validation steps for common test failure scenarios (e.g., determinism errors, timeout issues)
| 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, copy-paste ready code examples for both workflow and activity testing with proper pytest fixtures, imports, and async patterns. The Quick Start Guide gives concrete, working code. | 3 / 3 |
Workflow Clarity | The testing philosophy and three test types are clearly explained, but there's no explicit validation/verification workflow for the testing process itself. Missing 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
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.
- 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.