CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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, workers, or background job queues 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".

89

1.61x
Quality

91%

Does it follow best practices?

Impact

84%

1.61x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A well-structured router skill: the body indexes a large reference bundle with clear navigation, task-based routing instructions, and genuinely valuable disambiguation guidance (job-queue vs. task-queue vocabulary, out-of-scope routing to sibling skills). Main improvement area is trimming the Core Architecture section, which explains Temporal concepts Claude already knows.

DimensionReasoningScore

Conciseness

The body is an efficient router/index: sections are compact, there is no filler, and the job-queue disambiguation guidance is high-value and non-obvious. It falls short of 5 because the Core Architecture section (~20 lines) re-explains concepts Claude already knows (cluster, workers polling task queues, dev vs. production fleet sizing) that could be trimmed or delegated to a reference.

4 / 5

Actionability

As an instruction-only skill, its guidance is fully actionable: an explicit per-language mapping to SDK guides, a concrete pre-flight check ('check whether `temporal` is installed before using it. If it is missing, follow the [Temporal CLI installation guide]'), the exact dev-server command (`temporal server start-dev`), and a direct directive for job-queue requests ('build it with a Standalone Activity — not a Workflow wrapping a single Activity, and not a dispatcher Workflow'). Common task categories each route to a specific, verified file.

5 / 5

Workflow Clarity

'Choose References for the Task' gives a clear, ordered decision process (identify language and task → read core reference plus language counterpart → load extras only as needed; new projects → SDK guide; CLI tasks → check installation first). It lacks the explicit validation checkpoints and error-recovery feedback loops of the 5 anchor, though no destructive or batch operations are present, so the validation cap does not apply.

4 / 5

Progressive Disclosure

The body is a lean overview with well-signaled, verified, one-level-deep references: every cited path (core guides, per-language counterparts via `references/{your_language}/...`, SDK guides, integrations catalog) exists on disk, the deep link anchor is real, and language-specific counterparts are systematically listed. Content is appropriately split and navigation is easy; the integrations catalog's second hop is a deliberate index pattern, not buried instructions.

5 / 5

Total

18

/

20

Passed

Description

95%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.

A strong description: it explicitly states what the skill does, enumerates seven SDK languages, and provides a rich, natural set of when-triggers including exact CLI commands users would type. Third-person voice is used throughout and there is no fluff or over-claiming.

DimensionReasoningScore

Specificity

Concrete actions are named ('Develop, debug, and manage Temporal applications') along with specific failure modes ('non-determinism errors, stuck workflows, or activity retries') and enumerated durable-execution concepts, giving several specific capabilities. It falls just short of the 5 anchor because the top-line action verbs (develop/debug/manage) are relatively high-level, and the most concrete specifics serve as triggers rather than distinct capability descriptions.

4 / 5

Completeness

Both questions are answered explicitly: the 'what' ('Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust') and a detailed 'when' with two explicit trigger clauses ('Use when the user is building... debugging... using... or working with...' and 'Also use when the user mentions...'), matching the top anchor exactly.

5 / 5

Trigger Term Quality

Comprehensive natural-language coverage including synonyms and exact commands: 'building workflows, activities, workers, or background job queues', 'stuck workflows', 'signals, queries, heartbeats', plus quoted phrases users would type verbatim ('start a dev server', 'run temporal server start-dev', 'temporal workflow start', 'temporal workflow signal', 'temporal workflow query', 'temporal workflow update').

5 / 5

Distinctiveness Conflict Risk

The Temporal SDK development niche is unambiguous with distinct triggers (specific SDK languages, Temporal CLI/Server/Cloud, durable-execution vocabulary). It is third-person and stays within its lane; sibling skills (ops, serverless, cloud setup) are disambiguated in the body, leaving minimal conflict risk.

5 / 5

Total

19

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 23 deeper-than-1-level

Warning

referenced_paths_exist

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

Warning

Total

14

/

16

Passed

Repository

temporalio/skill-temporal-developer

Path

SKILL.md

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.