namespace-management

Manage Temporal namespaces for isolation, configuration, and governance.

3|1|Updated Feb 8, 2026

Search Tags:#security #retention #namespace #temporal #provisioning #nexus

Ready to run

npx skills add https://github.com/therealbill/mynet --skill namespace-management

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: namespace-management
Source: https://github.com/therealbill/mynet/tree/main/timelord/skills/namespace-management
Command: npx skills add https://github.com/therealbill/mynet --skill namespace-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Temporal namespaces require careful provisioning, isolation, and governance across environments; teams need a clear guide for naming, configuring retention, security, search attributes, archival, and cross-namespace patterns to avoid sprawl and misconfigurations.

Core Features & Use Cases

Namespace provisioning and configuration (retention, description, and security)
Multi-tenant patterns across environments (per-service, per-environment, per-team)
Nexus endpoint guidance and per-namespace access control, including archival and search attributes setup
Governance practices: naming conventions, authorization, and auditability

Quick Start

Create a new namespace named 'orders' with a 7-day retention and a description for production workloads.

Frequently Asked Questions about namespace-management

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

FAQPage Schema

How do I provision a Temporal namespace for production?▼

Provisioning a Temporal namespace requires creating it with defined retention periods, descriptions, and security controls using CLI, operator, or SDK interactions. This ensures proper isolation and governance for production workloads.

What is the best way to configure retention and archival for Temporal namespaces?▼

Configuring retention and archival for Temporal namespaces requires setting specific parameters during namespace creation or updates. You can apply retention policies and enable archival to maintain data governance and compliance across your environments.

How do I set up multi-tenant isolation across Temporal environments?▼

Multi-tenant isolation in Temporal is achieved by provisioning separate namespaces per service, environment, or team. This approach provides clear boundaries, access control, and prevents configuration sprawl across development, staging, and production.

Can I apply per-namespace access control and search attributes in Temporal?▼

Yes, you can apply per-namespace access control and configure search attributes in Temporal. This allows you to manage authorization, enable custom querying, and maintain security boundaries for specific namespace workloads.

Do I need Nexus endpoint configuration for Temporal namespace governance?▼

Nexus endpoint configuration is part of comprehensive Temporal namespace governance. It provides guidance on cross-namespace patterns and access control, ensuring proper authorization and auditability across your workflow environments.

What naming conventions should I use for Temporal namespace management?▼

Temporal namespace management requires clear naming conventions to avoid sprawl and misconfigurations. Establishing consistent naming practices for per-service, per-environment, and per-team namespaces ensures proper authorization, auditability, and governance across your infrastructure.