{"version":"2.1.281","anchor":"skill-proposal-slugs-must-not-contain-claude-or-anthropic","canonical_anchor":"skill-proposal-slugs-must-not-contain-claude-or-anthropic","heading":"Skill proposal slugs must not contain \"claude\" or \"anthropic\", max 64 chars","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/skill-proposal-slugs-must-not-contain-claude-or-anthropic","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Skill proposal slugs must not contain \"claude\" or \"anthropic\", max 64 chars\n\nSkill proposals now tell the model a skill's slug must not contain \"claude\" or \"anthropic\" and must be at most 64 characters\n\n**Unclear.** The finding does not show whether the naming rules are enforced anywhere or only described.\n\n**What**\n\nWhen Claude proposes a new skill or an improvement to one, the proposal includes a slug, a short lowercase name with words joined by hyphens. The field's description now tells the model that the slug must not contain \"claude\" or \"anthropic\", and that a new skill's slug can be at most 64 characters long.\n\nOnly the description text changed. The only visible check on the field is that it cannot be empty.\n\n**Why**\n\nProposed skill names should now avoid those two words and stay within 64 characters, because the model has been told to follow those rules."}