Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.283 ·

Skill errors and permission prompts drop their hints about a skill's old name

The unknown-skill error and the Skill permission prompt no longer point from a skill's old name or namespace to its current one

Group of 3 You'll notice Improvements
JSON All of v2.1.283
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SkillsArea: what it touches
ImprovementsKind: in v2.1.283,
ImprovementsSection of the release

What

A skill is a packaged set of instructions Claude can load and run by name. Two messages that helped when a skill was called by a name it no longer uses are gone:

  • Unknown-skill error: when Claude asks for a skill that does not exist, the error no longer suggests "a skill from the user's claude.ai account" under that skill's former namespace. It still suggests a close match, meaning a name that differs by at most two characters. It may now also add text built from plugin load errors and the list of enabled plugins.
  • Skill permission prompt: the "renamed" case is removed. When checking whether to ask you, the Skill tool no longer looks for an allow rule that names a skill's former name. It used to say that a rule like Skill(old) covers the skill's old name, give the new name, and tell you to add Skill(new) to allow it without asking.

Why

If your permission rules still name a skill by its old name, Claude Code no longer tells you to update them, so you may be asked for permission without an explanation. When a plugin's skill fails to load, the unknown-skill error can now tell Claude about plugin loading problems instead of only saying the skill is unknown.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe exact text added about plugin loading errors is not known.

See this entry in the whole of v2.1.283 →

Feedback