CtrlK
BlogDocsLog inGet started
Tessl Logo

temporal-developer

Develop, debug, and manage Temporal applications across Python, TypeScript, Go, and Java. Use when the user is building workflows, activities, or workers with a Temporal SDK, debugging issues like non-determinism errors, stuck workflows, or activity retries, using Temporal CLI, Temporal Server, or Temporal Cloud, or working with durable execution concepts like signals, queries, heartbeats, versioning, continue-as-new, child workflows, or saga patterns.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/temporal/skills/temporal-developer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-3

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

A well-structured overview with excellent progressive disclosure and a clear reference architecture, but the body leans on pointers for the core actionable guidance and could tighten concept restatements. Adding an inline minimal executable example and a post-install verification checkpoint would lift the lower dimensions.

Suggestions

Tighten the 'Core Architecture' and 'History Replay' sections by moving the Command/Event table and replay mechanics to references/core/determinism.md, keeping only the essential pointer in the body.

Add a minimal inline executable snippet (e.g., starting a dev server and a tiny workflow) so the body offers copy-paste-ready actionability rather than only reference pointers.

Add a verification step after the CLI install sequence (e.g., run `temporal --version` to confirm the install) to give Getting Started an explicit validation checkpoint.

DimensionReasoningScore

Conciseness

The body is largely lean and does not over-explain Temporal basics, but the 'Core Architecture' and 'History Replay' sections restate durable-execution/replay concepts and a Command/Event table that an expert Claude largely knows and that also live in references/core/determinism.md; this could be tightened.

2 / 3

Actionability

Provides concrete per-OS CLI install commands and explicit reference navigation, but core development/debugging guidance is deferred entirely to references with no inline executable workflow example, so the body instructs mainly via pointers rather than copy-paste-ready code.

2 / 3

Workflow Clarity

Getting Started and 'Read All Relevant References' give a clear ordered sequence, but there is no validation checkpoint or feedback loop (e.g., verifying `temporal` runs after install, or confirming a workflow is healthy), leaving checkpoints implicit.

2 / 3

Progressive Disclosure

The body is a concise overview pointing to a well-organized one-level-deep reference tree (core/ plus per-language), with every referenced path verified to exist and clearly signaled in a Primary References list with language cross-links.

3 / 3

Total

9

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

A strong, specific, third-person description that clearly states both capabilities and explicit 'Use when' triggers across a well-defined domain. Trigger term coverage and distinctiveness are excellent.

DimensionReasoningScore

Specificity

Lists multiple concrete actions such as 'Develop, debug, and manage Temporal applications' and 'building workflows, activities, or workers with a Temporal SDK', matching the top anchor for specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Develop, debug, and manage Temporal applications across Python, TypeScript, Go, and Java') and when via a clear 'Use when the user is building...' clause with multiple trigger scenarios.

3 / 3

Trigger Term Quality

Includes natural user-facing terms across the domain — 'non-determinism errors, stuck workflows, or activity retries' and 'signals, queries, heartbeats, versioning, continue-as-new' — giving good coverage of phrasing users would actually say.

3 / 3

Distinctiveness Conflict Risk

The named 'Temporal' platform with distinctive triggers (Temporal SDK, durable execution, saga patterns, continue-as-new) carves a clear niche that is unlikely to conflict with other skills.

3 / 3

Total

12

/

12

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

referenced_paths_exist

Referenced path issues: 14 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
openai/plugins
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.