The SDK now rejects malformed skill names with a clear reason instead of creating a rule that never matches.
What's wrong with this entry?
Each name in the SDK skills option is now checked before it becomes a Skill(name) allowed-tool rule, so a name that could never match is reported instead of silently producing a dead rule.
- Rejects empty names, unpaired surrogates, leading or trailing whitespace, parentheses, commas, control characters, wildcard suffixes, a leading slash, consecutive backslashes and a trailing unpaired backslash.
- Each rejection carries a specific explanation of why the resulting rule could not match.
- Applies to everyone using the SDK
skillsoption; no gate.
Invalid skill name '*': use skills: 'all' to enable every skill.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Question options with identical text are no longer confused with each other
Both mention agent
-
v2.1.236
Teammate messages whose summary swallowed the body are split back apart
Both mention agent
-
v2.1.238
Claude is told to stay in a worktree even when it did not create one
Both mention agent