Skip to main content
skill CX Codex

skybridge — Claude Code skill: Claude Code plugins and MCP Apps

A skill that walks you from idea to release for Claude plugins and MCP Apps: bootstrap, build, debug, deploy.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add alpic-ai/skybridge --skill skybridge -a claude-code
Open on GitHub

What skybridge does

The skill covers the whole path of building an app for LLMs. You start by brainstorming the idea against UX guidelines, then copy a project template, implement tools and views, debug, run a dev server, deploy, and connect the result to Claude. One idea it pushes hard: the view is a shared surface. The human interacts with it, the LLM reads its state.

Everything hangs off SPEC.md, which holds requirements and design decisions. No SPEC.md yet? The skill sends you to references/discover.md and nothing else. Once the file exists, you read it, design the change through references/architecture.md, update the spec, and only then write code. Separate branches cover migrating from < 0.36.x and from 1.x to 2.x, plus references/ecommerce.md for storefront apps.

The references split by task: fetching and rendering data, view state and LLM context, prompting the model from a view, UI guidelines, external links, file downloads, OAuth, CSP. There is also an evals reference for checking that a real model reaches the right tools from natural prompts. Deploy goes through Alpic, publishing through the Claude and Claude directories. If your project already runs a different major version of Skybridge, do the migration first — otherwise the references will not match the code you are writing.

What it helps with

  • brainstorm a plugin idea against UX guidelines
  • bootstrap a new project from a template with SPEC.md
  • implement MCP server tools and views
  • debug views in devtools and connect them to Claude
  • check that a model calls the right tools from natural prompts

Example prompts for the agent

  • help me brainstorm a Claude plugin and fill in SPEC.md
  • bootstrap an MCP App from the template and start the dev server
  • add OAuth to my plugin tools

How to install skybridge

1Skills CLI (Vercel)

npx skills add alpic-ai/skybridge --skill skybridge -a claude-code

2Manually: put the files in place

~/.claude/skills/skybridge/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/skybridge/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about skybridge

How do I install skybridge in Claude?

Run npx skills add alpic-ai/skybridge --skill skybridge -a claude-code. The skill lands in ~/.claude/skills/skybridge/SKILL.md.

What does skybridge do?

It guides you through creating and updating Claude plugins and MCP Apps, from the first idea and project template to implementation, debugging, deployment and publishing.

What do I need before building an app?

A SPEC.md file with requirements and design decisions. Until it exists, the skill points you at references/discover.md and holds off on the rest.

Source text

SKILL.md · MIT
---
name: skybridge
description: |
  Guide developers through creating and updating ChatGPT plugins and MCP Apps.
  Covers the full lifecycle: brainstorming ideas against UX guidelines, bootstrapping projects, implementing tools/views, debugging, running dev servers, deploying and connecting them to ChatGPT.
  Use when a user wants to create or update a ChatGPT plugin, MCP App, MCP server or use the Skybridge framework.
---

# Creating Plugins For LLMs

Those are conversational experiences that extend AI assistants through tools and custom UI views. They're built as MCP servers invoked during conversations.

⚠️ The app is consumed by two users at once: the **human** and the **AI Assistant LLM**. They collaborate through the view—the human interacts with it, the LLM sees its state. Internalize this before writing code: the view is your shared surface.

SPEC.md keeps track of the app's requirements and design decisions. Keep it up to date as you work on the app.

**No SPEC.md?** → Read [discover.md](references/discover.md) first. Nothing else until SPEC.md exists.

**SPEC.md exists?** → Read SPEC.md, then follow [architecture.md](references/architecture.md) to design the change. Update SPEC.md, then read the relevant Implementation references below before writing code.

**Migrating from Skybridge `< 0.36.x`?** → Read [migrate-to-v1.md](references/migrate-to-v1.md) first. Users may reference `skybridge >= 0.36.x` as v1.

**Migrating from Skybridge `1.x` to `2.x`?** → Fetch the [v2.0.0 release notes](https://github.com/alpic-ai/skybridge/releases/tag/v2.0.0) first and follow them.

**Building an ecommerce app?** → Read [ecommerce.md](references/ecommerce.md) first.

## Setup

1. **Copy template** → [copy-template.md](references/copy-template.md): when starting a new project with ready SPEC.md
2. **Run locally** → [run-locally.md](references/run-locally.md): when ready to test, need dev server, use devtools to render views or connect to ChatGPT/Claude
3. **Evals** → [evals.md](references/evals.md): when checking that a real model reaches the right tools from natural prompts, in a test

## Architecture

Design or evolve UX flows and API shape → [architecture.md](references/architecture.md)

## Implementation

- **Fetch and render data** → [fetch-and-render-data.md](references/fetch-and-render-data.md): when implementing server handlers and view data fetching
- **State and context** → [state-and-context.md](references/state-and-context.md): when persisting view UI state and updating LLM context
- **Prompt LLM** → [prompt-llm.md](references/prompt-llm.md): when view needs to trigger LLM response
- **UI guidelines** → [ui-guidelines.md](references/ui-guidelines.md): display modes, layout constraints, theme, device, and locale
- **External links** → [open-external-links.md](references/open-external-links.md): when redirecting to external URLs or setting "open in app" target
- **Download file** → [download-file.md](references/download-file.md): when saving content to the user's filesystem
- **OAuth** → [oauth.md](references/oauth.md): when tools need user authentication to access user-specific data
- **CSP** → [csp.md](references/csp.md): when declaring allowed domains for fetch, assets, redirects, or iframes

## Deploy

- **Ship to production** → [deploy.md](references/deploy.md): when ready to deploy via Alpic
- **Publish to ChatGPT/Claude Directories** → [publish.md](references/publish.md): when ready to submit for review

Full API docs: [https://docs.skybridge.tech/api-reference.md](https://docs.skybridge.tech/api-reference.md)

Release notes & changelog: [https://skybridge.tech/changelog.md](https://skybridge.tech/changelog.md)

© alpic-ai · MIT · alpic-ai/skybridge

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set2

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor