Sanity & Netlify Env Check v1.0

Install

Start with the ZIP package, then choose the AI tool workflow that fits your setup.

1. Download sanity-netlify-env-check.zip (1.2 KB).
2. Open the package and read SKILL.md, plus any included references, templates, or scripts.
3. Use the instructions directly in any AI tool that supports reusable instructions, project knowledge, custom agents, or uploaded reference files.

For Claude Code, unzip into ~/.claude/skills/ so the folder lands at ~/.claude/skills/sanity-netlify-env-check/, then reload Claude Code. For Claude.ai, upload the same ZIP from Customize → Skills.

Use with other AI tools

This package is not locked to one vendor. If your AI tool does not support Claude-style skills, copy the core instructions from SKILL.md into the tool's custom instructions, project prompt, agent setup, or reusable prompt library.

• Upload or paste any included reference files as project knowledge where your tool supports it.
• Keep the output format from SKILL.md intact so results stay predictable.
• Run a small test with your own data before using the workflow in production.

Compatibility depends on the features your AI tool provides. Treat scripts as optional local helpers unless your environment can run them safely.

Claude installation reference

What it does

This skill provides a pre-deployment check that validates all required environment variables for a Sanity + Netlify project. Missing variables are the silent killer of CI pipelines; this script makes them loud and clear.

When to use it

Run this script before any netlify deploy or Sanity build hook trigger. Integrate it into your package.json scripts or your CI pipeline as a first step. It's especially useful when multiple team members manage different env files.

Installation

Copy the check-env.sh script from the skill package into your project:

cp agent-output/skill/scripts/check-env.sh ./scripts/

Usage

Make the script executable and run:

chmod +x scripts/check-env.sh
bash scripts/check-env.sh

If all environment variables are set, you'll see a success message. If any are missing, the script exits with code 1 and prints a list of missing variables.

Limitations

• Only checks variables by name; does not validate their values (e.g., token validity).
• Assumes the variable names match exactly those used in the Sanity Netlify integration.
• Does not check for optional env vars; only the required ones.

Related skills

Skills that pair well, or that you'd reach for instead:

Review this skill