CtrlK
BlogDocsLog inGet started
Tessl Logo

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

1.12x
Quality

75%

Does it follow best practices?

Impact

87%

1.12x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/backend-development/skills/temporal-python-testing/SKILL.md

The canonical home for this skill is temporal-python-testing in wshobson/agents

SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body offers executable quick-start examples and a clean test-type taxonomy, but it is padded with redundant principle restatements and, critically, points to four resource files that are not present in the bundle.

Suggestions

Provide the referenced resources/*.md files (unit-testing, integration-testing, replay-testing, local-setup) so the progressive-disclosure structure resolves, or inline the key guidance and drop the dead references.

Consolidate the redundant 'Testing Philosophy', 'Key Testing Principles', and 'Coverage Targets' sections — the ≥80% target and time-skipping benefit are each stated multiple times.

Add a short checkpointed workflow for choosing and running a test (e.g., pick test type → write test → run pytest → assert/fix), so the sequencing is explicit rather than implied by the routing table.

DimensionReasoningScore

Conciseness

Mostly efficient with useful code, but 'Testing Philosophy', 'Key Testing Principles', 'Coverage Targets', and 'How to Use Resources' largely restate the 'When to Use' list and resource descriptions (e.g., the ≥80% coverage target appears three times), adding padding.

3 / 5

Actionability

Two complete, executable code blocks with real imports (WorkflowEnvironment, ActivityEnvironment) are copy-paste ready; minor gaps remain via placeholders (YourWorkflow, your_activity, expected) and detail deferred to resource files.

4 / 5

Workflow Clarity

Content is organized by test type with a clear need→file decision table, but there is no checkpointed multi-step sequence with validation loops; the guidance is a routing map rather than an explicit workflow.

3 / 5

Progressive Disclosure

The body signals four one-level-deep references (resources/*.md) with clear 'When to load' and 'Contains' annotations, but the referenced files do not exist (no resources/ directory or bundle files), so the well-signaled structure points to non-resolving targets.

3 / 5

Total

13

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinct, clearly stating both capabilities and explicit 'Use when' trigger guidance in third-person voice. Its only gap is slightly limited synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete strategies — 'Test Temporal workflows with pytest, time-skipping, and mocking strategies' plus 'unit testing, integration testing, replay testing, and local development setup' — giving comprehensive coverage of specific actions.

5 / 5

Completeness

Explicitly answers both what ('Test Temporal workflows with pytest, time-skipping, and mocking strategies; covers unit/integration/replay/local setup') and when ('Use when implementing Temporal workflow tests or debugging test failures') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms a user would say ('Temporal workflows', 'pytest', 'workflow tests', 'debugging test failures') but misses some synonyms like 'Temporal SDK', 'worker tests', or 'activity tests'.

4 / 5

Distinctiveness Conflict Risk

'Temporal workflows with pytest' is a clear niche with distinct triggers and minimal overlap risk with other skills, since the Temporal-specific scope is unambiguous.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Dicklesworthstone/pi_agent_rust
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.