{"version":"2.1.292","anchor":"frontmatter-name-goes-through-a-validator-for-skills-and-plu","canonical_anchor":"frontmatter-name-goes-through-a-validator-for-skills-and-plu","heading":"Skill and plugin command names are now checked when loaded","tier":"internal","area":"Skills","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/frontmatter-name-goes-through-a-validator-for-skills-and-plu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Skill and plugin command names are now checked when loaded\n\nThe name field in a skill's or plugin command's header is now passed through a check instead of being taken as plain text\n\n**Unclear.** What the check accepts and what happens to a name that fails it is not clear.\n\n**What**\n\nSkills and plugin commands start with frontmatter, a short header block of settings at the top of the file. The `name` field there is now passed through a check when it is read. Before, whatever value was there was simply turned into text.\n\n**Why**\n\nNames that do not pass may now be rejected or warned about.\n\n- Area: Skills\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}