Skip to main content

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

MicroSkills Reference

Docker Compose Parser

devops.parse_docker_compose

ProductionBounded custom (Class B)Deterministicstrictfastv1.0.0
No network

Overview

You pass a Docker Compose YAML document and we return a normalized summary: services, images, ports, volumes, environment keys, dependencies, and networks, plus structural conflict findings. Environment values are never emitted — only keys. We do not run docker compose or contact a daemon; variable substitution uses only values you supply. Do not use this for live daemon validation or secret extraction.

Ad-hoc YAML parsing drops short/long port forms and leaks env values into logs. We normalize structure and keep secrets out of the response.

Reliability

STRICT and deterministic. Alias bombs and deep nesting are refused before interpretation. Domain errors (not retryable — fix input): COMPOSE_YAML_INVALID (YAML cannot be parsed — correct the document); COMPOSE_STRUCTURE_INVALID (valid YAML but not a Compose shape — fix structure); COMPOSE_SERVICE_LIMIT_EXCEEDED (too many services — split the file); YAML_ALIAS_LIMIT_EXCEEDED (YAML alias expansion limit hit — remove alias chains). Warnings such as COMPOSE_IMAGE_UNTAGGED appear in findings[] and do not fail the call.

Context footprint

One call replaces ad-hoc YAML parsing and port-conflict scanning. A successful call costs 1 execution credit.

When to use it

When you need a normalized inventory of a Compose file without executing it.

When you need live daemon validation or actual environment values.

Scope

Note
Parses one Compose document into a structural inventory and conflict findings.

Non-goals

  • Does not run docker compose or contact a daemon
  • Does not pull or inspect images
  • Does not interpolate from the server environment
  • Does not emit environment values — only keys

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

parsingvalidation

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call1 credit

File handling

Accepts file_refProduces file_refMax input512 KB

How we handle your data

Sensitive output possible
What this means

This skill may receive sensitive content and may return submitted, transformed, extracted, or reformatted content.

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.
  • This skill does not target sensitive data.
  • Output may reveal sensitive derived information
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
composestringYesDocker Compose YAML parsed without starting containers.
variablesobjectNoPurpose-bound bounded interpolation-variable map; omit it to interpolate no variables. It contains from 0 through 10,000 string-valued properties.
optionsobjectNoPurpose-bound bounded Compose parser options; omit it for safe defaults. Its purpose-bound option properties are bounded to 128 entries — unconstrained RFC 8259 JSON items.

Output schema

FieldTypeRequiredDescription
versionstringNoDeclared Compose version when present.
servicesarrayYesBounded parsed service receipts. The item shape is defined by the nested schema and the array contains from 0 through 100000 items.
networksarrayYesBounded parsed network receipts. The item shape is defined by the nested schema and the array contains from 0 through 100000 items.
volumesarrayYesBounded parsed volume receipts. The item shape is defined by the nested schema and the array contains from 0 through 100000 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.
_metaobjectYesClosed Compose parser 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.parse_docker_compose","input":{"compose":"services:\n  api:\n    image: nginx:1.27\n"}}'
Integrations
TypeScript SDK
import { Squillify } from "@squillify/sdk";

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

const { output } = await sq.execute("devops.parse_docker_compose", {"compose":"services:\n  api:\n    image: nginx:1.27\n    ports:\n      - \"8080:80\"\n"});

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.
COMPOSE_YAML_INVALID400NoThe request payload failed this skill's input validation.
COMPOSE_STRUCTURE_INVALID400NoThe request payload failed this skill's input validation.
COMPOSE_SERVICE_LIMIT_EXCEEDED429NoA size, quota, rate, or time limit was exceeded.
YAML_ALIAS_LIMIT_EXCEEDED422NoThe input was rejected as unsafe.

Other limits

LimitValue
Recommended inline bytes32 KiB

Limitations

  • Does not run docker compose or contact a daemon
  • Does not pull or inspect images
  • Does not interpolate from the server environment
  • Does not emit environment values — only keys
  • Runtime compose validation against a live daemon
  • Reading secret values from environment blocks

How to call

POST /v1/execute (requires authentication)

Request bodyjson
{
  "skillKey": "devops.parse_docker_compose",
  "input": {
    "compose": "services:\n  api:\n    image: nginx:1.27\n    ports:\n      - \"8080:80\"\n"
  }
}

Examples

Single service with a published port

Inputjson
{
  "compose": "services:\n  api:\n    image: nginx:1.27\n    ports:\n      - \"8080:80\"\n"
}
Expected outputjson
{
  "networks": [],
  "_meta": {
    "unresolvedVariables": [],
    "documentCount": 1,
    "serviceCount": 1
  },
  "volumes": [],
  "services": [
    {
      "name": "api",
      "image": {
        "raw": "nginx:1.27",
        "repository": "nginx",
        "tag": "1.27"
      },
      "ports": [
        {
          "published": "8080",
          "target": 80,
          "protocol": "tcp"
        }
      ],
      "volumes": [],
      "environmentKeys": [],
      "dependsOn": [],
      "networks": [
        "default"
      ]
    }
  ],
  "findings": []
}

Environment keys listed without values

Inputjson
{
  "compose": "services:\n  web:\n    image: nginx\n    environment:\n      API_KEY: secret\n      DEBUG: \"1\"\n"
}
Expected outputjson
{
  "networks": [],
  "_meta": {
    "unresolvedVariables": [],
    "documentCount": 1,
    "serviceCount": 1
  },
  "volumes": [],
  "services": [
    {
      "volumes": [],
      "environmentKeys": [
        "API_KEY",
        "DEBUG"
      ],
      "dependsOn": [],
      "networks": [
        "default"
      ],
      "name": "web",
      "image": {
        "repository": "nginx",
        "raw": "nginx"
      },
      "ports": []
    }
  ],
  "findings": [
    {
      "details": {
        "service": "web"
      },
      "path": "/services/web/image",
      "code": "COMPOSE_IMAGE_UNTAGGED",
      "message": "Service 'web' image has neither a tag nor a digest.",
      "severity": "warning"
    }
  ]
}
  • Pre-flight structural review of Compose files before deploy
  • Extracting service, image, and port inventory for agents

Avoid for

  • Runtime compose validation against a live daemon
  • Reading secret values from environment blocks

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

yamldockerparsingvalidationcompose