Installs into .claude/skills of the current project.
Are you the author of Cloud Secrets?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/davidondrej-cloud-secrets)
---
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.
```bash
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.
