skills.rest
ryan-haver
ryan-haverCOMMUNITY
Explore all skills by this author →
GitHub

app-secrets

Create and access encrypted secrets for FuseBase app backends via CLI and environment variables.

5|2|Updated Feb 9, 2026
Search Tags:#backend#cli#configuration#secrets#environment variables#api keys#fusebase
One-click install
npx skills add https://github.com/ryan-haver/fusebase-mcp --skill app-secrets-ryan-haver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: app-secrets
Source: https://github.com/ryan-haver/fusebase-mcp/tree/main/apps/client-portal-dashboard/.claude/skills/app-secrets
Command: npx skills add https://github.com/ryan-haver/fusebase-mcp --skill app-secrets-ryan-haver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing API keys, passwords, and other sensitive configuration for FuseBase app backends without committing them to source control or relying on local .env files. ## Core Features & Use Cases - CLI Secret Registration: Register secret keys with descriptions using fusebase secret create, which updates fusebase.json and registers keys on the platform at deploy time. - Runtime Injection: Secrets are injected as environment variables into the backend process and read via process.env, with fail-fast startup validation patterns. - Local Development Parity: fusebase dev start downloads the same production secrets automatically, eliminating the need for dotenv or backend/.env files. - Use Case: A backend needs a Stripe secret key and an OpenAI API key. Register both with one CLI command, deploy to get the secrets URL, fill in values in the FuseBase UI, and access them via process.env in both dev and production. ## Quick Start Ask the AI to create the required secrets for your app backend using the fusebase secret create CLI command and show how to validate them at backend startup.

Frequently Asked Questions about app-secrets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create secrets for a FuseBase app backend?▼

Run fusebase secret create with the --app flag and one or more --secret flags in KEY:description format. This edits fusebase.json only; keys are registered on the platform during the next fusebase deploy or fusebase dev start, which prints the URL to set values.

How do I access secrets in backend code at runtime?▼

Secrets are injected as environment variables, so read them with process.env in any backend file. Validate required secrets at startup with a helper that throws a clear error when a variable is missing, so the backend fails fast.

Can I use a .env file or dotenv for local development?▼

No. fusebase dev start downloads the same production secrets and injects them automatically. Do not create a backend/.env file, add dotenv as a dependency, or use import 'dotenv/config' in backend code.

Are secrets available in the browser or frontend SPA?▼

No. Secrets are only injected into the app backend process and are never accessible in browser or SPA code. Never reference secret keys from frontend code.

Can the backend update secret values at runtime?▼

No. Secrets are read-only at runtime and can only be set via the CLI or the FuseBase web UI. For per-user credentials obtained at runtime like OAuth refresh tokens, use httpOnly cookies instead.

Related Skills

Explore More Software Engineering Skills→
fusebase-devfusebase-dev
6

app-sidecar

Manage auxiliary container services for FuseBase app backends and cron jobs.

Official
Intermediate
fusebase-devfusebase-dev
6

app-secrets

Stores sensitive Fusebase app credentials securely and injects them as environment variables.

Official
Intermediate
RyanzucchiRyanzucchi

autenticacao-jwt-e-refresh-token

Implements stateless JWT authentication with rotating refresh tokens in HTTPOnly cookies.

Community
Advanced
darkmatterdarkmatter
1

sops-secret-access

Decrypt SOPS-encrypted project files to access non-secret configuration details.

Official
Intermediate