Validate Env File

Overview

When you send .env content, we parse it with a conservative grammar and validate required, forbidden, and allowed keys plus optional value rules. We never evaluate command substitution, resolve ${VAR} references, or read your process environment. Likely secret values are never returned — do not use this when you need interpolation expansion or shell execution. Accepts file input via file_ref — no need to extract file content first.

Env misconfiguration and committed secrets are common. We validate safely offline without executing your values.

When to use it

Scope

Non-goals

• Does not evaluate commands or backticks
• Does not resolve ${VAR} interpolation
• Does not read the process environment
• Does not return raw secret values

Properties

Capabilities

Cost & billing

Flat rate per invocation

File handling

File limits

Constraints this skill applies to your input and generated files. The “Limited by” column shows the static source of each cap; none of these can be raised by upgrading your plan.

How we handle your data

Input schema

Output schema

API contract

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"code.validate_env_file","input":{"content":"PORT=8080\n","requirements":{"requiredKeys":["PORT"]}}}'

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("code.validate_env_file", {"requirements":{"requiredKeys":["DATABASE_URL"]},"content":"PORT=8080\n"});

Errors

Other limits

Limitations

• Does not evaluate commands or backticks
• Does not resolve ${VAR} interpolation
• Does not read the process environment
• Does not return raw secret values
• Interpolating variable references
• Executing shell in values

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "code.validate_env_file",
  "input": {
    "requirements": {
      "requiredKeys": [
        "DATABASE_URL"
      ]
    },
    "content": "PORT=8080\n"
  }
}

Examples

{
  "requirements": {
    "requiredKeys": [
      "DATABASE_URL"
    ]
  },
  "content": "PORT=8080\n"
}

{
  "warnings": [],
  "valid": false,
  "_meta": {
    "grammar": "dotenv-conservative-1",
    "keyCount": 1
  },
  "errors": [
    {
      "code": "ENV_REQUIRED_KEY_MISSING",
      "message": "Required key 'DATABASE_URL' is missing",
      "path": "DATABASE_URL",
      "line": null,
      "severity": "error"
    }
  ],
  "keys": [
    {
      "line": 1,
      "key": "PORT",
      "quote": "none"
    }
  ]
}

{
  "requirements": {
    "requiredKeys": [
      "PORT"
    ]
  },
  "content": "PORT=8080\n"
}

{
  "warnings": [],
  "valid": true,
  "_meta": {
    "grammar": "dotenv-conservative-1",
    "keyCount": 1
  },
  "errors": [],
  "keys": [
    {
      "line": 1,
      "key": "PORT",
      "quote": "none"
    }
  ]
}

Recommended use cases

• Enforce required and forbidden keys in CI
• Validate integer ranges and enums on env values
• Flag likely secrets committed to .env files

Avoid for

• Interpolating variable references
• Executing shell in values

Related skills

Composable with

Safety & privacy

• Runs without calling any external service.
• Your payloads are never stored permanently.
• Telemetry captures metadata only — never your payload contents.
• We never train models on your payloads.
• No human reviews your payloads.

Tags