Creating Plugins For LLMs skill

Guide developers through creating and updating ChatGPT plugins.

by alpic-ai·MIT license·★ 2,133 Stars on the repo·GitHub ↗

Use now

Files of Creating Plugins For LLMs

alpic-ai/main1 file shown
SKILL.md
Show the full text57 lines
chatgpt-app-builder/SKILL.md57 lines · 3.9 KB

Creating Plugins For LLMs

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

⚠️ The plugin is consumed by two users at once: the human and the ChatGPT 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 plugin's requirements and design decisions. Keep it up to date as you work on the plugin.

Building an ecommerce plugin? → Read ecommerce.md first.

No SPEC.md? → Read discover.md first. Nothing else until SPEC.md exists.

SPEC.md exists? → Read SPEC.md, then follow 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 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 first and follow them.

Setup

  1. Copy template → copy-template.md: when starting a new project with ready SPEC.md
  2. Run locally → run-locally.md: when ready to test, need dev server or ChatGPT connection
  3. Evals → 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

Implementation

  • Fetch and render data → fetch-and-render-data.md: when implementing server handlers and view data fetching
  • State and context → state-and-context.md: when persisting view UI state and updating LLM context
  • Prompt LLM → prompt-llm.md: when view needs to trigger LLM response
  • UI guidelines → ui-guidelines.md: display modes, layout constraints, theme, device, and locale
  • External links → open-external-links.md: when redirecting to external URLs or setting "open in app" target
  • OAuth → oauth.md: when tools need user authentication to access user-specific data
  • Assets and styling → assets-and-styling.md: when adding images, fonts or CSS to views
  • CSP → csp.md: when declaring allowed domains for fetch, assets, redirects, or iframes
  • OpenAI MCP extensions → openai-extensions.md: when the view should open from the ChatGPT sidebar, a conversation side panel, a file, or a deep link, or use ChatGPT at-mentions, titled messages or local files

Deploy

  • Ship to production → deploy.md: when ready to deploy via Alpic
  • Publish to ChatGPT Directory → publish.md: when ready to submit for review

Full API docs: https://docs.skybridge.tech/api-reference.md

Release notes & changelog: https://skybridge.tech/changelog.md

1---
2name: chatgpt-app-builder
3description: |
4 Guide developers through creating and updating ChatGPT plugins.
5 Covers the full lifecycle: brainstorming ideas against UX guidelines, bootstrapping projects, implementing tools/views, debugging, running dev servers, deploying and connecting plugins to ChatGPT.
6 Use when a user wants to create or update a ChatGPT plugin (formerly called a ChatGPT app) / MCP server for ChatGPT, or use the Skybridge framework.
7---
8 
9# Creating Plugins For LLMs
10 
11ChatGPT plugins are conversational experiences that extend ChatGPT through tools and custom UI views. They're built as MCP servers invoked during conversations.
12 
13⚠️ The plugin is consumed by two users at once: the **human** and the **ChatGPT 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.
14 
15SPEC.md keeps track of the plugin's requirements and design decisions. Keep it up to date as you work on the plugin.
16 
17**Building an ecommerce plugin?** → Read [ecommerce.md](references/ecommerce.md) first.
18 
19**No SPEC.md?** → Read [discover.md](references/discover.md) first. Nothing else until SPEC.md exists.
20 
21**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.
22 
23**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.
24 
25**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.
26 
27## Setup
28 
291. **Copy template** → [copy-template.md](references/copy-template.md): when starting a new project with ready SPEC.md
302. **Run locally** → [run-locally.md](references/run-locally.md): when ready to test, need dev server or ChatGPT connection
313. **Evals** → [evals.md](references/evals.md): when checking that a real model reaches the right tools from natural prompts, in a test
32 
33## Architecture
34 
35Design or evolve UX flows and API shape → [architecture.md](references/architecture.md)
36 
37## Implementation
38 
39- **Fetch and render data** → [fetch-and-render-data.md](references/fetch-and-render-data.md): when implementing server handlers and view data fetching
40- **State and context** → [state-and-context.md](references/state-and-context.md): when persisting view UI state and updating LLM context
41- **Prompt LLM** → [prompt-llm.md](references/prompt-llm.md): when view needs to trigger LLM response
42- **UI guidelines** → [ui-guidelines.md](references/ui-guidelines.md): display modes, layout constraints, theme, device, and locale
43- **External links** → [open-external-links.md](references/open-external-links.md): when redirecting to external URLs or setting "open in app" target
44- **OAuth** → [oauth.md](references/oauth.md): when tools need user authentication to access user-specific data
45- **Assets and styling** → [assets-and-styling.md](references/assets-and-styling.md): when adding images, fonts or CSS to views
46- **CSP** → [csp.md](references/csp.md): when declaring allowed domains for fetch, assets, redirects, or iframes
47- **OpenAI MCP extensions** → [openai-extensions.md](references/openai-extensions.md): when the view should open from the ChatGPT sidebar, a conversation side panel, a file, or a deep link, or use ChatGPT at-mentions, titled messages or local files
48 
49## Deploy
50 
51- **Ship to production** → [deploy.md](references/deploy.md): when ready to deploy via Alpic
52- **Publish to ChatGPT Directory** → [publish.md](references/publish.md): when ready to submit for review
53 
54Full API docs: [https://docs.skybridge.tech/api-reference.md](https://docs.skybridge.tech/api-reference.md)
55 
56Release notes & changelog: [https://skybridge.tech/changelog.md](https://skybridge.tech/changelog.md)
57 

Discussion

Alternatives