CtrlK
BlogDocsLog inGet started
Tessl Logo

temporal-python-pro

Master Temporal workflow orchestration with Python SDK. Implements durable workflows, saga patterns, and distributed transactions. Covers async/await, testing strategies, and production deployment.

35

Quality

31%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

17%Scale 1-5

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

This skill reads like a comprehensive but generic reference document or knowledge dump about Temporal Python SDK rather than an actionable skill for Claude. It is severely verbose, explaining concepts Claude already knows, while paradoxically lacking any concrete code examples. The absence of executable code, clear workflows with validation steps, and proper content organization across files makes it poorly suited as a skill file.

Suggestions

Replace the extensive bullet-point descriptions with 3-5 concrete, executable code examples covering the most common patterns (workflow definition, activity implementation, worker startup, testing with time-skipping).

Add a clear step-by-step workflow for implementing a Temporal workflow from scratch, with explicit validation checkpoints (e.g., 'Run replay test to verify determinism before deploying').

Remove sections that explain what Temporal is, its benefits, and ideal scenarios — Claude already knows these. Focus only on Python SDK-specific implementation details and gotchas.

Move detailed reference content (error handling taxonomy, timeout types, serialization patterns) into a separate bundle file like 'resources/implementation-playbook.md' and ensure that file actually exists in the bundle.

DimensionReasoningScore

Conciseness

Extremely verbose at ~350+ lines, mostly listing concepts and categories Claude already knows. Extensive sections like 'Capabilities', 'When to Use Temporal Python', 'Key Benefits', and 'Common Pitfalls' read like documentation summaries rather than actionable skill instructions. The content explains what Temporal is and why to use it rather than providing concise, novel guidance.

1 / 5

Actionability

Despite the length, there is almost no executable code anywhere in the skill. It lists decorators and patterns by name (e.g., '@workflow.defn', 'ThreadPoolExecutor') but never provides a concrete, copy-paste-ready code example. The guidance remains at the level of bullet-point descriptions rather than executable instructions.

2 / 5

Workflow Clarity

There is no clear multi-step workflow with sequenced steps and validation checkpoints. The 'Instructions' section is four generic bullets. Best practices are listed as numbered items but lack concrete sequencing, validation gates, or feedback loops for error recovery in what is inherently a complex, multi-step domain.

2 / 5

Progressive Disclosure

The skill references 'resources/implementation-playbook.md' but no bundle files are provided, making this a dead reference. The massive amount of content is inlined as a monolithic wall of categorized bullet points with no meaningful splitting into separate files. External URLs to docs.temporal.io are listed but don't substitute for proper bundle structure.

2 / 5

Total

7

/

20

Passed

Description

45%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 identifies a clear domain (Temporal with Python SDK) and lists relevant concepts, giving it reasonable distinctiveness. However, it lacks a 'Use when...' clause, uses the imperative 'Master' voice which is unusual, and lists topics rather than concrete actions Claude can perform. The trigger terms are decent but miss common user vocabulary around Temporal specifics.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'Use when the user asks about Temporal workflows, durable execution, saga patterns, or building distributed systems with Temporal Python SDK'.

Replace topic-listing language ('Covers async/await, testing strategies') with concrete action verbs describing what the skill enables Claude to do, e.g., 'Generates Temporal workflow and activity definitions, implements saga patterns for distributed transactions, writes workflow tests using Temporal's test framework'.

Include additional natural trigger terms users might say, such as 'Temporal.io', 'task queue', 'worker', 'activity', 'retry policy', and 'workflow execution'.

DimensionReasoningScore

Specificity

Names the domain (Temporal workflow orchestration with Python SDK) and lists several concepts (durable workflows, saga patterns, distributed transactions, async/await, testing strategies, production deployment), but these read more like topic areas than concrete actions. 'Implements' is the only action verb, and the rest are covered by the vague 'Covers'.

3 / 5

Completeness

The description addresses 'what' (implements workflows, saga patterns, etc.) but has no 'when' clause at all. There is no explicit trigger guidance or 'Use when...' statement, which per the rubric should cap completeness at 3, and the 'what' itself is more of a topic list than a clear capability statement, bringing it to 2.

2 / 5

Trigger Term Quality

Includes relevant keywords like 'Temporal', 'workflow', 'Python SDK', 'saga patterns', 'distributed transactions', and 'async/await'. However, it misses natural user phrases like 'Temporal.io', 'activity', 'worker', 'retry policy', 'task queue', or 'workflow definition' that users would commonly mention.

3 / 5

Distinctiveness Conflict Risk

The mention of 'Temporal' and 'Python SDK' together creates a fairly distinct niche. There's minor overlap risk with general Python workflow or distributed systems skills, but the Temporal-specific terminology makes it mostly distinguishable.

4 / 5

Total

12

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.