check-env

Name: check-env
Author: ZenAlexa

Check required environment variables

by ZenAlexa(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Prompt file imported from ZenAlexa/hachimi-figure (.claude/commands/check-env.md). Copyright stays with the author.

Check if all required environment variables are properly configured:

Read .env.example to see required variables
Check if .env.local exists
Verify critical variables are set (without revealing their values):
- DATABASE_URL
- BETTER_AUTH_SECRET
- NEXT_PUBLIC_SITE_URL
- Other required variables based on enabled features

Report which variables are:

✅ Configured
⚠️ Optional (feature flags disabled)
❌ Missing but required

Do NOT display the actual values of sensitive variables.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

Check if all required environment variables are properly configured:

1. Read .env.example to see required variables
2. Check if .env.local exists
3. Verify critical variables are set (without revealing their values):
   - DATABASE_URL
   - BETTER_AUTH_SECRET
   - NEXT_PUBLIC_SITE_URL
   - Other required variables based on enabled features

Report which variables are:
- ✅ Configured
- ⚠️ Optional (feature flags disabled)
- ❌ Missing but required

Do NOT display the actual values of sensitive variables.

Manifest

Installed into a catalogue, chosen by a router

Install check-env and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Photo: RDNE Stock project

zenalexa-hachimi-figure-check-env-command.prompt.jsonjson

{
  "prompt": "Check if all required environment variables are properly configured:\n\n1. Read .env.example to see required variables\n2. Check if .env.local exists\n3. Verify critical variables are set (without revealing their values):\n   - DATABASE_URL\n   - BETTER_AUTH_SECRET\n   - NEXT_PUBLIC_SITE_URL\n   - Other required variables based on enabled features\n\nReport which variables are:\n- ✅ Configured\n- ⚠️ Optional (feature flags disabled)\n- ❌ Missing but required\n\nDo NOT display the actual values of sensitive variables.",
  "variables": [],
  "notes": "Check required environment variables",
  "metadata": {
    "source": {
      "provider": "github-claude-commands",
      "repository": "https://github.com/ZenAlexa/hachimi-figure",
      "path": ".claude/commands/check-env.md",
      "ref": "bfde51acaa858c46e4b03f40e2902292bdf1c226",
      "url": "https://github.com/ZenAlexa/hachimi-figure/blob/bfde51acaa858c46e4b03f40e2902292bdf1c226/.claude/commands/check-env.md",
      "key": "ZenAlexa/hachimi-figure/.claude/commands/check-env.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/zenalexa-hachimi-figure-check-env-command/manifest?version=1.0.0

About

Use it

Manifest

Install check-env and it becomes one more candidate the router can pick - when it fits.

Reviews