Research calendar

What this skill teaches

Workflow

1. 1

   List a bounded date window with the narrowest useful Project, company, event-type, status, or importance filters.

2. 2

   Open a selected event before editing it.

3. 3

   Use startDate and endDate for all-day events. Use startsAt, endsAt, and an IANA timezone for timed events.

4. 4

   Link authorized companies, sources, documents, articles, artifacts, or URLs when they support the event.

5. 5

   Read the latest updatedAt before updating. Delete only after explicit user approval with confirm true.

Tool routing

Safety boundaries

---
name: prism-research-calendar
description: "Use when an AI client needs to read, create, or update dated Prism research events with correct date and evidence links."
---

# Research calendar

Plan earnings, milestones, and research deadlines with dates and source links.

## Before you start

Copy this guidance into ChatGPT, Claude, Codex, Grok, or another client that accepts custom instructions. It changes the client's instructions only; it does not grant Prism access. Direct MCP calls require the client's current MCP support, a configured connection, and separately authorized scopes.

Scopes this workflow may need:

- `calendar:read`
- `calendar:write`

The installed skill does not grant these permissions. Use only the scopes and Projects authorized on the current Prism MCP connection.

## Workflow

1. List a bounded date window with the narrowest useful Project, company, event-type, status, or importance filters.
2. Open a selected event before editing it.
3. Use startDate and endDate for all-day events. Use startsAt, endsAt, and an IANA timezone for timed events.
4. Link authorized companies, sources, documents, articles, artifacts, or URLs when they support the event.
5. Read the latest updatedAt before updating. Delete only after explicit user approval with confirm true.

## Tool routing

- `list_calendar_events`, `get_calendar_event`: Find the correct event and its latest complete state.
- `create_calendar_event`: Create a personal or Project event with the correct date model.
- `update_calendar_event`: Apply a described change with the latest concurrency token.
- `delete_calendar_event`: Delete only after explicit confirmation; Prism retains immutable history.

## Expected result

- Events use consistent date precision, timezone, status, importance, and company or Project context.
- Preparation notes and expected impact remain distinct from the actual outcome.
- Every edit preserves the latest event version and linked evidence.

## Boundaries

- A skill does not grant Prism access. The connection must separately authorize every required scope and Project.
- Call only tools verified callable by the current AI host. Use discover_prism_actions for granular actions. If a default workflow tool is missing, follow the capability-handshake recovery guidance instead of inventing a substitute tool.
- Read before writing. Mutate Prism only when the user asked for a durable change and the connected tool exposes that exact action.
- Keep retrieved evidence separate from analysis. Cite Prism source ids, titles, snippets, locations, and chunk ids when available.
- Calendar events are scheduled dates, not a substitute for recurring Project watchlist monitoring.
- Do not infer exact timing when the source supports only a month, quarter, or year. Preserve date precision.
- Deletion requires the user's explicit approval, the latest updatedAt, and confirm true.