Stable identity and versioning
Use a reverse-domain identifier, semantic version, clear publisher identity, customer-facing summary, category, source, availability, and required plan.
Extension developer documentation
Build manifests before asking for runtime power.
The current developer contract covers identity, publisher information, versions, plan requirements, permissions, and contribution metadata. It does not enable executable third-party packages.
Declare capabilities explicitly
Request only the project, file, skill, command, connected-app, model, notification, or automation capabilities the manifest actually contributes.
Keep contributions declarative
Current contributions are metadata for Skills, commands, providers, connected-app presets, workspace modules, and Automation Studio recipes.
Executable packages are rejected.
Do not include JavaScript entry points, native modules, shell commands, installers, remote script URLs, or instructions that assume an executable Extension host exists.
Download the contract
Use the published schema to validate extension manifests consistently before importing them into LobeWork.
Open JSON Schema