其他

using-marketplace-templates

celigo/ai

Find, install, and reuse pre-built integration blueprints from the Celigo Marketplace -- Templates (unlocked, fully editable, no ongoing updates) and Integration Apps (vendor-maintained, upgrade-protected, receive updates). Covers whole-template install versus recreating a single element from the template preview, how connections are mapped rather than copied, and when to start from a blueprint instead of building from scratch. Use when browsing the marketplace, installing a template or Integration App, reusing one flow, export, or import from a template in your own integration, or checking what publishing your own templates and Integration Apps takes.

  • 2871 次安装
  • 4 星标
  • 收录于

安装命令

npx skills add https://github.com/celigo/ai --skill using-marketplace-templates

SKILL.md

Using Marketplace Templates

The Celigo Marketplace is a catalog of pre-built integration blueprints -- packaged flows, exports, imports, connections, and scripts you can browse, install, or reuse instead of building from scratch. Each listing is a Template or an Integration App (IA) (docType Template or Connector). A template installs either an integration or an MCP server (its type), and the AI agent listings are integration templates tagged aiagent whose flows carry an AI agent step. Most decisions come down to Templates vs Integration Apps.

Templates vs Integration Apps

Templates are open, customizable blueprints. Every flow, export, import, and script ships into your account as your own editable resource -- rename, restructure, or rewrite anything. The trade-off: templates receive no ongoing updates. A template is a starting point, not a maintained product; if the source application's API changes, you carry the fix.

Integration Apps (IAs) are vendor-maintained, structure-locked products. Their flows' steps, the connection each step uses, and the code the app ships are upgrade-protected so Celigo (or a partner) can ship updates without breaking your customizations. The trade-off: you change behavior through the app's settings and edit only what it leaves open, such as import mappings, and can't rewrite the core -- in exchange you inherit bug fixes and new features over time. See Changing an Installed Integration App. An IA also sits outside cloning and ILM: to run one in another environment, install it there from the Marketplace (one license covers every environment) -- see managing-integrations > Plain Integrations vs Integration Apps.

Choosing wrong has opposite failure modes: pick a template when you needed an IA and you own the integration forever with no upstream fixes; pick an IA when you needed a template and you hit the locked-component ceiling the moment you must customize beyond what it exposes. When unsure, list both and compare.

MCP-server templates (type: mcpserver) install an MCP server, not an integration, through their own route (step 5).

Whole Install vs Borrowing One Piece

Two distinct intents: