Skip to main content

Squillify development is paused indefinitely. Read why, and discover what this experiment achieved. Read the story

MicroSkills Reference

Environment Matrix Validator

devops.validate_env_matrix

ProductionBounded custom (Class B)Deterministicstrictfastv1.0.0
No network

Overview

You pass up to 16 already-parsed environment maps and we report missing keys, drifting values, secret reuse, and schema violations. Values are never emitted — secrets are compared by digest only. This complements code.validate_env_file, which checks dotenv syntax for one file. Do not use this for dotenv file parsing.

Cross-environment diffs that echo values leak production secrets into agent logs. We compare by digest and report policy violations without exposing values.

Reliability

STRICT and deterministic — findings never contain values. Domain errors (not retryable — fix input): ENV_MATRIX_LIMIT_EXCEEDED (more than 16 environments or 1,000 keys — split the matrix); ENV_SCHEMA_INVALID (schema object is malformed — correct required/secret/allowedValues shapes); ENV_ENVIRONMENT_NAME_DUPLICATE (two environments share a name — use unique names). Policy violations such as ENV_KEY_MISSING and ENV_SECRET_REUSED appear in findings[] with valid:false.

Context footprint

One call replaces pairwise env diffs that would leak values into logs. A successful call costs 1 execution credit.

When to use it

When comparing already-parsed env maps for drift and policy.

When validating dotenv file syntax — use code.validate_env_file first.

Scope

Note
Compares already-parsed environment maps; never emits values.

Non-goals

  • Does not validate dotenv syntax (use code.validate_env_file)
  • Does not mutate environments or generate corrected files
  • Does not compare secret values in plaintext

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

validation

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call1 credit

File handling

Accepts file_refProduces file_refMax input256 KB

How we handle your data

Sensitive processing
What this means

This skill is designed to detect, mask, redact, validate, or otherwise process sensitive data.

Squillify guarantees
  • Runs inside Squillify
  • This skill runs inside Squillify.
  • Payloads are not sent to an external service by this skill.
  • Squillify does not permanently store submitted payloads.
  • Telemetry records metadata only, not submitted content.
  • Submitted payloads are not used for training.
  • Submitted payloads are not reviewed by humans.
  • Targets sensitive data
  • The response does not contain submitted content.
Your responsibility

Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.

Read the Microskill Data Handling Policy

Input schema

FieldTypeRequiredDescription
environmentsarrayYesBounded array of named environment variable maps. The item shape is defined by the nested schema and the array contains from 1 through 1000 items.
schemaobjectNoClosed environment-variable schema with required, optional, secret, and equality rule properties; omit it to run presence and drift checks only. Its documented receipt properties are bounded to 256 entries — unconstrained RFC 8259 JSON items.
referenceEnvironmentstringNoOptional reference environment name; omit it to skip reference-equality checks.

Output schema

FieldTypeRequiredDescription
validbooleanYesWhether no error-severity environment finding exists.
environmentsarrayYesBounded normalized environment names in caller order. The item shape is defined by the nested schema and the array contains from 0 through 1000 items.
findingsarrayYesBounded array of safe structured DevOps findings. The item shape is defined by the nested schema and the array contains from 0 through 20000 items.
matrixarrayYesBounded variable-by-environment matrix rows. The item shape is defined by the nested schema and the array contains from 0 through 100000 items.
_metaobjectYesClosed environment validator metadata receipt. Its documented receipt properties are bounded to 256 entries — unconstrained RFC 8259 JSON items.

API contract

POST /v1/execute
curl
curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"devops.validate_env_matrix","input":{"environments":[{"name":"dev","variables":{"A":"1"}}]}}'
Integrations
TypeScript SDK
import { Squillify } from "@squillify/sdk";

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

const { output } = await sq.execute("devops.validate_env_matrix", {"environments":[{"name":"dev","variables":{"API_URL":"http://localhost","LOG_LEVEL":"DEBUG"}},{"name":"prod","variables":{"API_URL":"https://api.example.com"}}],"schema":{"required":["API_URL","LOG_LEVEL"]}});

Errors

CodeHTTPRetryableDescription
VALIDATION_ERROR400NoThe request payload failed schema validation.
UNAUTHORIZED401NoMissing or invalid API key.
SKILL_NOT_ACCESSIBLE403NoThe API key is not granted access to this skill.
SKILL_NOT_AVAILABLE_FOR_PLAN403NoThis skill is not included in your current plan.
PLAN_ELIGIBILITY_UNAVAILABLE503YesPlan eligibility could not be decided. Retry after backoff.
SKILL_NOT_FOUND404NoThe requested skill or version does not exist.
TENANT_RATE_LIMITED429YesRequest rate limit exceeded. Retry after backoff.
QUOTA_EXCEEDED429YesPlan quota exhausted. Retryable once the quota period resets.
EXECUTION_TIMEOUT504YesExecution exceeded the allowed time budget.
ENV_MATRIX_LIMIT_EXCEEDED429NoA size, quota, rate, or time limit was exceeded.
ENV_SCHEMA_INVALID400NoThe request payload failed this skill's input validation.
ENV_ENVIRONMENT_NAME_DUPLICATE400NoThe request payload failed this skill's input validation.

Other limits

LimitValue
Recommended inline bytes32 KiB

Limitations

  • Does not validate dotenv syntax (use code.validate_env_file)
  • Does not mutate environments or generate corrected files
  • Does not compare secret values in plaintext
  • Parsing raw .env file syntax
  • Generating corrected environment files

How to call

POST /v1/execute (requires authentication)

Request bodyjson
{
  "skillKey": "devops.validate_env_matrix",
  "input": {
    "environments": [
      {
        "name": "dev",
        "variables": {
          "API_URL": "http://localhost",
          "LOG_LEVEL": "DEBUG"
        }
      },
      {
        "name": "prod",
        "variables": {
          "API_URL": "https://api.example.com"
        }
      }
    ],
    "schema": {
      "required": [
        "API_URL",
        "LOG_LEVEL"
      ]
    }
  }
}

Examples

Missing required key in prod

Inputjson
{
  "environments": [
    {
      "name": "dev",
      "variables": {
        "API_URL": "http://localhost",
        "LOG_LEVEL": "DEBUG"
      }
    },
    {
      "name": "prod",
      "variables": {
        "API_URL": "https://api.example.com"
      }
    }
  ],
  "schema": {
    "required": [
      "API_URL",
      "LOG_LEVEL"
    ]
  }
}
Expected outputjson
{
  "findings": [
    {
      "details": {
        "environment": "prod",
        "key": "LOG_LEVEL"
      },
      "path": "prod/LOG_LEVEL",
      "code": "ENV_KEY_MISSING",
      "message": "Key 'LOG_LEVEL' is declared required but absent in 'prod'.",
      "severity": "error"
    }
  ],
  "matrix": [
    {
      "missingFrom": [],
      "key": "API_URL",
      "presentIn": [
        "dev",
        "prod"
      ],
      "secret": false,
      "distinctValueCount": 2,
      "identicalAcross": false
    },
    {
      "missingFrom": [
        "prod"
      ],
      "key": "LOG_LEVEL",
      "presentIn": [
        "dev"
      ],
      "secret": false,
      "distinctValueCount": 1,
      "identicalAcross": false
    }
  ],
  "valid": false,
  "_meta": {
    "comparisonsPerformed": 1,
    "environmentCount": 2,
    "keyCount": 2
  },
  "environments": [
    "dev",
    "prod"
  ]
}

Secret reused across staging and prod

Inputjson
{
  "environments": [
    {
      "name": "staging",
      "variables": {
        "DB_PASSWORD": "same-secret"
      }
    },
    {
      "name": "prod",
      "variables": {
        "DB_PASSWORD": "same-secret"
      }
    }
  ],
  "schema": {
    "secret": [
      "DB_PASSWORD"
    ]
  }
}
Expected outputjson
{
  "findings": [
    {
      "details": {
        "key": "DB_PASSWORD",
        "environments": [
          "staging",
          "prod"
        ]
      },
      "path": "DB_PASSWORD",
      "code": "ENV_SECRET_REUSED",
      "message": "Secret key 'DB_PASSWORD' has the same value across environments.",
      "severity": "error"
    }
  ],
  "matrix": [
    {
      "missingFrom": [],
      "key": "DB_PASSWORD",
      "presentIn": [
        "staging",
        "prod"
      ],
      "secret": true,
      "distinctValueCount": 1,
      "identicalAcross": true
    }
  ],
  "valid": false,
  "_meta": {
    "comparisonsPerformed": 1,
    "environmentCount": 2,
    "keyCount": 1
  },
  "environments": [
    "staging",
    "prod"
  ]
}
  • dev/staging/prod drift detection
  • Secret-reuse detection across environments

Avoid for

  • Parsing raw .env file syntax
  • Generating corrected environment files

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

dotenvvalidationconfigenvironment