nexus-operations

Coordinate cross-namespace durable communication for Temporal workflows.

3|1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/therealbill/mynet --skill nexus-operations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nexus-operations
Source: https://github.com/therealbill/mynet/tree/main/timelord/skills/nexus-operations
Command: npx skills add https://github.com/therealbill/mynet --skill nexus-operations

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Temporal Nexus provides cross-namespace durable communication for workflows, enabling independent teams to coordinate via typed service contracts while preserving full Temporal guarantees.

Core Features & Use Cases

  • Cross-namespace calls with durable execution guarantees
  • Typed operations and explicit endpoints for clean contracts
  • Async (workflow-backed) and sync operations with error handling

Quick Start

Instantiate a Nexus endpoint and try a sample synchronous operation to validate cross-namespace communication.

Frequently Asked Questions about nexus-operations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make durable cross-namespace calls in Temporal workflows?

Cross-namespace durable communication in Temporal uses Nexus endpoints and typed service contracts to connect workflows. This preserves full execution guarantees and end-to-end event history across independent namespaces.

What are Nexus endpoints and how do they route cross-namespace services?

Nexus endpoints route cross-namespace services by defining explicit typed operations. They support both synchronous and asynchronous workflow-backed operations with at-least-once semantics and comprehensive error handling.

Does Temporal Nexus support cross-namespace operations in Python and Java?

Temporal Nexus supports cross-namespace operations across Go, Java, Python, and TypeScript. It provides typed service contracts and endpoint routing for durable communication in all these languages.

Can I use Nexus operations for async workflow-backed calls with error handling?

Nexus operations support async workflow-backed calls with built-in error handling. You define typed operations on a Nexus endpoint to execute durable cross-namespace communication with at-least-once semantics.

When do I need typed service contracts for Temporal cross-namespace workflows?

Typed service contracts are needed when independent teams coordinate cross-namespace Temporal workflows. They provide explicit endpoint routing and operation definitions, ensuring clean interfaces and durable execution guarantees.