YAML Schema Validator

Overview

You send YAML text and a JSON Schema, and we read the YAML with a parser that will not build arbitrary objects, will not follow custom tags, and gives up on the alias and nesting tricks that turn a small file into a memory bomb. What comes out is checked against your schema, and every problem is reported with the path inside the document, the rule that rejected it, and a readable message. We check structure and values, not indentation style or comment placement.

Most of what runs your infrastructure is a YAML file, and the usual way to find a mistake in one is to apply it. Checking it against a schema first is cheaper, and doing so with a parser that refuses to instantiate objects keeps an untrusted file from becoming an execution path.

When to use it

Scope

Non-goals

• We never pull in another schema document, so send a self-contained schema
• We never build custom objects from YAML tags; only plain data comes out
• We never comment on style, indentation, or key ordering

Properties

Capabilities

Cost & billing

Flat rate per invocation

File handling

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":"schema.validate_yaml_schema","input":{"yaml":"name: Alice\nage: 30","schema":{"type":"object","required":["name"],"properties":{"name":{"type":"string"}}}}}'

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

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

const { output } = await sq.execute("schema.validate_yaml_schema", {"yaml":"name: Alice\nage: 30\n","schema":{"required":["name"],"type":"object","properties":{"name":{"type":"string"},"age":{"type":"integer"}}}});

Errors

Other limits

Limitations

• We never pull in another schema document, so send a self-contained schema
• We never build custom objects from YAML tags; only plain data comes out
• We never comment on style, indentation, or key ordering
• Judging formatting or style rather than content
• Schemas that only work if another document is fetched

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "schema.validate_yaml_schema",
  "input": {
    "yaml": "name: Alice\nage: 30\n",
    "schema": {
      "required": [
        "name"
      ],
      "type": "object",
      "properties": {
        "name": {
          "type": "string"
        },
        "age": {
          "type": "integer"
        }
      }
    }
  }
}

Examples

{
  "yaml": "name: Alice\nage: 30\n",
  "schema": {
    "required": [
      "name"
    ],
    "type": "object",
    "properties": {
      "name": {
        "type": "string"
      },
      "age": {
        "type": "integer"
      }
    }
  }
}

{
  "errors": [],
  "valid": true,
  "documentCount": 1
}

{
  "yaml": "name: Alice\nage: not-an-int\n",
  "schema": {
    "type": "object",
    "properties": {
      "age": {
        "type": "integer"
      }
    }
  }
}

{
  "errors": [
    {
      "path": "/age",
      "schemaPath": "/properties/age/type",
      "message": "string found, integer expected",
      "keyword": "type"
    }
  ],
  "valid": false,
  "documentCount": 1
}

Recommended use cases

• Check a config or manifest before you deploy it anywhere
• Hold infrastructure-as-code to a schema in review or in CI
• Verify generated YAML against the contract it is supposed to meet

Avoid for

• Judging formatting or style rather than content
• Schemas that only work if another document is fetched

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