team-calendar – Other skill for AI agents

Team Calendar

What it is: Unified view.

Overview

Works out the smallest useful Team Calendar setup for the business in front of it, then

builds it only when asked. The default output is a short recommendation, not a

spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on

request, from one field list so they cannot drift apart.

Layer: Layer 4: Manage. Fits: Growth stage. Table code: n/a.

When to Use This Skill

• team calendar
• shared events calendar
• who is available

Also use it when the user says "unified view", or describes the same process happening in a

spreadsheet, a document or someone inboxes.

Do not use it for: payroll calculation, tax filing, or legal advice. This skill produces

empty templates only - it never holds or processes real employee or customer data.

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

• "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
• "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
• "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
• "how do I ..." -> advice question; answer directly and offer the build only if it helps.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

> Q: What should appear on the shared calendar?

Step 2 - Ask only what is missing

Skip anything the user already answered, in any earlier message. Ask the rest one at a

time, and stop as soon as the remaining answers would not change the output.

• Content - Which events? / Holidays included? / Personal events excluded?
• Visibility - Who sees what? / Department calendars? / Private items?
• Sync - Synced with Google? / Two-way? / Who owns it?
• Current process - How do you share now? / Which calendar? / What is missing?
• Outcome - What do you need? / A calendar view, a feed or conflict rules?

Never invent an answer. If the user does not know, record it as unknown and carry on.

Step 3 - Hold the internal context

Hold the answers in this shape. It stays internal - it is not shown to the user unless

they ask, and it never carries a value the user did not give.

module: team-calendar
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Content": null
  "Visibility": null
  "Sync": null
  "Current process": null
  "Outcome": null
requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: []     # only what the user actually said
open_questions: []      # the unanswered ones, in the order worth asking

Step 4 - Recommend the smallest workflow

If an artifact was requested, build it after resolving essential missing facts. Otherwise give a short recommendation and offer the relevant artifact.

Recommended approach: Keep the calendar in the tool already used and make the database a thin index of it, not a second calendar.

Why this one: Two calendars is worse than one. If a shared calendar already exists, the useful output is a record of key events, not a scheduler.

Workflow: Event created → Calendar entry → Attendance or RSVP → Reminder

Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the

requested artifacts. For machine-readable text, keep prose outside the data; for files,

provide a usable link. Report material validation failures or limitations separately.

**A selected Notion output is rendered by notion-manual-import, so route the

Notion step there.** When the user selects Notion, hand that step to

@notion-manual-import: it holds the CSV, the property

mapping, the import steps and the verification checklist, and it renders the Field

Reference below instead of defining a table of its own. Do not restate the mapping

here and do not improvise the import steps. Manual CSV and mapping outputs need no

connection. For requested workspace changes, follow the shared contract: verify actual

tool access and the target before writing. A user saying "connected" is not tool evidence.

Never ask for a Notion password or token.

For an Excel-compatible CSV, use UTF-8 with a byte order mark so Excel opens the

text correctly. A CSV is not an .xlsx workbook; create .xlsx only when the user

requests a workbook.

A CSV carries no types, so after it, name the columns

that need a number, date or currency format applied.

Event,Event Type,Date,Start Time,End Time,Time Zone,Department,Attendees,Organizer,Source Module,Location or Link,Notes,Event ID
Q1 Town Hall,Meeting,2026-01-15,10:00,11:00,IST (UTC+5:30),Delivery,All employees,Karan Malhotra,Invoices & Billing,https://example.com/calendar/launch-week,February all-hands moved for the client call; the room is double-booked until March.,

CREATE TABLE team_calendar (
  event VARCHAR(255),
  event_type VARCHAR(100) NOT NULL,
  date DATE NOT NULL,
  start_time VARCHAR(255),
  end_time VARCHAR(255),
  time_zone VARCHAR(255),
  department VARCHAR(255),
  attendees VARCHAR(255),
  organizer VARCHAR(255),
  source_module VARCHAR(255),
  location_or_link TEXT,
  notes TEXT,
  event_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Team Calendar",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Event": { "type": "string" },
      "Event Type": { "type": "string" },
      "Date": { "type": "string", "format": "date" },
      "Start Time": { "type": "string" },
      "End Time": { "type": "string" },
      "Time Zone": { "type": "string" },
      "Department": { "type": "string" },
      "Attendees": { "type": "string" },
      "Organizer": { "type": "string" },
      "Source Module": { "type": "string" },
      "Location or Link": { "type": "string", "format": "uri" },
      "Notes": { "type": "string" },
      "Event ID": { "type": "integer" }
  },
  "required": [
      "Event Type",
      "Date"
  ]
}

| CSV column | Notion property | Set after import |
|---|---|---|
| Event | Title | Use as the database title |
| Event Type | Select (add options after import) | Convert to Select, add options: "Meeting", "Deadline", "Leave", "Training", "Travel", "Review" |
| Date | Date | Convert to Date |
| Start Time | Text | Leave as Text |
| End Time | Text | Leave as Text |
| Time Zone | Text | Leave as Text |
| Department | Text | Leave as Text |
| Attendees | Text | Leave as Text |
| Organizer | Text | Leave as Text |
| Source Module | Text | Leave as Text |
| Location or Link | URL | Convert to URL |
| Notes | Text | Leave as Text |
| Event ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |

The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays currency, dates stay date,

and anything pointing at another table stays relation.

Field Reference

| # | Field | Type | SQL | JSON Schema | Notion | CSV example |

|---:|---|---|---|---|---|---|

| 1 | Event | text | VARCHAR(255) | string | Text | Q1 Town Hall |

| 2 | Event Type | select | VARCHAR(100) | string | Select (add options after import) | Meeting |

| 3 | Date | date | DATE | string, format: date | Date | 2026-01-15 |

| 4 | Start Time | text | VARCHAR(255) | string | Text | 10:00 |

| 5 | End Time | text | VARCHAR(255) | string | Text | 11:00 |

| 6 | Time Zone | text | VARCHAR(255) | string | Text | IST (UTC+5:30) |

| 7 | Department | text | VARCHAR(255) | string | Text | Delivery |

| 8 | Attendees | text | VARCHAR(255) | string | Text | All employees |

| 9 | Organizer | text | VARCHAR(255) | string | Text | Karan Malhotra |

| 10 | Source Module | text | VARCHAR(255) | string | Text | Invoices & Billing |

| 11 | Location or Link | url | TEXT | string, format: uri | URL | https://example.com/calendar/launch-week |

| 12 | Notes | long_text | TEXT | string | Text | February all-hands moved for the client call; the room is double-booked until March. |

| 13 | Event ID | id | SERIAL PRIMARY KEY | integer | Text (preserve source ID) | (blank) |

Select Options

Event Type

Meeting | Deadline | Leave | Training | Travel | Review

Relations

Link fields: none

Examples

Prompt

We share a Google Calendar but nobody knows who is on leave.

Context first - one q

… (full content is in the download package)