Name: temporal-python-testing
Rating: 50.4 (1 reviews)
Author: administrakt0r

temporal-python-testing

Comprehensive testing approaches for Temporal workflows using pytest, progressive disclosure resources for specific testing scenarios.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/temporal-python-testing/SKILL.md

The canonical home for this skill is temporal-python-testing in administrakt0r/AI-Agents-Safe-Coding-Skills

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 is well-sectioned with executable code and a clear resource-navigation scheme, but it suffers from repeated content across sections, vague high-level instructions, and progressive-disclosure references that point to non-existent files.

Suggestions

Create the referenced resource files (resources/unit-testing.md, integration-testing.md, replay-testing.md, local-setup.md, implementation-playbook.md) or remove the dangling references.

Consolidate the repeated testing-philosophy and coverage points into a single section to remove padding across 'Testing Philosophy', 'Coverage Targets', and 'Key Testing Principles'.

Replace the generic 'Instructions' list with a concrete sequenced workflow with validation checkpoints (e.g. write test -> run with time-skipping -> assert -> replay against production history before deploy).

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete code, but the same points (time-skipping, mock activities, replay, >=80% coverage) are repeated across 'Use this skill when', 'Testing Philosophy', 'Three Test Types', 'Coverage Targets', and 'Key Testing Principles', which is noticeable padding that could be consolidated.	3 / 5
Actionability	Provides two copy-paste-ready code blocks (WorkflowEnvironment fixture with time-skipping, ActivityEnvironment run) with real imports; minor gaps only in that workflow/activity identifiers are placeholders (YourWorkflow, your_activity, args).	4 / 5
Workflow Clarity	The 'Instructions' section is vague ('Apply relevant best practices and validate outcomes') and there is no sequenced multi-step workflow with explicit validation checkpoints; the 'How to Use Resources' trigger-to-file mapping is clear but checkpoints are only implicit.	3 / 5
Progressive Disclosure	References to resources/*.md files are clearly signaled with 'When to load' and 'Contains' metadata and are one level deep, but no references/ or resources/ bundle directory actually exists, so every linked file is a dangling reference rather than real navigable content.	3 / 5
	Total	13 / 20 Passed

Description

53%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 states a clear domain and tool but stops at a generic action and omits any 'Use when' trigger guidance, leaving its activation cues implicit. The meta-phrase about progressive disclosure adds little capability information.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when testing Temporal Python workflows, mocking activities, time-skipping tests, or replay-testing workflow determinism.'

Replace 'Comprehensive testing approaches' with specific actions like 'Write unit, integration, and replay tests for Temporal workflows using pytest.'

Drop the 'progressive disclosure resources...' phrase from the description; it describes the skill's file structure rather than a capability.

Dimension	Reasoning	Score
Specificity	Names the domain ('Temporal workflows using pytest') and one concrete action ('testing approaches'), but 'comprehensive testing approaches' is generic and the 'progressive disclosure resources' phrase is meta-description of skill structure rather than a capability.	3 / 5
Completeness	Has a clear 'what' (testing approaches for Temporal workflows with pytest) but no 'Use when...' clause or equivalent explicit trigger guidance; per the rubric a missing 'when' caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant keywords ('Temporal workflows', 'pytest', 'testing') are present and natural, but common variations users say like 'Temporal Python SDK', 'time-skipping', 'workflow replay', or 'test Temporal activities' are missing.	3 / 5
Distinctiveness Conflict Risk	'Temporal workflows using pytest' is a fairly specific niche unlikely to trigger for unrelated skills; minor overlap risk only with closely related testing skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/temporal-python-testing/SKILL.md
Commit: debb2ec

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.