temporal-development
/temporal-development
Build, test, deploy, or operate this monorepo's Temporal workflows, activities, workers, task queues, and schedules. Use for packages/temporal or Scout Temporal integration; use a generic Temporal reference skill for SDK concepts alone.
- Author
- shepherdjerred ↗
- Repository
- monorepo ↗
- Licence
- GPL-3.0
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
GPL-3.0, otwarta.
What it does and when to use it
Build, test, deploy, or operate this monorepo's Temporal workflows, activities, workers, task queues, and schedules. Use for packages/temporal or Scout Temporal integration; use a generic Temporal reference skill for SDK concepts alone.
Original author description
Build, test, deploy, or operate this monorepo's Temporal workflows, activities, workers, task queues, and schedules. Use for packages/temporal or Scout Temporal integration; use a generic Temporal reference skill for SDK concepts alone.
How it works
SKILL.md has no level-two headings · 31 lines, 223 words
SKILL.md preview
--- name: temporal-development description: Build, test, deploy, or operate this monorepo's Temporal workflows, activities, workers, task queues, and schedules. Use for packages/temporal or Scout Temporal integration; use a generic Temporal reference skill for SDK concepts alone. --- # Temporal development Temporal owns every scheduled and recurring workload in this repository. Central workflows live in `packages/temporal`; Scout domain workflows live in Scout's Temporal package. Read the local AGENTS file and README for the boundary you change. - Workflow code must remain deterministic. Time, I/O, network, filesystem, process, and secrets belong in Activities. - Changes to Workflow history behavior need replay/versioning analysis. Never assume a deployment can safely reinterpret open executions. - Define recurring work in `src/schedules/schedule-definitions.ts`; do not add a CronJob or timer. - Keep task queues, namespaces, schedules, and worker ownership explicit. - Activities use deliberate timeouts, retries, heartbeats, and cancellation. External writes need idempotency or a durable effect checkpoint. - A terminal external or quota failure is not automatically retryable. Preserve the semantic distinction between failure, deferral, and operator action. - Use the shared typed agent-task contract and environment sanitizer. Deployed inference goes through the repository runtime and approved credential path. Run focused build, typecheck, test, lint, and replay tests for changed Workflows. For live work, identify namespace, workflow ID, run ID, task queue, worker build, and schedule before mutation. Inspect histories and pending Activities rather than inferring from a UI summary. Do not cancel a healthy durable timer merely because it is quiet. Source tests, worker registration, schedule state, Workflow completion, and downstream delivery are separate acceptance layers.
Versions
The database has no other skills named temporal-development.
Database snapshot: 13.11.2026 · package version f71556eaf58e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 85temporal-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,… - 90temporal-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,… - 100local-temporal-developer-88d147e2
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,… - 100temporal-python-pro
Temporal workflow orchestration with the Python SDK. Use when building durable workflows, implementing distributed transactions, designing activity patterns, or deploying Temporal workers. - 100temporal-developer
Temporal durable-execution fundamentals — workflow/activity/worker split and determinism. Use when building or debugging Temporal workflows. Do NOT use for the config-driven DAG engine (temporal-config-driven). - 100temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.