Skip to content

Update the retired model id in the create-command example - #105

Merged
LeoVS09 merged 2 commits into
NeoLabHQ:masterfrom
kasparovabi:chore/opus5-compat
Aug 20, 2026
Merged

Update the retired model id in the create-command example#105
LeoVS09 merged 2 commits into
NeoLabHQ:masterfrom
kasparovabi:chore/opus5-compat

Conversation

@kasparovabi

Copy link
Copy Markdown
Contributor

The frontmatter example in the create-command skill sets model: claude-3-5-haiku-20241022. Anthropic retired that id on 19 February 2026, so a slash command written from this example pins a model the API no longer serves.

File Change
plugins/customaize-agent/skills/create-command/SKILL.md claude-3-5-haiku-20241022 becomes claude-haiku-4-5-20251001
skills/create-command/SKILL.md same edit, so the generated bundle stays in sync

Retirement dates are on the Anthropic deprecations page: https://platform.claude.com/docs/en/about-claude/model-deprecations

I touched the root-level skills/ copy because the sync-provider-formats workflow fails on drift for fork PRs and cannot push a fix back to my branch. The two files differ elsewhere for reasons I did not touch, and that difference is byte-for-byte the same before and after this change. If just sync-provider-formats would produce something else, say so and I will drop the generated file from the diff.

I read this diff line by line before opening it, and I am happy to adjust or drop any part of it. What brought me here was a checker I maintain that flags retired Claude model ids, so I am saying that up front rather than leaving you to wonder. I have not run a command with that frontmatter to reproduce a failure, the claim rests on the published retirement date. If you would rather not get this kind of contribution at all, tell me and I will not send another.

claude-3-5-haiku-20241022 was retired on 2026-02-19. The example teaches
readers to put it in a slash command's model field.

The generated bundle under skills/ is updated with the same edit so the
provider sync finds no drift.
@LeoVS09

LeoVS09 commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Thank you for contribution. I'm believe model field is outdated in general, because it not supported by official skills format, so even better will be to remove it.

@LeoVS09
LeoVS09 self-requested a review August 20, 2026 19:11
Comment thread plugins/customaize-agent/skills/create-command/SKILL.md Outdated
Comment thread skills/create-command/SKILL.md Outdated
Co-authored-by: Vladislav Goncharov <LeoVS010@gmail.com>
@LeoVS09
LeoVS09 merged commit 87baea1 into NeoLabHQ:master Aug 20, 2026
1 check passed
@kasparovabi

Copy link
Copy Markdown
Contributor Author

Agreed, and I see you already removed the fields in 20afd3c.

For the record, the docs back you up: the Agent Skills reference lists name and description as the only required frontmatter fields, and model does not appear in the skill frontmatter spec at all. So dropping it was the right call rather than pinning it to a newer id as my PR did.

Thanks for the merge and the correction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants