Temporal Developer

What it does

The entry explains cluster, worker, task-queue and replay responsibilities, then routes development topics into SDK-specific references. It distinguishes durable orchestration from Activity implementations and maps ordinary background-job vocabulary to standalone Activities rather than automatically wrapping every job in a Workflow.

Best for

Developers designing or debugging a Temporal application who can name the SDK language and the intended durable behavior.

Tradeoffs and requirements

A local development server is not a production deployment. Different SDKs and preview features have different constraints, while operations, serverless deployment and initial Cloud setup have separate source workflows. This assessment covers the main instruction map rather than every language guide or a running cluster.

Unknown; inspect source requirements and supporting scripts.

Install from the source

First time installing a skill? Follow the walkthrough →

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/temporalio/skill-temporal-developer/tree/5f5a94d448d53e0d535a7369bf9cb7248620a0bf --skill temporal-developer

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Network Access — review the source context.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

Offline package integrity

A temporary folder-copy check, not an agent installation or runtime safety verdict.

Check not completed: Package copy budget exceeded. This is not a successful installation.

AI Craft Pad Skill Score

85/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

43/100

43

Originality

80/100

80

Static Safety

60/100

60

Supporting-file static inspection

Bounded source inspection, not a runtime security audit. This inspection does not execute code.

2 text files inspected at this exact repository snapshot. 123 files outside the inspection budget or type allowlist. Dependencies were not installed or independently audited.

• Dependency Declaration: 1 file — inspect context before use.
• Network Client: 1 file — inspect context before use.

Absence of a pattern is not proof of safety. Permission needs and runtime behavior remain Unknown.

Suggested workflow

Identify the SDK, workflow history constraints and side-effect boundary before choosing references. Keep nondeterministic work in the supported Activity path, consider retries and idempotency, and review version changes against histories that may still replay.

How to judge the result

Exercise retries, worker restart, representative replay and the relevant interactive operations in a controlled environment. Confirm that a background-job design matches the intended producer behavior. Do not equate a started worker or queued execution with successful completion of the business operation.