Skip to content
Agentmart
Submit a tool

managing-temporal-cloud-resources

Manage Convergint Temporal Cloud resources from a local machine using Chad's configured Temporal CLI profiles and Temporal Cloud API keys.

Skill by chadxz

IndexedMIT★ 3
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/chadxz-managing-temporal-cloud-resources

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Manage Convergint Temporal Cloud resources from a local machine using Chad's configured Temporal CLI profiles and Temporal Cloud API keys. Use when the user asks to list, inspect, start, signal, query, cancel, or terminate workflows; inspect schedules, task queues, workers, namespaces, API keys, or service accounts; refresh Temporal CLI profiles; or install and authenticate the Temporal and Temporal Cloud CLIs with mise.

Use cases: backend, productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 26, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/managing-temporal-cloud-resources

What's inside

Skill name
managing-temporal-cloud-resources
Description
Manage Convergint Temporal Cloud resources from a local machine using Chad's configured Temporal CLI profiles and Temporal Cloud API keys. Use when the user asks to list, inspect, start, signal, query, cancel, or terminate workflows; inspect schedules, task queues, workers, namespaces, API keys, or service accounts; refresh Temporal CLI profiles; or install and authenticate the Temporal and Temporal Cloud CLIs with mise.
License
MIT
Instructions
188 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • openai.yaml · agents/

SKILL.md (first lines)

# Managing Temporal Cloud Resources

## Overview

Use the `temporal` CLI for namespace-scoped operations such as workflows,
schedules, task queues, workers, and batches. Use the Temporal Cloud CLI surface
(`temporal cloud ...` when available, or `tcld ...` on Chad's current machine)
for account-level resources such as namespaces, API keys, service accounts, and
users.

For SDK code, worker implementation, workflow determinism, and application
development, use the `developing-temporal-applications` skill instead. This
skill is for operating Temporal Cloud from the command line.

## Local setup

Start by checking the local tools and profiles:

```bash
command -v temporal
temporal --version
temporal config list
```

The configured profile convention is:

- profile name: the Temporal namespace without the `.sajb4` account suffix
- namespace: the fully-qualified namespace, including `.sajb4`
- address: `us-east-2.aws.api.temporal.io:7233`
- auth: profile-local `api_key`

Examples:

```text
engineering-enablement-staging -> engineering-enablement-staging.sajb4
internal-tools-production      -> internal-tools-production.sajb4
platform-staging               -> platform-staging.sajb4
```

Use the profile name directly:

```bash
temporal --profile engineering-enablement-staging workflow list --limit 10
```

Do not add `--namespace` for normal use. The shorthand profiles already carry
the namespace. Use `--namespace` only when intentionally overriding a profile or
debugging an incomplete profile.

Inspect profile contents safely by redacting the API key:

```bash
temporal --profile engineering-enablement-staging config get \
  --output json |
  jq 'del(.api_key)'
```

Never paste API keys into chat, saved files, or command output unless the user
explicitly asks to reveal a token. Turn off shell tracing before commands that
touch tokens.

## Common operations

Prefer `--output json` when the result will be parsed or summarized.

```bash
# Workflows
temporal --profile <profile> workflow list --limit 10
temporal --profile <profile> workflow describe --workflow-id <workflow_id>
temporal --profile <profile> workflow show --workflow-id <workflow_id>
temporal --profile <profile> workflow query --workflow-id <workflow_id> \
  --type <query_type>
temporal --profile <profile> workflow signal --workflow-id <workflow_id> \
  --name <signal_name> --input '<json>'
temporal --profile <profile> workflow cancel --workflow-id <workflow_id>
temporal --profile <profile> workflow terminate --workflow-id <workflow_id> \
  --reason '<reason>'

# Schedules
temporal --profile <profile> schedule list
temporal --profile <profile> schedule describe --schedule-id <schedule_id>
temporal --profile <profile> schedule trigger --schedule-id <schedule_id>

# Task queues and workers
temporal --profile <profile> task-queue describe --task-queue <task_queue>
temporal --profile <profile> worker deployment list
```

Before destructive operations such as `terminate`, `delete`, schedule updates,
or API key deletion, confirm the profile, namespace, workflow ID, and expected
impact with the user unless the request already names them clearly.

## Install and authenticate

If `temporal` is missing, lacks `config --profile`, or the user asks for fresh
setup, follow the Temporal CLI access instructions from the Notion page titled
`Durable Execution with Temporal`. Use the Notion connector to fetch the page
when exact current wording matters.

Install with mise in the repo or directory where the user wants the tools
pinned:

```bash
mise use --pin "aqua:temporalio/cli" "github:temporalio/cloud-cli"
temporal --version
```

If mise reports an untrusted config in a new directory, run `mise trust` rather
than working around mise.

Authenticate to Temporal Cloud and create a personal API key. The Notion doc
uses this command form:

```bash
temporal cloud login
temporal cloud apikey create-for-me \
  --display-name "$(whoami)" \
  --description "Personal CLI access" \
  --expiry-duration 365d \

From chadxz/prompts, MIT.

More from chadxz/prompts

Signals

Stars
3
Forks
1
Open issues
0
Last commit (this folder)
Jul 7, 2026 (3 months ago)
Last release
Oct 15, 2026 (14 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from chadxz

Cite this page

managing-temporal-cloud-resources skill. Agent Mart. https://agentmart.dev/skills/chadxz-managing-temporal-cloud-resources (last updated 2026-10-24)