{"version":"2.1.290","anchor":"skills-and-mcp-commands-with-over-long-display-names-are-rej","canonical_anchor":"skills-and-mcp-commands-with-over-long-display-names-are-rej","heading":"Skills and MCP commands with very long names are no longer loaded","tier":"notice","area":"Skills","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/skills-and-mcp-commands-with-over-long-display-names-are-rej","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Skills and MCP commands with very long names are no longer loaded\n\nSkills with over-long display names are not loaded, and MCP commands with over-long names or aliases are not listed\n\n**Unclear.** The character limit itself is not known.\n\n**What**\n\nClaude Code now enforces a maximum length on names:\n\n- Skills, packaged instructions Claude can use, are not loaded if their display name is longer than the limit.\n\n- MCP commands, commands supplied by a connected tool server, are not listed if their name, display name or any alias is longer than the limit.\n\nIn each case a log line says what was skipped and how many characters are allowed.\n\n**Why**\n\nA skill or MCP command with a very long name will now drop out of the list without any message on screen. If one goes missing, check the log and shorten its name.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}