How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

temporal - Skill - OpenSmartRoute

Name: temporal
Author: shepherdjerred

Imported from shepherdjerred/monorepo (packages/temporal/AGENTS.md). Install upstream with npx skills add shepherdjerred/monorepo --skill temporal. Copyright stays with the author.

Monorepo Temporal constraints

This package owns central durable workflows, activities, workers, schedules, and event ingress for the monorepo. README.md owns role/queue and operator reference; the Temporal wiki explains workflow families and boundaries. Load temporal-development for the working procedure.

Runtime boundaries

Workflow code is deterministic and credentialless. I/O, time, filesystem, subprocesses, network, and secrets belong in Activities.
Production uses explicit role-separated workers. all is local development only and must never become a production fallback.
Namespaces are explicit: local dev, Scout beta beta, and shared production prod. Do not export a production address globally.
Central/business Workflow tasks use monorepo-workflows; Delivery orchestration uses its own delivery-workflows queue and independently released poller. Domain Activity queues keep separate credentials, service accounts, concurrency, and health.
Existing executions stay on their recorded task queue and Workflow history. Use compatible pollers, replay, and Worker Versioning for changes.

Schedules and effects

All recurring jobs are declared in src/schedules/schedule-definitions.ts. Preserve stable schedule and workflow IDs, overlap policy, catchup intent, and orphan detection.
Activities declare semantic retry/timeout/heartbeat/cancellation behavior. External writes and delivery use idempotency or durable effect checkpoints.
A quota-terminal or ambiguous external result is not a generic retry. Do not replay an occurrence when a prior executor may still settle it.
Report delivery is exclusive and auditable. A generated report, durable send record, downstream receipt, and user-visible message are separate evidence.
Generic agent tasks follow the shared typed schema, bounded tools, redacted environment, and Codex SDK policy. Never pass inference credentials to tool subprocesses.
Durable agent chats use the reviewed Claude Agent SDK or Codex App Server adapter with subscription authentication. Their provider is fixed at chat creation; provider session state is durable, while each turn gets a fresh workspace.
PR-creating workflows use the bot-clone helper and repository PR contract; do not hand-roll installs or stack state in ephemeral clones.

Verification and operations

TEMPORAL_NAMESPACE=dev TEMPORAL_WORKER_ROLE=all bun run start
bun run typecheck
bun run test
bun run lint

Workflow changes require bundle and retained-history replay appropriate to the change. Delivery worker releases verify exact image provenance, replay, healthy pollers and pinned candidate canaries before direct promotion, then verify normally routed canaries. Retained hosts require independent drainage proof before retirement. Rollouts and patch retirements never wait out a fixed period; gate them on replay, canaries and drainage evidence. Alerts from other workers do not block deployment routing. Inspect a stale lease before removal.

For live work, identify namespace, workflow ID, run ID, task queue, worker build, and schedule. A quiet durable timer is healthy; do not cancel it merely for inactivity. Verify downstream effects separately from Workflow completion.

Install temporal and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "shepherdjerred-monorepo-temporal", "kind": "skill", "name": "temporal", "description": "This package owns central durable workflows, activities, workers, schedules, and event ingress for the monorepo. `README.md` owns role/queue and operator reference; the Temporal wiki explains workflow families and boundaries. Load `temporal-development` for the working procedure.", "publisher": "shepherdjerred", "version": "1.0.0", "capabilities": { "domains": [ "customer_support", "coding" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "This package owns central durable workflows, activities, workers, schedules, and event ingress for the monorepo. `README.md` owns role/queue and operator reference; the Temporal wiki explains workflow families and boundaries. Load `temporal-development` for the working procedure." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/shepherdjerred/monorepo", "path": "packages/temporal/AGENTS.md", "ref": "34151335691b49dcf413a9f736a1e1be0b0d3ce4", "url": "https://github.com/shepherdjerred/monorepo/blob/34151335691b49dcf413a9f736a1e1be0b0d3ce4/packages/temporal/AGENTS.md", "key": "shepherdjerred/monorepo/packages/temporal/AGENTS.md" } }, "instructions": "# Monorepo Temporal constraints\n\nThis package owns central durable workflows, activities, workers, schedules,\nand event ingress for the monorepo. `README.md` owns role/queue and operator\nreference; the Temporal wiki explains workflow families and boundaries. Load\n`temporal-development` for the working procedure.\n\n## Runtime boundaries\n\n- Workflow code is deterministic and credentialless. I/O, time, filesystem,\n subprocesses, network, and secrets belong in Activities.\n- Production uses explicit role-separated workers. `all` is local development\n only and must never become a production fallbac", "cost": { "context_tokens": 821 } }

temporal

About

Monorepo Temporal constraints

Runtime boundaries

Schedules and effects

Verification and operations

Install temporal and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews