{"version":"2.1.223","anchor":"skill-health-values-are-validated-against-a-fixed-set","canonical_anchor":"skill-health-values-are-validated-against-a-fixed-set","heading":"Skill health values are validated against a fixed set","tier":"soon","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/skill-health-values-are-validated-against-a-fixed-set","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Skill health values are validated against a fixed set\n\nThe skills dashboard drops entries with unrecognised health values, but the dashboard itself stays off.\n\n**What**\n\nThe skills dashboard now discards entries whose health value is not one of three accepted strings before building its name to health map.\n\n**Details**\n\n- a new predicate accepts only the three valid health strings\n- filtering happens in the dashboard fetch, before the map is constructed\n- gated on tengu_skills_dashboard_enabled, which falls back to false in this build\n\n**Evidence**\n\n`Skill health fetch skipped: status `\n\n- Flag `tengu_skills_dashboard_enabled`: Off in both readings (read for one account on one subscription tier against v2.1.223; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Skills\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}