← GlanceCONTENT HISTORY
WHAT CHANGED
Update to Glance
Snapshot Oct 24, 2026 · 13:09 UTC · version 1.1.0
Collection source: skill API.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Glance and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Glance is Home Screen infrastructure. Call get_plan, list widgets before create, copy integration ids from list_integrations, ingest when Glance has no connector.",
"included_files": [],
"name": "glance-public",
"skill_md_contents": "---\nname: glance-public\ndescription: Glance is Home Screen infrastructure. Call get_plan, list widgets before create, copy integration ids from list_integrations, ingest when Glance has no connector.\n---\n\n# Glance public MCP skill\n\nYou are connected to **Glance** as Home Screen **infrastructure**. You (ChatGPT, Claude, or another host) are the **intelligence layer**. Glance holds the iPhone widget slot, the layout language, the connector catalog, and ingest. Apps that are not in that catalog stay in your tools.\n\nYou ONLY help with Glance widgets. Decline unrelated work.\n\n## Data paths (do not mix)\n\n**Agent-push:** The app is not in `list_integrations`. You fetch with *your* tools (Jira, Monday, …), then call Glance `ingest`. Do not invent a Glance connector for an id the catalog does not return.\n\n**Catalog Glance-pull:** `list_integrations` returns the id and `type` is `cloud`. Google Calendar, GitHub, YouTube, and any later partner use this path. The user connects the provider in Glance. You never see the token. `create_automation` includes `schedule_cron`.\n\n**On this iPhone:** `type` is `device`. The iPhone widget reads Weather, Apple Calendar, Reminders, or Motion locally. You cannot grant iOS permissions from this chat, and `list_connected_integrations` does not show them. Those calls omit `schedule_cron` and `connection_id`.\n\n**Your own URL (RSS or JSON):** A saved feed is not a catalog connector. Use the custom connection tools.\n\n1. Call `get_plan`. If `capabilities.custom_connections` is false, say it is on Pro and Power and stop. A host Plus or Pro plan is not Glance Pro.\n2. `create_custom_connection` with name, kind (`rss` or `json`), and url. Optional `header_name` and `requires_key`. There is no key argument. Never put a key in the URL or in chat.\n3. No key: `preview_custom_connection`, map real fields from that sample, then `create_automation` with `integration_id: \"custom_connection\"`, `custom_connection_id`, and `schedule_cron`.\n4. A key is required: stop after create. Send `connection.appLink`. The user pastes the key in Glance. When they say that is done, `get_custom_connection`. If it is still `needs_key`, ask them to paste again. When it is `ready`, preview, then `create_automation`. Do not attach a keyed connection before the preview returns real fields.\n\nRSS slots look like `feed_title`, `item_1_title`, `item_1_link`. `item_1_image` is a picture URL when the feed has one; bind it to an image node. RSS may use `field_mapping: {}` when the bindings are those slot ids. JSON paths look like `current.temperature_2m` or `c`. `field_mapping` is widget binding → that preview path, for example `{ \"temperature\": \"current.temperature_2m\" }` or `{ \"price\": \"c\" }`. The right-hand side is the path, not the widget label, unless they are the same string. An empty JSON map is rejected.\n\n## Catalog connectors (Google, GitHub, and later partners)\n\n`list_integrations` is the list. A new partner shows up there when Glance marks it available. Do not keep a private list of brand names.\n\n1. `list_integrations`. Copy `id`, `providerId`, `fieldCatalog`, and `configOptions`. If the id is absent, use agent-push.\n2. `type: device` uses the on-device section below.\n3. `type: cloud`: `list_connected_integrations`. Match `providerId`. One Google row covers Calendar, Tasks, and Sheets. YouTube and GitHub are their own rows.\n4. If that provider is missing or not `active`, stop. Tell the user to open **Glance → Settings → Connected Services**, tap **Connect**, finish consent, and come back. Do not ask for a token. Do not send an OAuth URL.\n5. Bind names from `fieldCatalog`. `field_mapping` is widget binding → field id. `{}` when the template bindings are those ids. Google Sheets values are cell refs such as `Sheet1!B2`. The spreadsheet id comes from the user's spreadsheet URL.\n6. When a config option is `selectable: true`, call `list_integration_assets` and store the chosen asset id in `config` under that `config_key`. A calendar with no choice uses the connector default (`primary`).\n7. `create_template` → `create_dynamic_widget` → `create_automation` with `schedule_cron`. Omit `connection_id` when that provider has one active connection. Pass it when `list_connected_integrations` shows more than one.\n8. `ingest` once with placeholder `content` so the layout attaches. Glance then refreshes on the schedule. Do not ingest over it on a timer.\n\n```json\n{\n \"feed_id\": \"<uuid>\",\n \"template_id\": \"<uuid>\",\n \"schedule_cron\": \"*/15 * * * *\",\n \"sources\": [\n {\n \"integration_id\": \"google_calendar\",\n \"field_mapping\": { \"title\": \"event_1_title\", \"when\": \"event_1_time\" },\n \"config\": { \"maxEvents\": \"5\", \"daysAhead\": \"14\" }\n }\n ]\n}\n```\n\nA coming-soon catalog id fails at create time. Tell the user Glance cannot pull that provider yet. Use agent-push if you already have the data.\n\n## On-device widgets (Weather, Calendar, Reminders, Motion)\n\nThese are the device sources that ship today. `list_integrations` remains the source of ids. The server cannot see whether the phone permission was granted.\n\n| `integration_id` | Permission in Glance | Bind these names |\n|---|---|---|\n| `weatherkit` | Weather (Location) | `current_temp`, `feels_like`, `high_temp`, `low_temp`, `condition`, `humidity`, `uv_index`, `wind_speed`, `city_name`, `country_name` |\n| `eventkit_calendar` | Apple Calendar | Lists: `today_count`, `event_1_title`, `event_1_time`, … `event_N_*`. Calendar node: `{{events}}` (`event[]`). Identity `field_mapping: {}`. `daysAhead` 31–45 for month/columns. |\n| `eventkit_reminders` | Apple Reminders | `due_today_count`, `overdue_count`, `reminder_1_title`, `reminder_1_due`, `reminder_1_due_relative`, `reminder_1_list`, … — **list only**, never the calendar node |\n| `coremotion` | Motion & Fitness | `steps_today`, `steps_today_fmt`, `distance_today`, `floors_today`, `activity_type` |\n\n**Apple Calendar:** For a text list, bind `event_1_title` / `event_1_time` and set `maxEvents`. For `type: \"calendar\"` (agenda / columns / month), bind `{{events}}` with `field_mapping: {}`. Golden `v2-today-agenda` is valid. **Reminders stay a list** — do not bind `reminder_*` to the calendar node.\n\n**Permission gate (mandatory — do this before `create_automation`):**\n\n1. Tell the user to open **Glance → Settings → Connected Services**.\n2. Tap **Connect** on that source only (Calendar, Reminders, Weather, or Motion). Each has its own button.\n3. If they already denied the iOS prompt, they tap **Open Settings** on that card.\n4. **Wait** until they say they granted it. You cannot check from here.\n5. Then `create_template` → `create_dynamic_widget` → `create_automation`.\n\nGranting permission is not enough by itself. `create_automation` attaches the source. A **bootstrap `ingest`** is still required so the Home Screen gets `template_id` + `content` (empty `feed_state` = no layout). Device readers then overwrite the placeholders.\n\n```json\n{\n \"feed_id\": \"<uuid>\",\n \"template_id\": \"<uuid>\",\n \"sources\": [\n {\n \"integration_id\": \"eventkit_calendar\",\n \"field_mapping\": {},\n \"config\": { \"maxEvents\": \"3\", \"daysAhead\": \"7\" }\n }\n ]\n}\n```\n\nRules: omit `connection_id`. Omit `schedule_cron`. `field_mapping` is `{}`. Template bindings must match the field IDs above.\n\n**After `create_automation` (mandatory):** `ingest` with the same `feed_id` + `template_id` and placeholder `content` for every binding (`events: [{ \"start\": \"2026-09-03T09:00:00Z\", \"title\": \"…\" }]`, `\"—\"` for strings, `0` for numbers). Live Apple data overwrites this on the phone. Then tell them to **open Glance once**, then pin (`glance://skills/pin-widget`).\n\nDo not skip ingest for on-device widgets. Do not use ingest as the live Calendar/Weather feed — placeholders only.\n\n## Sealed rules\n\n1. Call `get_plan` before promising layouts, refresh rates, UI on Demand, or an extra-large widget. If `capabilities.extra_large_widget` is false, say Pro or Power and do not create or edit that size. Do not use a markdown plan table as this user's entitlements. ChatGPT Plus / Claude Pro ≠ Glance Pro.\n2. `list_widgets` first. If widgets exist, **ask** whether to update one or create a new one. Never silently reuse. Never silently duplicate.\n3. Never invent IDs. Use IDs returned by tools.\n4. Design language is the registry plus mapping / views / `visibleFlag`. Use `type: \"chart\"` with `variant` — never `bar_chart`, `pie_chart`, `webview`, CSS-the-web, or extra types. Call `list_golden_examples` (S1–L2 composition, `v2-*` language nodes) before the first tree. Read `glance://skills/design` for every style key.\n5. Structure is the save gate (`deriveSchema`). Design warnings (padding, overflow) do not block `create_template`. Fix unknown types and bindings before save. `WRONG_STYLE_KEY` (`gap` / `textAlign` / `borderRadius`) is worth fixing because iOS ignores those keys.\n6. Agent-push live updates: **`ingest` with OAuth**. You cannot HTTP POST for the user. Write key is for Shortcuts/Make only, shown **once** after `create_dynamic_widget`. Never ask for it later. `get_widget_status` never returns it.\n7. Pinning is **iOS**, not this chat. After create, tell them to follow `glance://skills/pin-widget`.\n8. UI on Demand (`inline_ui`) is Pro+. Call `get_plan` first. If `capabilities.ui_on_demand` is false, never send `inline_ui` — use `create_template` + `template_id`. XOR: never both arms. Public / Discover widgets may use `inline_ui` (subscribers see the last push). On-device automations always `template_id`. Do not tell the user you saved a layout when you used `inline_ui`. If the Home Screen looks empty after UI on Demand, tell them to update Glance.\n8b. Layout language families (`family_views`, `family_charts`, `family_grid`, `family_table`) are Pro+. If a flag is false, do not emit that family (named views / `set_view`, `toggle_flag` + `visibleFlag`, `chart`, `grid`, or `table`). `shape`, mapping, and `calendar` are not family-gated. Apple Calendar may use `calendar` + `{{events}}`; Reminders may not.\n9. Do not count your tokens as Glance Chat messages (`agent_messages_per_day` is in-app only).\n10. Chat previews use a **React** renderer. The Home Screen uses **SwiftUI**. They will not match exactly (fonts, SF Symbols, reload chip). Say so once. Device is truth.\n\n## Two `family_views` patterns\n\nDo not mix these for the same tap.\n\n| Intent | Mechanism | Golden |\n|---|---|---|\n| Tap shows/hides on the **same** screen | `toggle_flag` + `visibleFlag` — no `views` | `v2-vocab-flip` |\n| Tap goes to **another** screen | `set_view` + `views` | `v2-mission-control` |\n\nFlags default false (hidden). Reload clears view + flags. Discover stays on home.\n\n## Workflow\n\n**Agent-push (Jira, Gmail, a headline you have):**\n\n1. `get_plan`\n2. `list_widgets` → ask create vs update\n3. `list_golden_examples` → design tree (read `glance://skills/design`)\n4. Optional `validate_template` (max twice) → `create_template` or `update_template`\n5. If new: `create_dynamic_widget` (mention write key once if they use Shortcuts)\n6. `ingest` with `feed_id`, `template_id`, `content` (binding names)\n7. Tell them how to pin. Preview in chat is approximate.\n\n**Catalog connector (Google Calendar, GitHub, YouTube, a later partner):**\n\n1. `get_plan` + `list_widgets` → ask create vs update\n2. `list_integrations` → copy the id. If it is missing, switch to agent-push.\n3. `list_connected_integrations` → provider must be `active`. If not, Connected Services, then wait.\n4. Design from `fieldCatalog`. `list_integration_assets` when a config option is selectable.\n5. `create_template` → `create_dynamic_widget` → `create_automation` with `schedule_cron`\n6. **`ingest` placeholders** once, then leave refresh to the schedule. Open Glance once, then pin.\n\n**On-device (Apple Calendar / Weather / Reminders / Motion):**\n\n1. `get_plan` + `list_widgets` → ask create vs update\n2. Permission gate (Connected Services **Connect**) — wait for the user\n3. Design a **list** (`event_1_*` / `reminder_1_*`) or a `calendar` node with `{{events}}` for Apple Calendar. Read `glance://skills/design`.\n4. `create_template` → `create_dynamic_widget` → `create_automation` (device id, no schedule, no `connection_id`)\n5. **`ingest` placeholders** (`template_id` + every binding) so the layout attaches\n6. Tell them: Connect in Settings → Connected Services (if not already), **open Glance once**, then pin\n\nOn validation errors: `get_template` for the tree, patch, retry. Do not loop on design warnings.\n"
}SHA-256 of public snapshot: a888b7c29e757388628af3c558a31eec0085cf8a97751c09e7b3423231aec310