Skip to content

Decouple SKILL.md versioning from CLI releases? #458

Description

@FabianBeiner

Currently, every stable CLI release regenerates and commits skills/todoist-cli/SKILL.md, primarily to keep metadata.version aligned with the package version.

This means that even releases without any meaningful change to the skill instructions produce a new SKILL.md revision.

For consumers that vendor, pin, synchronize, or monitor skills independently from the CLI package, these version-only changes create unnecessary update churn. The CLI may have changed, but the skill contract and instructions often have not.

Would it make sense to decouple the two versions?

Possible approaches:

  • Increment metadata.version only when the generated skill content changes materially.
  • Maintain an independent skill version.
  • Replace the field with something more explicit, such as minimum_cli_version or tested_cli_version.
  • Skip committing the generated file when the only change is the package-version metadata.

My preference would be an independently versioned skill, optionally combined with explicit CLI compatibility metadata. This would preserve useful compatibility information without making every CLI patch release appear like a new skill release.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions