← Plugin catalog
Productivity

Glance

Glance v1.1.0

Connect widgets to anything

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Read
  • Write

Cost & access

This plugin does not sell products or process payments.

Declared limitations

  • Invented Glance Jira
  • Delete without confirm
  • Write-key HTTP

Onboarding example

Make me a Glance widget of my next Apple Calendar events. Tell me to grant Calendar in Settings, then how to pin it.

View onboarding source →

Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 22, 2026. Package observed Nov 21, 2026.

View package source →

Description

From the marketplace listing

Glance puts widgets on the iPhone Home Screen and lets you update them from this chat. Create a widget, design its layout, and push whatever you want onto it. Pinning happens on the iPhone.

Language: English · Automatically detected from descriptions.

What changed

· 4 observations

Capabilities & instructions

Skill instructions changed from “`fontFamily`). Reserve `sf-rounded` for playful/countdown widgets; `sf-mono` for code/GitHub hashes only. | Role | fontSize | fontWeight | color |...” to “`fontFamily`) unless the widget asks for a different face. Reserve `sf-rounded` for playful/countdown widgets; `sf-mono` for code...

View comparison →
Capabilities & instructions

Is template instance added: “false”. App-6a897f3be004819180880dd62e2d779d updated; open the comparison for details. Glance updated; open the comparison for details. Full description changed from “Glance puts widgets on the iPhone Home Screen and lets you update them from this chat. Create a widget, design its...

View comparison →
Capabilities & instructions

Is template instance added: “false”. App-6a897f3be004819180880dd62e2d779d updated; open the comparison for details. Glance updated; open the comparison for details. Full description changed from “Glance puts widgets on the iPhone Home Screen and lets you update them from this chat. Create a widget, design its...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Keywords

Files & skills

File archives

Plugin package8 files · 91.7 KBBrowse files →
glance-design1 files · 13.8 KBBrowse files →
glance-ingest1 files · 1.89 KBBrowse files →
glance-pin-widget1 files · 869 BytesBrowse files →
glance-public1 files · 4.94 KBBrowse files →
Skill instructions
glance-design33 KB

View saved version →

---
name: glance-design
description: Design native iOS Home Screen widgets in Glance layout language. Apple-like, glanceable. Use registry types only — chart with variant, never bar_chart or webview.
---

# Glance Widget Design Skill

You design **iOS home screen widgets** that feel native, calm, and glanceable — like Apple built them. This skill covers **visual design and composition only**. Workflow, tools, integrations, and sizing math live in the main agent skill.

**Diversity over templates:** Every widget should fit its data and the user's intent. These are principles and patterns — not a single layout to copy. Vary structure, density, and emphasis. Never force one recipe when another fits better.

---

## Design north star

Widgets should feel like **Apple system UI**: clear hierarchy, generous whitespace, restrained color, SF typography. A user glancing at their home screen should read the widget in under two seconds.

| Trait | What it means in practice |
|---|---|
| **Glanceable** | One clear takeaway — a number, status, or headline |
| **Native** | System fonts, semantic colors, no "web app" density |
| **Calm** | Mostly neutral surfaces; color carries meaning, not decoration |
| **Intentional** | Every element earns its space — if it doesn't help, remove it |

---

## Color — Apple-native default, user-guided override

### Default (no user color preference)

Think **Settings / Stocks / Weather** — not marketing landing pages.

| Role | Guidance |
|---|---|
| **Background** | Omit `background` on root for system adaptive fill, or `#FFFFFF` / `#F2F2F7` (light) — never loud gradients unless the user asks |
| **Primary text** | `#000000` or omit `color` (system primary) |
| **Secondary / labels** | `#8E8E93` (iOS secondary label) — captions, timestamps, units |
| **Tertiary / hints** | `#AEAEB2` — de-emphasized metadata only |
| **Accent** | **One** semantic accent per widget — e.g. `#007AFF` (system blue) for links/active, `#34C759` success, `#FF9500` warning, `#FF3B30` alert |
| **Progress / fills** | Muted track `#E5E5EA`, fill = single accent |

**Rules:**
- Never use more than **one accent hue** unless the user requests a colorful or branded look.
- Never fill large areas with saturated color — accents belong on small elements (badge, progress fill, status dot, one headline word).
- Prefer **opacity and weight** over more colors to create hierarchy.

### iOS color format (critical on device)

The iOS renderer only parses **6-digit hex** (`#RRGGBB`). Values like `#FFFFFFCC` or `#FFFFFF40` are **ignored** and fall back to system `.primary` (often black on light widgets).

- Use solid 6-digit hex for every `color`, `background`, `backgroundColor`, `trackColor`, `fillColor`.
- For muted/secondary text on dark or gradient backgrounds, pick a lighter solid tint (e.g. `#FFE8F5` on purple gradients) — not alpha suffixes.
- On colorful widgets, desaturated label colors still beat 8-char hex.

### When the user gives color direction

**Follow the user.** If they say "dark purple theme", "brand pink #E91E8C", or "match my logo colors" — apply their palette to backgrounds, accents, and text while keeping hierarchy and readability. Still use muted variants for labels (`#8E8E93` or a desaturated version of their accent).

If they share no preference, use the Apple-native defaults above.

---

## Typography

Use **SF Pro** (`sf-pro` or omit `fontFamily`) unless the widget asks for a different face. Reserve `sf-rounded` for playful/countdown widgets; `sf-mono` for code and hashes only.

These faces are bundled. Use the id. An unknown `fontFamily` draws as SF Pro.

| ID | Use | Scripts in the file |
|---|---|---|
| `heebo` | Clean body text | Latin, Hebrew |
| `rubik` | The face that also covers Arabic and Cyrillic | Latin, Hebrew, Arabic, Cyrillic |
| `frank_ruhl_libre` | Serif | Latin, Hebrew |
| `varela_round` | Round. One weight — `bold` and `regular` look the same | Latin, Hebrew |
| `secular_one` | Display. One weight — `bol

Preview of the first 4,000 characters. Read full instructions →

glance-ingest3.75 KB

View saved version →

---
name: glance-ingest
description: Push live content to a Glance widget with the ingest tool. XOR template_id vs inline_ui. OAuth only — never HTTP POST a write key.
---

# Glance ingest

Live widget updates from ChatGPT/Claude use the **`ingest` tool** (OAuth). Same class of tool as sending Gmail: the host runs it with the user's Glance token. Do **not** `curl` `/ingest/:feedId`.

## XOR (exactly one layout arm)

**Saved layout**

```json
{
  "feed_id": "<feed uuid>",
  "template_id": "<template uuid>",
  "content": {
    "headline": "Standup in 10 min"
  }
}
```

**UI on Demand (Pro+)** — full tree every ingest. Does not create a Layouts row.

```json
{
  "feed_id": "<feed uuid>",
  "inline_ui": {
    "tree": { "id": "root", "type": "container", "children": [] },
    "widget_size": "medium",
    "views": {
      "revenue": { "id": "rev", "type": "chart", "variant": "line", "x": "{{hours}}", "y": "{{revenue}}" }
    }
  },
  "content": {
    "headline": "Standup in 10 min",
    "hours": [9, 10, 11],
    "revenue": [12, 18, 15]
  }
}
```

Top-level `tree` is an alias for `inline_ui.tree`. Optional `inline_ui.views` is the same named-view map as `create_template`. Never send `template_id` with `inline_ui` or `tree`. If `get_plan.capabilities.ui_on_demand` is false, only `template_id`. Named views / `chart` / `grid` / `table` also need the matching `family_*` flag. `widget_size` may be `extra_large`. It must match the slot from `list_widgets`. If that slot is `extra_large` and `capabilities.extra_large_widget` is false, do not ingest. A template push and an inline layout are both rejected, and the last accepted content stays. Say Pro or Power. Do not retry.

- `content` keys are **binding names** (inside `{{ }}`), not Jira/GitHub field IDs. Arrays (`number[]`, `string[]`, `event[]`) are legal when the layout asked for them.
- Extra keys are dropped. Missing required bindings 400.
- Glance-pull automations: always `template_id`. Public / Discover widgets may use `inline_ui`; subscribers see the last push. Cloneable templates still need a saved layout (`template_id`).
- Do not tell the user you saved a layout when you used `inline_ui`.
- If the widget looks empty: they need the latest Glance app.

## On-device bootstrap (mandatory)

Apple Weather / Calendar / Reminders / Motion, and any later on-device source, **do not** write `feed_state`. After `create_automation`, call `ingest` once with `template_id` and placeholder `content` for every required binding. Live device readers overwrite the placeholders on the phone.

Then tell the user: Connect that source in Glance → Settings → Connected Services (if not already), **open Glance once**, then pin.

```json
{
  "feed_id": "<feed uuid>",
  "template_id": "<template uuid>",
  "content": {
    "events": [{ "start": "2026-09-03T09:00:00Z", "title": "Placeholder" }],
    "current_temp": "—",
    "steps_today": 0
  }
}
```

Include only the bindings that layout actually uses. Missing required keys 400. Do not treat this ingest as the live Calendar/Weather feed.

## Custom URL

A `custom_connection` does write `feed_state` on its schedule. Ingest once so the layout attaches, then do not keep ingesting over it. Do not put the key in `content`. Do not send them to Connected Services to tap Connect. A public feed is already saved. A keyed feed is ready after they paste the key. For JSON, `field_mapping` values are preview paths (`current.temperature_2m`, `c`). An empty JSON map is rejected. RSS may use `{}` when the bindings are the slot ids. Then tell them to **open Glance once** and pin.

## Write key HTTP (not you)

`POST {ingestUrl}` with `Authorization: Bearer <write_key>` is for Shortcuts, Make, n8n, Hermes. Same XOR. The write key is returned **once** from `create_dynamic_widget`. `get_widget_status` never returns it.
glance-pin-widget1.35 KB

View saved version →

---
name: glance-pin-widget
description: Tell the user how to pin a Glance widget on the iPhone Home Screen. ChatGPT cannot place widgets.
---

# Pin a Glance widget on iPhone

ChatGPT/Claude cannot place a Home Screen widget. After create, tell the user:

1. Long-press an empty area on the Home Screen until icons jiggle.
2. Tap **Edit** (or **+**) in the top-left.
3. Search **Glance** and select it.
4. Swipe to the size that matches the widget (Small, Medium, or Large). Tap **Add Widget**, then **Done**.
5. The slot may show a placeholder. Tap it → **Select Widget** → pick the name just created.

They must have the Glance iOS app installed and be signed in as the same account they connected here.

**Preview in this chat is React** (same renderer as glance.cool docs). **The Home Screen is native SwiftUI.** Fonts, icons, corner clipping, and the circular reload control (top-trailing ~40pt) will differ. The iPhone is the source of truth.

If a UI on Demand widget looks empty, update Glance. Old builds only render saved `template_id` layouts.

**On-device Calendar / Weather / Reminders / Motion:** the layout will not appear until you have (1) `ingest`ed placeholders, (2) they tapped **Connect** on that source under Glance → Settings → Integrations, and (3) they **opened the Glance app once**. Then pin. The chat preview can look empty until that ingest.
glance-public12.3 KB

View saved version →

---
name: glance-public
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.
---

# Glance public MCP skill

You 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.

You ONLY help with Glance widgets. Decline unrelated work.

## Data paths (do not mix)

**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.

**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`.

**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`.

**Your own URL (RSS or JSON):** A saved feed is not a catalog connector. Use the custom connection tools.

1. 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.
2. `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.
3. 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`.
4. 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.

RSS 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.

## Catalog connectors (Google, GitHub, and later partners)

`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.

1. `list_integrations`. Copy `id`, `providerId`, `fieldCatalog`, and `configOptions`. If the id is absent, use agent-push.
2. `type: device` uses the on-device section below.
3. `type: cloud`: `list_connected_integrations`. Match `providerId`. One Google row covers Calendar, Tasks, and Sheets. YouTube and GitHub are their own rows.
4. 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.
5. 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.
6. 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 cho

Preview of the first 4,000 characters. Read full instructions →

Release notes

Version 1.1.0 updates the skills for catalog connectors, custom RSS and JSON connections, and extra-large widgets.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
UNLICENSED
Package author
Glance
Keywords
See keywords
Getting started skill
./skills/public/SKILL.md
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Read
  • Write

Package observed Nov 21, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 22, 2026 · 12:00 UTC
Latest observed change
Oct 24, 2026 · 13:09 UTC
Collection status
Collected

plugin_asdk_app_6a897f3be004819180880dd62e2d779d

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.