CtrlK
BlogDocsLog inGet started
Tessl Logo

temporal-developer

Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust. 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. Also use when the user mentions "run a Temporal workflow from the CLI", "start a dev server", "run temporal server start-dev", "temporal workflow start", "temporal workflow execute", "temporal workflow signal", "temporal workflow query", "temporal workflow update".

84

1.90x
Quality

Does it follow best practices?

Impact

97%

1.90x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The body is a well-organized overview that practices strong progressive disclosure with real, clearly-labeled reference files. It is weaker on actionability and workflow clarity, leaning on reference pointers and prose explanation rather than inline executable steps or validation checkpoints.

Suggestions

Add a brief inline quick-start code/command snippet (e.g. a minimal worker definition or a start-dev command) so the body is actionable before requiring reference reads.

Tighten the Core Architecture prose to skip durable-execution concepts Claude already knows and keep only Temporal-specific detail.

Add explicit validation/checkpoint steps for risky workflows (e.g. verifying determinism after edits, or confirming a dev server is reachable) to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

Mostly efficient with well-organized sections, but prose like the Architecture overview explains durable-execution concepts Claude largely already knows, and could be tightened toward the lean score-3 anchor.

2 / 3

Actionability

Provides some concrete signals ("temporal server start-dev", the Command/Event table) but most guidance is directive pointers ("read references/python/python.md") rather than inline executable code, falling at the score-2 incomplete-guidance anchor.

2 / 3

Workflow Clarity

The "Read All Relevant References" section gives a numbered sequence, but there are no validation checkpoints or feedback loops and ordering beyond language selection is implicit, matching the score-2 sequence-without-checkpoints anchor.

2 / 3

Progressive Disclosure

A concise overview points to clearly signaled one-level-deep references (e.g. "references/core/determinism.md", "references/python/python.md"), all verified to exist in the bundle, matching the score-3 well-structured-navigation anchor.

3 / 3

Total

9

/

12

Passed

Description

100%

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, comprehensive, and rich in natural trigger terms, with explicit "Use when..." guidance and a clearly distinct Temporal niche. It uses third-person voice and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("Develop, debug, and manage" workflows, activities, workers) and enumerates seven specific SDKs, mirroring the score-3 anchor of several specific concrete actions.

3 / 3

Completeness

Explicitly answers what (develop/debug/manage Temporal apps) and when (two "Use when..." clauses with explicit triggers), matching the score-3 anchor for clearly answering both what AND when.

3 / 3

Trigger Term Quality

Captures natural user phrasings ("non-determinism errors", "stuck workflows", "activity retries") plus concrete CLI invocations ("temporal workflow start", "temporal server start-dev"), giving broad coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

The Temporal/durable-execution niche is sharply defined with distinct triggers unlikely to fire for unrelated skills, matching the score-3 clear-niche anchor.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

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

Warning

Total

14

/

16

Passed

Repository
temporalio/skill-temporal-developer
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.