Date Conflict Detector
time.detect_date_conflicts
Overview
Detects overlaps among caller-supplied time intervals and reports each conflicting pair with the overlapping window and its length in seconds. Endpoints may carry any offset or none — everything is compared on the instant timeline, so a Brussels meeting and a New York one are compared correctly. 'boundaryPolicy' decides whether intervals that merely touch conflict: 'half_open' (default) says they do not, 'closed' says they do. 'groupBy' names a field so that only intervals sharing that value are compared, which is how per-resource conflicts are checked. Detection is a sweep line, and conflicts are emitted in a stable order, so shuffling the input cannot change the output. This reports clashes; it does not schedule, resolve, or suggest alternatives.
Overlap detection has subtle rules — we make boundary policy, grouping, and stable output ordering explicit so you get every clash and its window.
Reliability
Same intervals, same conflicts — no clock is read, and the output order is part of the contract, by overlapStart then left id then right id, so shuffling your array cannot change the answer. Everything is compared as instants, so a Brussels booking and a New York one are compared correctly rather than by wall-clock text. Finding no conflict is a normal success, so branch on hasConflicts rather than on your error path, and check truncated before you treat the list as complete. TIMEZONE_UNKNOWN — trigger: the zone field is not a zone we can resolve, which covers a typo, a three-letter abbreviation such as CST, and a fixed offset such as +02:00; retryable: no, the same value always fails; next: send a region-based identifier like Europe/Brussels or UTC, or write your endpoints with explicit offsets so no default zone is needed. INTERVAL_ID_DUPLICATE — trigger: two intervals carry the same id, which would make a reported conflict impossible to trace back; retryable: no; next: make the ids unique within the call — the message names the position of the second one — and if you meant to group them, use groupBy instead. INTERVAL_END_BEFORE_START — trigger: an interval whose end is earlier than its start, usually a swapped pair or a missing day rollover at midnight; retryable: no; next: fix that interval — the message names its position — remembering that an interval ending exactly when it starts is allowed.
Context footprint
One call replaces an O(n²) comparison an agent would have to narrate; the response lists only the pairs that actually clash. A successful call costs 1 execution credit.
When to use it
When you hold concrete intervals and need to know which pairs overlap and by how much.
Do not use to find free slots, expand recurrence rules first (use time.generate_recurrence), or resolve conflicts automatically.
Scope
Non-goals
- Does not schedule, resolve conflicts, or suggest alternative slots
- Does not compute free slots or availability
- Does not expand recurrence rules — callers pass concrete intervals
- Does not rank or prioritise conflicts
- Does not read the system clock
Properties
Capabilities
Cost & billing
Flat rate per invocation
File handling
How we handle your data
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.
Input schema
| Field | Type | Required | Description |
|---|---|---|---|
| intervals | array | Yes | From 0 through 1,000 closed intervals, each with an identifier and ISO start and end endpoints. |
| boundaryPolicy | string | No | Touching-interval rule; omit it for half_open. |
| groupBy | string | No | Interval grouping-field name; omit it to compare every interval in one pool. |
| zone | string | No | Default IANA zone; omit it for UTC. |
Output schema
| Field | Type | Required | Description |
|---|---|---|---|
| hasConflicts | boolean | Yes | Whether a conflicting pair exists. |
| conflictCount | integer | Yes | Returned conflict-pair count. |
| conflicts | array | Yes | From 0 through the bounded conflict cap of ordered pairs, each a closed overlapping interval pair. |
| truncated | boolean | Yes | Whether conflicts exceeded the cap. |
| intervalCount | integer | Yes | Read interval count. |
| boundaryPolicy | string | Yes | Applied boundary rule. |
| _meta | object | No | Closed sweep-work receipt reporting how many interval comparisons the pass performed. |
API contract
POST /v1/executecurl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"time.detect_date_conflicts","input":{"intervals":[{"id":"a","start":"2026-03-02T09:00:00Z","end":"2026-03-02T10:00:00Z"},{"id":"b","start":"2026-03-02T09:30:00Z","end":"2026-03-02T11:00:00Z"}]}}'import { Squillify } from "@squillify/sdk";
const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });
const { output } = await sq.execute("time.detect_date_conflicts", {"intervals":[{"end":"2026-03-02T10:00:00Z","start":"2026-03-02T09:00:00Z","id":"a"},{"end":"2026-03-02T11:00:00Z","start":"2026-03-02T09:30:00Z","id":"b"}]});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. |
| INTERVAL_END_BEFORE_START | 400 | No | The request payload failed this skill's input validation. |
| INTERVAL_ID_DUPLICATE | 400 | No | The request payload failed this skill's input validation. |
| TIMEZONE_UNKNOWN | 400 | No | The request payload failed this skill's input validation. |
Other limits
| Limit | Value |
|---|---|
| Recommended inline bytes | 32 KiB |
Limitations
- Does not schedule, resolve conflicts, or suggest alternative slots
- Does not compute free slots or availability
- Does not expand recurrence rules — callers pass concrete intervals
- Does not rank or prioritise conflicts
- Does not read the system clock
- Finding a free slot for a new meeting
- Expanding a recurring series first (use time.generate_recurrence)
- Resolving a conflict once found
How to call
POST /v1/execute (requires authentication)
{
"skillKey": "time.detect_date_conflicts",
"input": {
"intervals": [
{
"end": "2026-03-02T10:00:00Z",
"start": "2026-03-02T09:00:00Z",
"id": "a"
},
{
"end": "2026-03-02T11:00:00Z",
"start": "2026-03-02T09:30:00Z",
"id": "b"
}
]
}
}Examples
Two meetings overlap by half an hour
{
"intervals": [
{
"end": "2026-03-02T10:00:00Z",
"start": "2026-03-02T09:00:00Z",
"id": "a"
},
{
"end": "2026-03-02T11:00:00Z",
"start": "2026-03-02T09:30:00Z",
"id": "b"
}
]
}{
"_meta": {
"comparisons": 1
},
"truncated": false,
"conflicts": [
{
"left": "a",
"overlapSeconds": 1800,
"overlapStart": "2026-03-02T09:30:00Z",
"overlapEnd": "2026-03-02T10:00:00Z",
"right": "b"
}
],
"hasConflicts": true,
"boundaryPolicy": "half_open",
"conflictCount": 1,
"intervalCount": 2
}Touching intervals conflict only under the closed policy
{
"intervals": [
{
"end": "2026-03-02T10:00:00Z",
"start": "2026-03-02T09:00:00Z",
"id": "a"
},
{
"end": "2026-03-02T11:00:00Z",
"start": "2026-03-02T10:00:00Z",
"id": "b"
}
],
"boundaryPolicy": "closed"
}{
"_meta": {
"comparisons": 1
},
"truncated": false,
"conflicts": [
{
"left": "a",
"overlapSeconds": 0,
"overlapStart": "2026-03-02T10:00:00Z",
"overlapEnd": "2026-03-02T10:00:00Z",
"right": "b"
}
],
"hasConflicts": true,
"boundaryPolicy": "closed",
"conflictCount": 1,
"intervalCount": 2
}Recommended use cases
- Check a proposed booking set for double-booked rooms with groupBy
- Validate that shift assignments for one person do not overlap
- Find where two imported calendars collide before merging them
Avoid for
- Finding a free slot for a new meeting
- Expanding a recurring series first (use time.generate_recurrence)
- Resolving a conflict once found
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.