cesdk
v1.81.0IMG.LY CreativeEditor SDK builder agent and documentation for Web
By IMG.LY GmbHLicense: MIT7 GitHub starsUpdated 2 hours ago
Directory evidence
- Runtimes
- Codex and Claude Code
- Parsed components
- 12 skill or MCP entries
- Source updated
- Aug 24, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install plugin
codex plugin marketplace add IchenDEV/agent-plugin-mkt
codex plugin marketplace upgrade agent-plugin-marketplace
codex plugin add cesdk@agent-plugin-marketplacePaste and run these commands in a terminal with Codex. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/imgly/agent-skillsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/cesdk/.
Plugin files
├── .codex-plugin/plugin.json├── .claude-plugin/plugin.json├── skills/build/SKILL.md├── skills/docs-angular/SKILL.md├── skills/docs-electron/SKILL.md├── skills/docs-js/SKILL.md├── skills/docs-nextjs/SKILL.md├── skills/docs-node/SKILL.md├── skills/docs-nuxtjs/SKILL.md├── skills/docs-react/SKILL.md├── skills/docs-svelte/SKILL.md├── skills/docs-sveltekit/SKILL.md├── skills/docs-vue/SKILL.md└── skills/explain/SKILL.md
Included Skills12
Implement features, write code, and set up CE.SDK Web projects. Covers React, Vue.js, Svelte, Angular, Electron, Vanilla JavaScript, Node.js, Nuxt.js, Next.js, SvelteKit. Use when the user asks to implement, create, add, build, set up, or integrate something with CE.SDK for Web. Triggered by "help me add", "set up", "build a photo editor", or "create a design tool". Covers photo, video, and design editors. Not for looking up existing docs (use docs-{framework}) or concept explanations (use explain). <example> Context: User wants to build a Web app with CE.SDK user: "Help me set up CE.SDK in my project" assistant: "I'll use /cesdk:build to help set this up." </example> <example> Context: User wants to add a specific feature user: "Add text overlays to my image editor" assistant: "Let me use /cesdk:build to implement text overlays." </example>
Look up CE.SDK Angular reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Angular — configuration, UI customization, export options, feature guides, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing Angular doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Angular configuration user: "How do I configure the editor in Angular?" assistant: "I'll use /cesdk:docs-angular to look up configuration options." </example> <example> Context: User needs Angular integration user: "How do I use CE.SDK in an Angular component?" assistant: "Let me use /cesdk:docs-angular to find the relevant documentation." </example>
Look up CE.SDK Electron reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Electron — configuration, UI customization, export options, feature guides, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing Electron doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Electron configuration user: "How do I configure the editor in Electron?" assistant: "I'll use /cesdk:docs-electron to look up configuration options." </example> <example> Context: User needs Electron integration user: "How do I embed CE.SDK in an Electron app?" assistant: "Let me use /cesdk:docs-electron to find the relevant documentation." </example>
Look up CE.SDK Vanilla JavaScript reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Vanilla JavaScript — configuration, UI customization, export options, feature guides, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing Vanilla JavaScript doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Vanilla JavaScript configuration user: "How do I configure the editor in Vanilla JavaScript?" assistant: "I'll use /cesdk:docs-js to look up configuration options." </example> <example> Context: User needs vanilla JS setup user: "How do I use CE.SDK without a framework?" assistant: "Let me use /cesdk:docs-js to find the relevant documentation." </example>
Look up CE.SDK Next.js reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Next.js — configuration, UI customization, export options, feature guides, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing Next.js doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Next.js configuration user: "How do I configure the editor in Next.js?" assistant: "I'll use /cesdk:docs-nextjs to look up configuration options." </example> <example> Context: User asks about SSR compatibility user: "Does CE.SDK work with Next.js server-side rendering?" assistant: "Let me use /cesdk:docs-nextjs to find the relevant documentation." </example>
Look up CE.SDK Node.js reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Node.js — configuration, headless rendering, export options, batch processing, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing Node.js doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Node.js configuration user: "How do I configure the engine in Node.js?" assistant: "I'll use /cesdk:docs-node to look up configuration options." </example> <example> Context: User needs server-side generation user: "How do I use CE.SDK for server-side image generation?" assistant: "Let me use /cesdk:docs-node to find the relevant documentation." </example>
Look up CE.SDK Nuxt.js reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Nuxt.js — configuration, UI customization, export options, feature guides, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing Nuxt.js doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Nuxt.js configuration user: "How do I configure the editor in Nuxt.js?" assistant: "I'll use /cesdk:docs-nuxtjs to look up configuration options." </example> <example> Context: User needs Nuxt.js integration user: "How do I use CE.SDK in a Nuxt.js page?" assistant: "Let me use /cesdk:docs-nuxtjs to find the relevant documentation." </example>
Look up CE.SDK React reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for React — configuration, UI customization, export options, feature guides, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing React doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about React configuration user: "How do I configure the editor in React?" assistant: "I'll use /cesdk:docs-react to look up configuration options." </example> <example> Context: User needs React component setup user: "How do I embed CE.SDK in a React component?" assistant: "Let me use /cesdk:docs-react to find the relevant documentation." </example>
Look up CE.SDK Svelte reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Svelte — configuration, UI customization, export options, feature guides, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing Svelte doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Svelte configuration user: "How do I configure the editor in Svelte?" assistant: "I'll use /cesdk:docs-svelte to look up configuration options." </example> <example> Context: User needs Svelte integration user: "How do I use CE.SDK in a Svelte component?" assistant: "Let me use /cesdk:docs-svelte to find the relevant documentation." </example>
Look up CE.SDK SvelteKit reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for SvelteKit — configuration, UI customization, export options, feature guides, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing SvelteKit doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about SvelteKit configuration user: "How do I configure the editor in SvelteKit?" assistant: "I'll use /cesdk:docs-sveltekit to look up configuration options." </example> <example> Context: User asks about SvelteKit SSR user: "Does CE.SDK work with SvelteKit server-side rendering?" assistant: "Let me use /cesdk:docs-sveltekit to find the relevant documentation." </example>
Look up CE.SDK Vue.js reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Vue.js — configuration, UI customization, export options, feature guides, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing Vue.js doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Vue.js configuration user: "How do I configure the editor in Vue.js?" assistant: "I'll use /cesdk:docs-vue to look up configuration options." </example> <example> Context: User asks about Vue plugin registration user: "How do I register CE.SDK as a Vue plugin?" assistant: "Let me use /cesdk:docs-vue to find the relevant documentation." </example>
Explain how CE.SDK Web features work — concepts, architecture, and workflows. Covers React, Vue.js, Svelte, Angular, Electron, Vanilla JavaScript, Node.js, Nuxt.js, Next.js, SvelteKit. Use when the user says "explain", "how does X work", "walk me through", "what is", or "describe" and wants to understand a CE.SDK concept for Web development. Generates custom markdown explanations with diagrams and code examples. Not for looking up existing docs (use docs-{framework}) or writing code (use build). <example> Context: User wants to understand how text layers work user: "Explain how text layers work in CE.SDK" assistant: "I'll use /cesdk:explain to generate a detailed explanation." </example> <example> Context: User needs a concept explained user: "How does the block hierarchy work for video editing?" assistant: "Let me use /cesdk:explain to explain video block hierarchy." </example>
Plugin manifests2
{
"author": {
"name": "IMG.LY GmbH",
"url": "https://img.ly"
},
"description": "IMG.LY CreativeEditor SDK builder agent and documentation for Web",
"homepage": "https://img.ly/docs/cesdk",
"interface": {
"capabilities": [
"CE.SDK documentation",
"Feature implementation",
"SDK integration"
],
"category": "Developer Tools",
"defaultPrompt": [
"Build a CE.SDK Web feature.",
"Explain a CE.SDK Web API or workflow.",
"Find the relevant CE.SDK Web documentation."
],
"developerName": "IMG.LY GmbH",
"displayName": "CE.SDK Web",
"longDescription": "CE.SDK builder agent and documentation for Web — photo editors, video editors, design editors, and creative automation.",
"shortDescription": "Build and understand CE.SDK Web projects.",
"websiteURL": "https://img.ly/docs/cesdk"
},
"keywords": [
"cesdk",
"creative-editor",
"photo-editor",
"video-editor",
"design-editor",
"img.ly",
"sdk",
"creative-automation",
"react",
"vue",
"svelte",
"angular",
"electron",
"js",
"node",
"nuxtjs",
"nextjs",
"sveltekit"
],
"license": "MIT",
"name": "cesdk",
"repository": "https://github.com/imgly/agent-skills",
"skills": "./skills/",
"version": "1.81.0"
}{
"author": {
"name": "IMG.LY GmbH",
"url": "https://img.ly"
},
"description": "IMG.LY CreativeEditor SDK builder agent and documentation for Web",
"homepage": "https://img.ly/docs/cesdk",
"license": "MIT",
"name": "cesdk",
"version": "1.81.0"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[cesdk on Agent Plugins Marketplace](https://pluginsmp.com/plugins/cesdk)