Skills

Versioning and updates

Semantic versions, pinning, and why business Workflows do not auto-update.

Availability note — these docs describe both working and planned product areas. Account authentication, administrator-managed AIHK/AICA tenant regions and keys, signed-in Composer runs and public Guard scans are connected. Skills, Memory, Agents, Workflows, Apps, billing, the public SDK/CLI and the unified API are previews unless a section explicitly says otherwise.


Roadmap and package-contract reference: this page describes the intended GenCMS runtime. The current deployment persists workspace records and drafts but does not execute marketplace Skills, index Memory for retrieval, publish packages, or run Agents, Workflows or Apps. See the deployed API reference for the routes available today.

Skills use semantic versions. A published version is immutable: fixing a bug means publishing 1.0.1, never replacing 1.0.0.

ChangeVersionEffect on installs
Prompt wording, no schema changepatch — 1.0.1Auto-updates unless pinned
New optional input fieldminor — 1.1.0Auto-updates unless pinned
Required input added or output shape changedmajor — 2.0.0Never auto-updates; shown as 'Update available'
Permission addedmajorRequires explicit re-approval by the installer

Pinning

Workflows pin by default. A process that produced a compliance matrix last quarter should produce the same shape this quarter, and a prompt improvement is not worth an unannounced change in a business output.

workflow.yaml
steps:
  - skill: gencms/tender-analyzer
    version: "2.1.0"        # exact — will not move
  - skill: gencms/requirements-structurer
    version: "^1.2"         # accepts compatible minors