菜单
Guides Codemation plugin package development, including `definePlugin(...)`, plugin sandboxes, custom nodes, custom credentials, and publishable plugin package structure. Use when building or updating a Codemation plugin package or the plugin starter template.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
CodemationDocumentScanner node — managed document/invoice/image extraction via the Codemation doc-scanner service. No Azure credentials required. Read before writing any workflow that scans documents, invoices, or images.
ListWorkspaceFiles + ReadWorkspaceFile nodes — read files from the shared workspace pool. Covers read-by-filename (latest-wins), pinned fileId, binary slot handoff, and the raw-upload → concierge-digests → workflow-reads-derived-file pattern. Read before building any workflow that reads workspace files.
AIAgent constructor, message shape, managed and BYOK chatModel configs, outputSchema, mcpServers. Read before writing any workflow step that calls an LLM.
Guides Codemation CLI work for consumer apps and framework-author development. Use when the user asks about `codemation dev`, `build`, `serve web`, `serve worker`, `user create`, `user list`, `--consumer-root`, `.codemation/output`, or consumer versus framework-author mode.
Guides Codemation custom credential development with `defineCredential(...)`, typed sessions, credential testing, and node credential slots. Use when creating or updating custom credentials, credential registrations, or credential-aware custom nodes.
Guides Codemation custom node development with `defineNode(...)` (`execute` per item), `defineBatchNode(...)` (batch `run`), reusable node modules, credential-aware nodes, and the class-based node fallback for advanced cases. Use when creating or updating custom nodes for apps or plugin packages.
| name | codemation-plugin-development |
| description | Guides Codemation plugin package development, including `definePlugin(...)`, plugin sandboxes, custom nodes, custom credentials, and publishable plugin package structure. Use when building or updating a Codemation plugin package or the plugin starter template. |
| compatibility | Designed for Codemation plugin packages and the Codemation plugin starter template. |
| tags | plugin, node, package |
A Codemation plugin is an npm package with a codemation.plugin.ts composition root that calls definePlugin(...). It registers custom nodes and credential types, optionally declares MCP servers, and ships a sandbox app so the plugin is immediately testable. Consumers load the built JavaScript entry (package.json#codemation.plugin) — not TypeScript source. Plugin code follows the same defineNode / defineCredential patterns as app-level code; the plugin boundary is purely about packaging and distribution.
Plugin authoring is a framework-author / non-managed task. Managed-mode agents work with credential slots and workflow DSL — they do not author or modify plugin packages.
Use this skill for published plugin packages, plugin starter work, and sandbox-driven plugin development. Do not use for ordinary consumer workflow-only changes.
MCP servers in plugins: Plugin-declared mcpServers is a non-managed pattern for self-hosted / framework-author scenarios. In managed mode, MCP servers are loaded from the control plane — see codemation-mcp-capabilities for the managed path.
Publishing guardrail: package.json#codemation.plugin must point at runnable JavaScript (./dist/codemation.plugin.js). Do not rely on consumers TypeScript-loading plugin files from node_modules.
references/plugin-anatomy.md for the full definePlugin(...) code, package layout, sandbox setup, MCP server declaration, binary payload rules, and publishing guidance.references/plugin-structure.md for a concise package layout reference.