COM-293: Fix skill issues found during manual review

[tomba7]

Changes

Provider scope

• SKILL.md gains a Supported compute providers table — provider, compute service, support status, reference directory — replacing release-status prose spread across four files. Provider support is now answerable without reading paragraphs
• Only a provider marked Supported is covered; a request naming another stops rather than being served adapted Lambda material
• Workflow steps and the routing table use references/<provider>/... with the directory layout stated once, so the file stays provider-neutral as providers are added
• GCP survives in exactly two places, both load-bearing: the support table, and the gcp- region prefix used to classify ineligible Namespaces in step 1
• Skill description no longer names Cloud Run

Control-plane CLI

• temporal cloud ... is still pre-release, so tcld is the supported path for control-plane work today — accounts, Namespaces, API keys, users, service accounts. The comparison table presenting the two as alternatives is gone
• Worker Deployments and Workflows are not control-plane operations: they live on the Namespace frontend, have no tcld equivalent, and keep using temporal worker deployment ...
• Namespace and API-key commands rewritten to tcld, including teardown. Confirmation flag corrected to --auto_confirm (underscore) — the temporal cloud spelling exits clean having deleted nothing
• Adds the two agent-shell mechanics: tcld login --disable-pop-up prints the URL instead of relying on auto-open, and mutating operations need --auto_confirm or AUTO_CONFIRM=true
• To revisit once temporal cloud ... reaches GA

Namespace and provider pairing

• Generalized from "a GCP Namespace can't run Lambda" to the rule: a Serverless Worker runs only on the cloud provider hosting its Namespace, and there is no cross-cloud pairing
• Step 1's Namespace pick now settles the provider answer, so a mismatch is caught there rather than at connection time several steps later

Browser fallback

• Where the Temporal CLIs cannot authenticate, "fix the CLI" and "work in the browser" are presented as equals rather than a preference and a fallback. Every control-plane and frontend step exists in the Cloud UI, and setup.md now names which steps belong to which plane
• "None" in the access matrix means no authenticated CLI, not no access — the user still has the Cloud UI and their provider's console. Both middle rows rewritten to walk the user through the UI, not just generate commands to hand off

Environment-specific content removed

• A real test-account Namespace was used as the "names are long and error-prone" example. Replaced with the shape, <name>-<suffix>.<account>

Run transparency

• The checklist is reprinted in full at every step boundary, marked ✅/⏳/⬜, rather than narrated as "stage complete." A narration says where you are but not what remains, and the user cannot see it without scrolling back
• Commands are announced in message text above the block — the user sees a collapsed "Ran 6 shell commands," and the tool's own description field renders underneath the command it describes
• Step 8 delivers the inventory before offering teardown, and does not write a teardown script until asked. Generating it unprompted buries the inventory the user needs in order to decide

Skill version 0.5.0 → 0.6.0.

Testing

Manually verified — driven end-to-end against Temporal Cloud on with a Go Worker on Lambda arm64 and a Namespace on AWS us-west-2, after these changes:

🤖 Generated with Claude Code

[starfleeth]

LGTM