Skip to content

support versioning/locking #46

Description

@mstsirkin

skills can be dynamic. imagine user trying to update a skill in ~/.claude/skills - now what?
agent will read md from one version then when it runs a script it is from another version.
not good.

a possible suggestion:
update spec and verifier to require that each resource (besides SKILL.md) has the version matching metadata in the file name
for example, always start name with the version?maybe replacing chars such as . and : with _ or - for windows compat?
this has other nice side effects for example, if script is actually a binary, a new version can be installed
while old one is running.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions