Healthcheck Generator

devops.generate_healthcheck

ProductionBounded custom (Class B)Deterministicstrictinstantv1.0.0

No network

Overview

You declare how your service is reached (HTTP path, TCP port, or exec command) and we generate a deterministic healthcheck configuration for docker_compose, kubernetes, or dockerfile targets using a published timing profile. We return both structured config and paste-ready text. Nothing is probed or contacted. Do not use this when you do not yet know the health endpoint or command.

Agents invent probe timings inconsistently across Compose, Kubernetes, and Dockerfile. We give you one timing table and three paste-ready shapes.

Reliability

STRICT and deterministic; timings come from the published profile table. Domain errors (not retryable — fix input): HEALTHCHECK_TARGET_UNSUPPORTED (target must be docker_compose, kubernetes, or dockerfile); HEALTHCHECK_SERVICE_INCOMPLETE (missing or invalid protocol, port, path, command, or startupSeconds — complete service metadata for the chosen protocol). Self-defeating timings appear in findings[] and do not fail the call.

Context footprint

One call yields structured config and paste-ready rendered text. A successful call costs 1 execution credit.

When to use it

When you know the protocol, port, and path or command and need a scaffold.

When the health endpoint itself is unknown or must be discovered at runtime.

Scope

Note

Generates probe configuration from metadata you declare and a published timing table.

Non-goals

Does not probe or contact the service
Does not infer a health endpoint from source code
Does not guarantee the probe matches your runtime

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

generation

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call1 credit

File handling

Accepts file_refProduces file_refMax input16 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.
The response may contain submitted or transformed 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

Field	Type	Required	Description
service	object	Yes	Closed service endpoint declaration with protocol, host, port, path, and expected status properties. Its documented receipt properties are bounded to 256 entries — unconstrained RFC 8259 JSON items.
target	string	Yes	Output target such as docker, kubernetes, or compose.
profile	string	No	Timing profile; omit it for standard.

Output schema

Field	Type	Required	Description
target	string	Yes	Applied output target.
profile	string	Yes	Applied timing profile.
config	object	Yes	Closed machine-readable healthcheck configuration. Its documented receipt properties are bounded to 256 entries — unconstrained RFC 8259 JSON items.
rendered	string	Yes	Rendered target-specific healthcheck snippet.
findings	array	Yes	Bounded array of safe structured DevOps findings. The item shape is defined by the nested schema and the array contains from 0 through 20000 items.
_meta	object	Yes	Closed generator 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.generate_healthcheck","input":{"service":{"protocol":"http","port":8080,"path":"/health"},"target":"kubernetes"}}'

Integrations

TypeScript SDK

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

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

const { output } = await sq.execute("devops.generate_healthcheck", {"service":{"name":"api","path":"/actuator/health","protocol":"http","startupSeconds":30,"port":8080},"profile":"balanced","target":"kubernetes"});

Errors

Code	HTTP	Retryable	Description
VALIDATION_ERROR	400	No	The request payload failed schema validation.
UNAUTHORIZED	401	No	Missing or invalid API key.
SKILL_NOT_ACCESSIBLE	403	No	The API key is not granted access to this skill.
SKILL_NOT_AVAILABLE_FOR_PLAN	403	No	This skill is not included in your current plan.
PLAN_ELIGIBILITY_UNAVAILABLE	503	Yes	Plan eligibility could not be decided. Retry after backoff.
SKILL_NOT_FOUND	404	No	The requested skill or version does not exist.
TENANT_RATE_LIMITED	429	Yes	Request rate limit exceeded. Retry after backoff.
QUOTA_EXCEEDED	429	Yes	Plan quota exhausted. Retryable once the quota period resets.
EXECUTION_TIMEOUT	504	Yes	Execution exceeded the allowed time budget.
HEALTHCHECK_TARGET_UNSUPPORTED	400	No	The skill does not support the requested variant.
HEALTHCHECK_SERVICE_INCOMPLETE	400	No	The request payload failed this skill's input validation.

Other limits

Limit	Value
Recommended inline bytes	32 KiB

Limitations

Does not probe or contact the service
Does not infer a health endpoint from source code
Does not guarantee the probe matches your runtime
Discovering the correct health URL from application code
Validating that a running service responds to the probe

How to call

POST /v1/execute (requires authentication)

Request bodyjson

{
  "skillKey": "devops.generate_healthcheck",
  "input": {
    "service": {
      "name": "api",
      "path": "/actuator/health",
      "protocol": "http",
      "startupSeconds": 30,
      "port": 8080
    },
    "profile": "balanced",
    "target": "kubernetes"
  }
}

Examples

Kubernetes HTTP probes with balanced timings

Inputjson

{
  "service": {
    "name": "api",
    "path": "/actuator/health",
    "protocol": "http",
    "startupSeconds": 30,
    "port": 8080
  },
  "profile": "balanced",
  "target": "kubernetes"
}

Expected outputjson

{
  "findings": [],
  "_meta": {
    "timingProfile": "balanced-v1"
  },
  "profile": "balanced",
  "target": "kubernetes",
  "config": {
    "startupProbe": {
      "httpGet": {
        "port": 8080,
        "path": "/actuator/health"
      },
      "failureThreshold": 6,
      "periodSeconds": 5
    },
    "readinessProbe": {
      "httpGet": {
        "port": 8080,
        "path": "/actuator/health"
      },
      "periodSeconds": 5,
      "timeoutSeconds": 2,
      "failureThreshold": 2
    },
    "livenessProbe": {
      "httpGet": {
        "port": 8080,
        "path": "/actuator/health"
      },
      "periodSeconds": 10,
      "timeoutSeconds": 2,
      "failureThreshold": 3
    }
  },
  "rendered": "livenessProbe:\n  httpGet:\n    path: /actuator/health\n    port: 8080\n  periodSeconds: 10\n  timeoutSeconds: 2\n  failureThreshold: 3\nreadinessProbe:\n  httpGet:\n    path: /actuator/health\n    port: 8080\n  periodSeconds: 5\n  timeoutSeconds: 2\n  failureThreshold: 2\nstartupProbe:\n  httpGet:\n    path: /actuator/health\n    port: 8080\n  periodSeconds: 5\n  failureThreshold: 6\n"
}

Docker Compose HTTP healthcheck