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. Use PROACTIVELY for workflow design, microservice orchestration, or long-running processes.

49

Quality

53%

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 ./skills/temporal-python-pro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

28%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 reads as a verbose reference catalog of Temporal/Python capabilities rather than actionable guidance: no executable code, no sequenced workflow with validation, and inlined content that should be split into bundle files. Structure exists but progressive disclosure and actionability are weak.

Suggestions

Replace the bullet capability catalogs with a small set of executable code snippets (worker startup, a @workflow.defn example, a RetryPolicy/timeout config) so guidance is copy-paste ready.

Collapse the long enumerated lists into concise pointers and move detailed capability reference material into separate files under references/ (e.g., patterns.md, testing.md, deployment.md), linked one level deep from SKILL.md.

Add a concrete sequenced workflow with validation checkpoints (e.g., write workflow -> run time-skipping test -> replay against history -> deploy with graceful shutdown) instead of the generic 'Instructions' list.

DimensionReasoningScore

Conciseness

The ~360-line body is a wall of capability bullet lists enumerating concepts largely known to Claude (e.g., 'Worker initialization with proper task queue configuration', 'Graceful shutdown and resource cleanup') with no executable code, making it noticeably verbose and padded.

2 / 5

Actionability

While it names real API symbols (@workflow.defn, workflow.now(), RetryPolicy fields, timeout names), it gives only high-level hints with no executable code or concrete end-to-end steps, so guidance is minimal rather than copy-paste ready.

2 / 5

Workflow Clarity

There is no coherent multi-step workflow; the 'Instructions' section is generic ('Clarify goals, constraints, and required inputs') and the numbered Best Practices lists lack validation checkpoints or feedback loops for destructive/batch workflow operations.

2 / 5

Progressive Disclosure

Section headers provide some structure and external doc URLs are listed under Resources, but the bulk of capability reference material is inlined in SKILL.md with no bundle files to split it into one-level-deep references.

3 / 5

Total

9

/

20

Passed

Description

78%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, distinct, and answers both what and when with concrete trigger phrases. It is slightly above the midpoint across most dimensions, held back only by trigger-phrase exhaustiveness and 'when' explicitness.

DimensionReasoningScore

Specificity

Lists several specific capability areas ('Implements durable workflows, saga patterns, and distributed transactions', 'Covers async/await, testing strategies, and production deployment') rather than vague language, though they describe domains more than granular concrete actions, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both 'what' (durable workflows, saga patterns, distributed transactions, testing, deployment) and 'when' ('Use PROACTIVELY for workflow design, microservice orchestration, or long-running processes'), but the 'when' could be more explicit with concrete user-mention triggers.

4 / 5

Trigger Term Quality

Provides natural trigger phrases ('workflow design, microservice orchestration, or long-running processes') a user would plausibly say, with good keyword coverage, though a few common synonyms or variations are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear, narrow niche (Temporal workflow orchestration with the Python SDK) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
rmyndharis/antigravity-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.