Configuring Cloud Environments
Inspect, create, and edit Claude Code cloud environments (the Name, Network access, Allowed domains, Setup script, and Environment variables behind claude.ai/code's environment selector) and decide what a repository needs from one — which hosts its toolchain downloads from and whether the Trusted allowlist covers them (bundled checker script), whether an existing environment fits or a new one is warranted, and what belongs in the environment's setup script versus the repository's SessionStart hook. Use when asked to look at, create, edit, or tune a cloud environment or its setup script, to add
Install
/plugin marketplace add tomada1114/tomada-claude-pluginsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add tomada1114/tomada-claude-plugins --skill configuring-cloud-environmentsgit clone --depth 1 https://github.com/tomada1114/tomada-claude-plugins.git /tmp/tomada-claude-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/tomada-claude-plugins/tomada-kit/skills/configuring-cloud-environments ~/.claude/skills/configuring-cloud-environmentsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Configuring cloud environments A cloud environment's settings live only in the claude.ai/code environment selector — no file, API, or CLI shows or changes them (`/remote-env` only picks the CLI default). Without this skill an agent guesses at what an environment contains, assumes Trusted covers a tool's downloads, or puts a VM install in the wrong layer. This skill reads the real settings through the browser, checks hosts against the live allowlist, and changes an environment only after the user approves the exact values. Facts about every field, caching, and the base image: [references/platform-facts.md](references/platform-facts.md). ## Before touching the browser Load the `operating-chrome` skill and read its `references/site-claude.md`. It owns how the selector and the environment dialog react to clicks (hover-only submenus, which button reference misfires, which field reads back its placeholder). This skill owns what to set and why. ## Inspecting an environment 1. In your own tab at `https://claude.ai/code`, open the environment selector → **Cloud** → the settings button beside the environment. 2. Read every field: Name, Network access, Allowed domains and the "Also include default list" checkbox (Custom only), Network secrets (names only), Setup script, Environment variables. Scroll the dialog; read the setup script from a screenshot. 3. Close with **Cancel**, never **Save changes**, and close the tab.
Details
- Skill name
configuring-cloud-environments- Repository
- tomada1114/tomada-claude-plugins
- Path
tomada-kit/skills/configuring-cloud-environments/SKILL.md- Repo updated
- 12 November 2026
FAQ
What does the Configuring Cloud Environments skill do?
Inspect, create, and edit Claude Code cloud environments (the Name, Network access, Allowed domains, Setup script, and Environment variables behind claude.ai/code's environment selector) and decide what a repository needs from one — which hosts its toolchain downloads from and whether the Trusted allowlist covers them (bundled checker script), whether an existing environment fits or a new one is warranted, and what belongs in the environment's setup script versus the repository's SessionStart hook. Use when asked to look at, create, edit, or tune a cloud environment or its setup script, to add
How do I install the Configuring Cloud Environments skill?
Claude Code plugin: /plugin marketplace add tomada1114/tomada-claude-plugins. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Configuring Cloud Environments popular?
It lives in tomada1114/tomada-claude-plugins, which has 5 GitHub stars and 0 forks.
Related skills
Auditing Prompt Docs
5tomada1114/tomada-claude-plugins
Audit and fix prompt-bearing documents — SKILL.md, CLAUDE.md, AGENTS.md, agent and command definitions, reference files, whole repositories — against Anthropic's published prompting guidance for current Claude models, proposing edits for approval before writing anything. Also answers how to prompt a specific model: holds the per- model guidance for Claude Fable 5.2, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5 alongside the cross-model practices. Use when reviewing or slimming an instruction file, when instructions are ignored or fire too often, when migrating a prompt to a newer m
Auditing Repositories
5tomada1114/tomada-claude-plugins
Audit the repository you are in, often a template or an app cut from one, for technical debt and room to improve in four areas: architecture and design patterns; tests; file structure and code quality; and tooling, CI, dependencies and the agent harness. Design a safe, test-first fix for every evidenced finding, and file the findings as GitHub issues that follow the repository's own issue conventions (triaging-issues, issue forms, past issues). A finding inherited from the template is also filed in the template repository. Cheap read-only sub-agents collect the evidence and high-effort analyst
Authoring Goal Prompts
5tomada1114/tomada-claude-plugins
Author a self-contained prompt for Claude Code's /goal command, run unattended in a separate session — a lead-to-staff handoff where this session researches, designs, and decides with full context, and a fresh executor session (Opus 5.5 or Fable 5.2, with none of that context) implements. Drafts a goal with measurable done-criteria, transcript-verifiable checks, scope + anti-cheat constraints, and stop rules; packages design intent, code examples, research findings, checklists, and pre-answered decisions as support files in a per-goal state directory whenever the executor would otherwise re-de
Configuring Project Permissions
5tomada1114/tomada-claude-plugins
Set up a repository's personal, uncommitted agent permissions so development runs without prompts: Claude Code's gitignored .claude/settings.local.json and Codex CLI's gitignored .codex/rules/local.rules, each in its native format. Generic rules (git, gh, coreutils, hook-bypass and force-push denies) go to the user-level files; the project file keeps only what names the repository — recipes, scripts, dependency policy, protected files — allow by default, ask only for commands that open the app, write to GitHub, release, or change dependencies. Detects the toolchain, drops rules a global rule a
Close
5Magnus-Gille/claude-skills
Close a coding-agent session or produce its final handoff only when the user explicitly asks to close, wrap up, or produce an end-of-session handoff.
Creating Agent Skills
5tomada1114/tomada-claude-plugins
Create or improve Agent Skills (the shared SKILL.md format read by Claude Code and OpenAI Codex CLI — SKILL.md + optional references/scripts/assets). Two playbooks: build a skill from scratch or from an existing doc; or review an existing skill through parallel specialist lenses (prose quality, agent neutrality, structure, scripts, orchestration) and propose fixes. Takes a free-form request — "I want a skill that…", "turn this runbook into a skill", "audit this skill", "it never fires", "split this into sub-agents" — optionally followed by a skill name or absolute path. Also triggers on Codex
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.