How do I install the Gapp Generative Bridge skill?

Run npx skillmds@latest add dwsy/gapp-generative-bridge in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gapp Generative Bridge safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gapp Generative Bridge?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gapp Generative Bridge free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gapp Generative Bridge?

Dwsy (@dwsy) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gapp Generative Bridge by dwsy — Agent Skill

Name: Gapp Generative Bridge
Rating: 4.5 (4 reviews)
Author: Dwsy

File contents

GAPP agent skill (progressive)

What is injected vs fetched

In system	Via tools when needed
Online app list (id / name / scope)	`gapp_list` full list
Live window ids only	`gapp_list_tools({ id })` catalog + schema
Inbound event/generate rules (short)	`gapp_get_state` / `gapp_call` payloads

Never invent domain tool names. System does not embed full tool catalogs.

Tool priority

See app in online list (or gapp_list)
gapp_list_tools({ id }) when you will call/mutate
gapp_call preferred mutate/read
gapp_get_state / gapp_set_state fallback only
gapp_upsert / gapp_open for create / window

Inbound

`[GAPP event]`

Re-read with tools, then short status + next steps

`[GAPP generate]`

Main session; content only; no chit-chat

SSOT

Disk state.json; UI via GappStore

Native-feel GAPP UI

GAPP owns the shared HTML surface, not the native shell. Apply native-feel T1 — place the seam at the rendering surface and T3 — adopt the platform; don't compete with it:

Let Glimpse/macOS own the title bar, traffic lights, window shadow, notifications, and native confirmations. Do not imitate them with HTML.
Use the Host theme tokens and system fonts; include color-scheme: light dark. Never hardcode a brand accent or a window-shaped container.
Use semantic controls, keyboard navigation, visible :focus-visible, and a meaningful Escape action. Keep text selection for user content and editable fields only.
Native rows may have a subtle visual hover, but rows and buttons must not use cursor: pointer. Give controls a distinct pressed state.
Preserve platform scrolling. Avoid JS smooth scrolling, route fades, skeletons for fast work, and decorative motion; honor prefers-reduced-motion.

The shell-specific portions of native-feel (WKWebView configuration, prewarming, title bar/window lifecycle, native menus) are Host responsibilities and must not be reimplemented in a GAPP. The only exception is a GAPP explicitly built as a desktop/window simulator: simulated chrome is then product content, not actual window chrome.

---name: gapp-generative-bridgedescription: Operate Glimpse-APPs with progressive context — app list in system, domain detail via tools on demand.---# GAPP agent skill (progressive)## What is injected vs fetched| In system | Via tools when needed ||-----------|------------------------|| Online app **list** (id / name / scope) | `gapp_list` full list || Live window **ids** only | **`gapp_list_tools({ id })`** catalog + schema || Inbound event/generate rules (short) | `gapp_get_state` / `gapp_call` payloads |**Never invent domain tool names.** System does not embed full tool catalogs.## Tool priority1. See app in online list (or `gapp_list`)2. **`gapp_list_tools({ id })`** when you will call/mutate3. **`gapp_call`** preferred mutate/read4. `gapp_get_state` / `gapp_set_state` fallback only5. `gapp_upsert` / `gapp_open` for create / window## Inbound### `[GAPP event]`- Re-read with tools, then short status + next steps### `[GAPP generate]`- Main session; content only; no chit-chat## SSOT- Disk `state.json`; UI via `GappStore`## Native-feel GAPP UIGAPP owns the shared HTML surface, not the native shell. Apply native-feel **T1 — place the seam at the rendering surface** and **T3 — adopt the platform; don't compete with it**:- Let Glimpse/macOS own the title bar, traffic lights, window shadow, notifications, and native confirmations. Do not imitate them with HTML.- Use the Host theme tokens and system fonts; include `color-scheme: light dark`. Never hardcode a brand accent or a window-shaped container.- Use semantic controls, keyboard navigation, visible `:focus-visible`, and a meaningful Escape action. Keep text selection for user content and editable fields only.- Native rows may have a subtle visual hover, but rows and buttons must not use `cursor: pointer`. Give controls a distinct pressed state.- Preserve platform scrolling. Avoid JS smooth scrolling, route fades, skeletons for fast work, and decorative motion; honor `prefers-reduced-motion`.The shell-specific portions of native-feel (WKWebView configuration, prewarming, title bar/window lifecycle, native menus) are Host responsibilities and must not be reimplemented in a GAPP. The only exception is a GAPP explicitly built as a desktop/window simulator: simulated chrome is then product content, not actual window chrome.

Frequently asked questions

Gapp Generative Bridge