Iron Proxy Gateway for NanoClaw
nanocoai/nanoclaw
Installs or refreshes Iron Proxy and its Iron Control web console for NanoClaw, with a local Docker setup, database, credentials and a human approval bridge.
Ask the user for API keys, tokens, or other credentials from a Cloudroom cloud thread and write them to a dotenv file without exposing them in chat.
Install Cloud Secrets
$ npx skills add davidondrej/cloudroom-core --skill cloud-secrets -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install davidondrej/cloudroom-core cloud-secrets --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/davidondrej/cloudroom-core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/secrets/cloud-secrets .claude/skills/cloud-secrets && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cloud-secrets" agent skill from https://github.com/davidondrej/cloudroom-core/tree/main/src/secrets/cloud-secrets into .claude/skills/cloud-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-secrets", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/davidondrej/cloudroom-core/tree/main/src/secrets/cloud-secretsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add davidondrej/cloudroom-core --skill cloud-secrets -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install davidondrej/cloudroom-core cloud-secrets --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davidondrej/cloudroom-core.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/secrets/cloud-secrets .agents/skills/cloud-secrets && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cloud-secrets" agent skill from https://github.com/davidondrej/cloudroom-core/tree/main/src/secrets/cloud-secrets into .agents/skills/cloud-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-secrets", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add davidondrej/cloudroom-core --skill cloud-secrets -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install davidondrej/cloudroom-core cloud-secrets --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davidondrej/cloudroom-core.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/secrets/cloud-secrets .cursor/skills/cloud-secrets && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cloud-secrets" agent skill from https://github.com/davidondrej/cloudroom-core/tree/main/src/secrets/cloud-secrets into .cursor/skills/cloud-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-secrets", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/davidondrej/cloudroom-core.git --path src/secrets/cloud-secrets--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add davidondrej/cloudroom-core --skill cloud-secrets -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install davidondrej/cloudroom-core cloud-secrets --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davidondrej/cloudroom-core.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/secrets/cloud-secrets .gemini/skills/cloud-secrets && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cloud-secrets" agent skill from https://github.com/davidondrej/cloudroom-core/tree/main/src/secrets/cloud-secrets into .gemini/skills/cloud-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-secrets", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install davidondrej/cloudroom-core cloud-secretsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add davidondrej/cloudroom-core --skill cloud-secrets -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/davidondrej/cloudroom-core.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/secrets/cloud-secrets .github/skills/cloud-secrets && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cloud-secrets" agent skill from https://github.com/davidondrej/cloudroom-core/tree/main/src/secrets/cloud-secrets into .github/skills/cloud-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-secrets", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add davidondrej/cloudroom-core --skill cloud-secrets -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install davidondrej/cloudroom-core cloud-secrets --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davidondrej/cloudroom-core.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/secrets/cloud-secrets .opencode/skills/cloud-secrets && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cloud-secrets" agent skill from https://github.com/davidondrej/cloudroom-core/tree/main/src/secrets/cloud-secrets into .opencode/skills/cloud-secrets/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-secrets", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cloud-secrets- GitHub stars
- 272
- Token cost
- ~337 tokens
- SKILL.md length
- 140 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Ask the user for API keys, tokens, or other credentials from a Cloudroom cloud thread and write them to a dotenv file without exposing them in chat.
- Tasks that involve Secrets management
- Needs OPENAI_API_KEY and RESEND_API_KEY
What it does
Cloud Secrets is an agent skill from davidondrej/cloudroom-core. Ask the user for API keys, tokens, or other credentials from a Cloudroom cloud thread and write them to a dotenv file without exposing them in chat.
Its SKILL.md is about 340 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Secrets management. The repository describes itself as: Open-source, self-hostable Rust runtime that runs Claude Code, Codex, and Pi in the cloud. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Secrets management
Example prompts
- “/cloud-secrets”
Requirements
- A credential in OPENAI_API_KEY
- A credential in RESEND_API_KEY
What it can do on your machine
Read from SKILL.md and the folder at commit d5222b5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
OPENAI_API_KEYRESEND_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cloud Secrets loads about 337 tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 140 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:17
--write-env .env.local
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from davidondrej/cloudroom-core at commit d5222b5, republished under its Apache-2.0 licence (© davidondrej). 140 words, ~337 tokens.
Download SKILL.mdSave it as
.claude/skills/cloud-secrets/SKILL.md (or your agent's skills folder).- name
- cloud-secrets
- description
- Ask the user for API keys, tokens, or other credentials from a Cloudroom cloud thread and write them to a dotenv file without exposing them in chat.
Request secrets securely
Use cloudroom secret request when the user needs to supply a credential. Never ask the user to paste a secret into chat.
Batch every known variable into one request. Check documentation or .env.example for names, but never read or print an existing secret-bearing env file.
cloudroom secret request OPENAI_API_KEY RESEND_API_KEY \
--purpose "Configure application credentials" \
--describe OPENAI_API_KEY "OpenAI API key used by the server" \
--describe RESEND_API_KEY "Resend API key used for transactional email" \
--write-env .env.local- The user fills a secure form in the thread. The command waits until they submit or cancel, so allow it up to 10 minutes.
- Relative paths resolve from the current folder. The file is written with mode 0600.
- After success, trust the printed path and added/updated/unchanged counts. Never verify with
cat,env, or anything that reveals values. - If it reports duplicate or multiline assignments, fix the file structure without reading values, then rerun.
- If the request is cancelled, ask in chat whether to try again. Never ask for the values in chat.
© davidondrej, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in src/secrets/cloud-secrets of davidondrej/cloudroom-core.
Open the folder on GitHubat commit d5222b5
Compare with similar skills
Cloud Secrets next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cloud Secrets this skilldavidondrej/cloudroom-core | 272 | — | ~337 | Automated safety check: Notes | Apache-2.0 | |
| Iron Proxy Gateway for NanoClawnanocoai/nanoclaw | 31k | — | ~4.6k | Automated safety check: Notes | MIT | |
| LangBot Deployment Guidelangbot-app/LangBot | 18k | — | ~1.2k | Automated safety check: Notes | Apache-2.0 | |
| Env Var Conventionssgl-project/sglang | 37k | 2 repos | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Mac Fleet Maintenancesteipete/agent-scripts | 7.3k | — | ~4.8k | Automated safety check: Pass | MIT | |
| Add Config Env Varbaserow/baserow | 6.1k | — | ~1.1k | Automated safety check: Pass | Custom licence |
Similar skills
LangBot Deployment Guide
langbot-app/LangBot
Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.
Env Var Conventions
sgl-project/sglang
Conventions for SGLang environment variables — where to define, how to access, how to name, and how to deprecate.
Mac Fleet Maintenance
steipete/agent-scripts
Inventories and maintains a fleet of Macs from a desired-state file: package updates, repo and Xcode sync, and disk, backup and security health reports.
Add Config Env Var
baserow/baserow
Add a Baserow configuration environment variable for the backend, frontend, or both, and propagate it through settings, Nuxt runtime config, Docker Compose, documentation, consumers, and tests as…
Edgeone Makers CLI
TencentEdgeOne/edgeone-makers-tools
EdgeOne Makers CLI command reference. An agent skill from TencentEdgeOne/edgeone-makers-tools.
More from davidondrej/cloudroom-core
Cloud Computer Use
davidondrej/cloudroom-core
See and control desktop apps on this Cloud sandbox’s virtual Linux screen with cloudroom computer-use: launch GUI apps you build or install, read their UI, click, type, and take screenshots.
Room CLI
davidondrej/cloudroom-core
Inspect and control the user’s Cloudroom threads, projects, and settings from a cloud thread.
Cloud Mac
davidondrej/cloudroom-core
Run commands and copy files on the user’s paired Mac from a Cloudroom cloud thread.
Cloud Preview
davidondrej/cloudroom-core
Show a web app running in a Cloudroom cloud thread through the user’s laptop localhost.
Related
Categories
Questions about Cloud Secrets
What does Cloud Secrets do?
Ask the user for API keys, tokens, or other credentials from a Cloudroom cloud thread and write them to a dotenv file without exposing them in chat. Cloud Secrets is an agent skill from davidondrej/cloudroom-core. Ask the user for API keys, tokens, or other credentials from a Cloudroom cloud thread and write them to a dotenv file without exposing them in chat.
When should I use Cloud Secrets?
Cloud Secrets fits situations like: tasks that involve Secrets management.
How do I install Cloud Secrets in Claude Code?
Run `npx skills add davidondrej/cloudroom-core --skill cloud-secrets -a claude-code`. Or copy the skill folder (src/secrets/cloud-secrets in davidondrej/cloudroom-core) into .claude/skills/cloud-secrets in your project. Claude Code loads it when a task matches its description.
How do I install Cloud Secrets in Codex?
Run `npx skills add davidondrej/cloudroom-core --skill cloud-secrets -a codex`. Or copy the skill folder (src/secrets/cloud-secrets in davidondrej/cloudroom-core) into .agents/skills/cloud-secrets in your project. Codex loads it when a task matches its description.
Can I use Cloud Secrets in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davidondrej/cloudroom-core --skill cloud-secrets -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cloud-secrets, .gemini/skills/cloud-secrets, .github/skills/cloud-secrets and .opencode/skills/cloud-secrets in your project.
What does Cloud Secrets need to run?
Going by SKILL.md and its folder, Cloud Secrets needs credentials named OPENAI_API_KEY and RESEND_API_KEY. Our summary lists: A credential in OPENAI_API_KEY; A credential in RESEND_API_KEY.
Does Cloud Secrets access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cloud Secrets safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Cloud Secrets use?
Cloud Secrets is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cloud Secrets use?
About 337 tokens (SKILL.md is roughly 1.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Cloud Secrets?
Skills that share tags, products or a category with Cloud Secrets: Iron Proxy Gateway for NanoClaw (nanocoai/nanoclaw, 31k stars), LangBot Deployment Guide (langbot-app/LangBot, 18k stars), Env Var Conventions (sgl-project/sglang, 37k stars) and Mac Fleet Maintenance (steipete/agent-scripts, 7.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cloud Secrets?
davidondrej (a GitHub user) maintains it in davidondrej/cloudroom-core, which has 272 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 7, 2026.
Source: davidondrej/cloudroom-core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.