Meeting Time Allocator

Overview

You send the length of the meeting and its already selected topics, some with fixed minutes and some to be given a share, and we return the allocation with every entry's minutes, offset and optional local start. The arithmetic is largest-remainder apportionment over whole minutes, published step by step so you can reproduce it by hand. Nothing is silently dropped or shrunk: a request whose numbers cannot work comes back as a typed refusal that reports what was required and what was available.

Splitting a meeting evenly has several defensible answers, and two agents that each invent one will disagree about the same meeting.

When to use it

Scope

Non-goals

• Does not create, send or store a calendar invitation of any kind
• Does not select, infer, rewrite or assess the importance of meeting topics
• Does not create an agenda, goals, outcomes, facilitators or pre-reading
• Treats every caller-supplied title as an opaque Unicode label
• Does not use a clock; startTime is a local label you supply
• Does not shrink or drop a topic to make the numbers work

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":"productivity.allocate_meeting_time","input":{"totalMinutes":60,"topics":[{"title":"Q3 pipeline"},{"title":"Hiring plan"},{"title":"Budget review"}]}}'

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

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

const { output } = await sq.execute("productivity.allocate_meeting_time", {"totalMinutes":60,"topics":[{"title":"Q3 pipeline"},{"title":"Hiring plan"},{"title":"Budget review"}]});

Errors

Other limits

Limitations

• Does not create, send or store a calendar invitation of any kind
• Does not select, infer, rewrite or assess the importance of meeting topics
• Does not create an agenda, goals, outcomes, facilitators or pre-reading
• Treats every caller-supplied title as an opaque Unicode label
• Does not use a clock; startTime is a local label you supply
• Does not shrink or drop a topic to make the numbers work
• Choosing the topics themselves, which is a judgement this does not make
• Creating or improving an agenda, which requires semantic judgement
• Scheduling the meeting into a calendar, which nothing here touches

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "productivity.allocate_meeting_time",
  "input": {
    "totalMinutes": 60,
    "topics": [
      {
        "title": "Q3 pipeline"
      },
      {
        "title": "Hiring plan"
      },
      {
        "title": "Budget review"
      }
    ]
  }
}

Examples

{
  "totalMinutes": 60,
  "topics": [
    {
      "title": "Q3 pipeline"
    },
    {
      "title": "Hiring plan"
    },
    {
      "title": "Budget review"
    }
  ]
}

{
  "summary": {
    "topicCount": 3,
    "fixedCount": 0,
    "flexibleCount": 3,
    "breakCount": 0,
    "ordering": "INPUT_ORDER",
    "roundingUnit": "ONE_MINUTE",
    "minTopicMinutes": 5,
    "remainderMinutes": 0,
    "unallocatedMinutes": 0
  },
  "allocation": {
    "totalMinutes": 60,
    "allocatedMinutes": 60,
    "entries": [
      {
        "position": 0,
        "type": "TOPIC",
        "title": "Q3 pipeline",
        "minutes": 20,
        "offsetMinutes": 0,
        "allocation": "FLEXIBLE",
        "remainderMinutesAdded": 0
      },
      {
        "position": 1,
        "type": "TOPIC",
        "title": "Hiring plan",
        "minutes": 20,
        "offsetMinutes": 20,
        "allocation": "FLEXIBLE",
        "remainderMinutesAdded": 0
      },
      {
        "position": 2,
        "type": "TOPIC",
        "title": "Budget review",
        "minutes": 20,
        "offsetMinutes": 40,
        "allocation": "FLEXIBLE",
        "remainderMinutesAdded": 0
      }
    ]
  }
}

{
  "topics": [
    {
      "title": "Q3 pipeline"
    },
    {
      "title": "Hiring plan"
    }
  ],
  "breaks": [
    {
      "minutes": 10,
      "afterPosition": 1
    }
  ],
  "startTime": "09:00",
  "totalMinutes": 60
}

{
  "summary": {
    "topicCount": 2,
    "fixedCount": 0,
    "flexibleCount": 2,
    "breakCount": 1,
    "ordering": "INPUT_ORDER",
    "roundingUnit": "ONE_MINUTE",
    "minTopicMinutes": 5,
    "remainderMinutes": 0,
    "unallocatedMinutes": 0
  },
  "allocation": {
    "totalMinutes": 60,
    "allocatedMinutes": 60,
    "entries": [
      {
        "position": 0,
        "type": "TOPIC",
        "title": "Q3 pipeline",
        "minutes": 25,
        "offsetMinutes": 0,
        "startsAt": "09:00",
        "allocation": "FLEXIBLE",
        "remainderMinutesAdded": 0
      },
      {
        "position": 1,
        "type": "BREAK",
        "title": "Break",
        "minutes": 10,
        "offsetMinutes": 25,
        "startsAt": "09:25",
        "allocation": "BREAK",
        "remainderMinutesAdded": 0
      },
      {
        "position": 2,
        "type": "TOPIC",
        "title": "Hiring plan",
        "minutes": 25,
        "offsetMinutes": 35,
        "startsAt": "09:35",
        "allocation": "FLEXIBLE",
        "remainderMinutesAdded": 0
      }
    ]
  }
}

Recommended use cases

• Give an agent a defensible timebox per topic that adds up to the meeting length
• Recompute timeboxes after a topic gains fixed minutes, without hand arithmetic

Avoid for

• Choosing the topics themselves, which is a judgement this does not make
• Creating or improving an agenda, which requires semantic judgement
• Scheduling the meeting into a calendar, which nothing here touches

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