Menu
Generate a URL-safe password or opaque secret key for connection URLs and config files
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/nirecom/agents --skill create-keyThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
Based on SOC occupation classification
| name | create-key |
| description | Generate a URL-safe password or opaque secret key for connection URLs and config files |
| context | fork |
Generate a cryptographically random key or password for use in configuration.
When embedding a password in a connection URL (DATABASE_URL, REDIS_URL, AMQP URL, etc.),
the password component must be URL-safe. Standard base64 (+/=) breaks URL parsers
(real example: Prisma invalid port number).
Allowed formats:
hex (recommended — no special characters)
openssl rand -hex 32-join ((1..32)|%{'{0:x2}' -f (Get-Random -Max 256)})base64url (no padding): openssl rand -base64 32 | tr '+/' '-_' | tr -d '='Prohibited: standard base64 (+/=) embedded unencoded in a URL password.
Variable separation (preferred): Provide both a composed URL and separate
POSTGRES_PASSWORD / POSTGRES_USER / POSTGRES_HOST variables — avoids URL escaping
issues entirely.
For secrets not embedded in a URL (NextAuth secret, salt, JWT secret, etc.):
openssl rand -base64 32 or openssl rand -hex 32 — either is fine.
Once a secret appears in chat, it persists in conversation logs, screenshots, and terminal scrollback. To minimize exposure: