commet
Installation
SKILL.md
Commet integration
Treat the installed SDK as the contract. This skill sequences the work; it does not carry a copy of the API surface.
Resolve installed context
Before changing an integration:
- Inspect dependency manifests and lockfiles for every Commet SDK, integration package, CLI, direct REST call, and explicit API or webhook version.
- Identify the package actually imported by the target application. If multiple versions are installed, do not assume the newest one is active.
- Resolve
docs/manifest.jsonfrom that installed artifact, read the manifest entrypoint, and then read only the relevant generated reference and Platform documents named by the manifest. - Read generated types from the same installed artifact when the task depends on an exact request, response, error, or webhook shape.
- If the installed artifact has no documentation, stop and report the exact package and version. Do not silently substitute current web documentation for an older installed contract.
- Plan version operations, such as publishing versions, moving subscribers,
planVersionId, and the version-change events, need an installed SDK version whose manifest lists them. If it does not, report the package and version; never read them from a source checkout.
Use the package manager rather than a source checkout to locate the artifact: