Skip to main content

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

MicroSkills Reference

Resolve Local Date-Time

time.resolve_local_datetime

ProductionBounded custom (Class B)Deterministicstrictinstantv1.0.0
No network

Overview

You send an ISO local date-time and an IANA zone. A time that occurs once is NORMAL. A fall-back overlap is OVERLAP_EARLIER or OVERLAP_LATER, or refused when disambiguation is REJECT (the default). A spring-forward gap is refused unless disambiguation is NEXT_VALID, which shifts forward by the gap and returns GAP_SHIFTED. This is not natural-language parsing and not recurrence expansion.

A local reading is not always one instant. Naming REJECT, EARLIER, LATER or NEXT_VALID makes the gap and overlap choice a contract instead of a silent guess.

Reliability

Default disambiguation is REJECT, so an overlap or gap is a typed failure until you choose a branch. NEXT_VALID on a gap uses the same forward shift as java.time atZone. TIMEZONE_UNKNOWN — trigger: zoneId is not a resolvable IANA region id; retryable: no; next: send Europe/Brussels or UTC. DATETIME_FORMAT_INVALID — trigger: localDateTime is not an ISO local date-time; retryable: no; next: send 2026-10-25T02:30:00 without an offset. DATETIME_AMBIGUOUS — trigger: the reading happens twice and disambiguation is REJECT; retryable: no; next: resend EARLIER or LATER. DATETIME_NONEXISTENT — trigger: the reading never happens and disambiguation is not NEXT_VALID; retryable: no; next: resend NEXT_VALID or correct the wall time.

Context footprint

One local reading and one zone in. A successful call costs 1 execution credit.

When to use it

When you hold a zone-less local date-time and must say how DST gaps and overlaps resolve.

When you already have an instant, or you need to convert that instant into another zone.

Scope

Note
Maps one timezone-local date-time to an instant under an explicit DST policy.

Non-goals

  • Does not parse natural-language dates (use time.parse_datetime)
  • Does not convert between two zones (use time.convert_timezone)

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

analysisnormalization

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call1 credit

File handling

Accepts file_refProduces file_refMax input2 KB

How we handle your data

Sensitive input, safe output
What this means

This skill may receive sensitive content, but it does not target sensitive data and returns only a structured non-sensitive result.

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 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
localDateTimestringYesISO local date-time without offset.
zoneIdstringYesIANA region zone or UTC.
disambiguationstringNoGap and overlap policy; omit it for REJECT.

Output schema

FieldTypeRequiredDescription
instantstringYesResolved UTC instant.
offsetstringYesUTC offset as ±HH:MM[:SS].
offsetSecondsintegerYesThe same UTC offset expressed as a signed count of seconds, including sub-minute offsets.
zoneIdstringYesCanonical IANA zone.
resolutionstringYesHow the local reading was resolved.
candidateOffsetsarrayYesFrom 0 through 4 offset strings: valid overlap offsets, or the transition before/after pair on a gap.
shiftSecondsintegerYesGap shift in seconds.
_metaobjectYesClosed applied tzdb receipt naming the IANA tzdbVersion used.

API contract

POST /v1/execute
curl
curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"time.resolve_local_datetime","input":{"localDateTime":"2026-01-15T12:00:00","zoneId":"Europe/Brussels"}}'
Integrations
TypeScript SDK
import { Squillify } from "@squillify/sdk";

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

const { output } = await sq.execute("time.resolve_local_datetime", {"localDateTime":"2026-01-15T12:00:00","zoneId":"Europe/Brussels"});

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.
TIMEZONE_UNKNOWN400NoThe request payload failed this skill's input validation.
DATETIME_FORMAT_INVALID400NoThe request payload failed this skill's input validation.
DATETIME_AMBIGUOUS412NoThe input is valid but cannot be processed as-is.
DATETIME_NONEXISTENT412NoThe input is valid but cannot be processed as-is.

Other limits

LimitValue
Recommended inline bytes32 KiB

Limitations

  • Does not parse natural-language dates (use time.parse_datetime)
  • Does not convert between two zones (use time.convert_timezone)
  • Reading the offset of an instant you already hold (use time.timezone_offset_at)
  • Guessing a zone from a city name

How to call

POST /v1/execute (requires authentication)

Request bodyjson
{
  "skillKey": "time.resolve_local_datetime",
  "input": {
    "localDateTime": "2026-01-15T12:00:00",
    "zoneId": "Europe/Brussels"
  }
}

Examples

Ordinary winter time in Brussels

Inputjson
{
  "localDateTime": "2026-01-15T12:00:00",
  "zoneId": "Europe/Brussels"
}
Expected outputjson
{
  "offsetSeconds": 3600,
  "resolution": "NORMAL",
  "candidateOffsets": [
    "+01:00"
  ],
  "shiftSeconds": 0,
  "instant": "2026-01-15T11:00:00Z",
  "offset": "+01:00",
  "_meta": {
    "tzdbVersion": "2026b"
  },
  "zoneId": "Europe/Brussels"
}
Tip
12:00 CET is 11:00 UTC, and the reading occurs once

Later pass of the Brussels autumn overlap

Inputjson
{
  "localDateTime": "2026-10-25T02:30:00",
  "disambiguation": "LATER",
  "zoneId": "Europe/Brussels"
}
Expected outputjson
{
  "offsetSeconds": 3600,
  "resolution": "OVERLAP_LATER",
  "candidateOffsets": [
    "+02:00",
    "+01:00"
  ],
  "shiftSeconds": 0,
  "instant": "2026-10-25T01:30:00Z",
  "offset": "+01:00",
  "_meta": {
    "tzdbVersion": "2026b"
  },
  "zoneId": "Europe/Brussels"
}
Tip
02:30 happens twice; LATER takes the post-transition +01:00 pass
  • Turning a wall-clock booking into an instant when DST may fold or skip an hour
  • Choosing the later overlap pass, or the next valid time after a spring gap

Avoid for

  • Reading the offset of an instant you already hold (use time.timezone_offset_at)
  • Guessing a zone from a city name

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

normalizationdate-time