{"version":"2.1.232","anchor":"skill-names-are-hashed-in-telemetry-only-when-they-are-your-","canonical_anchor":"skill-names-are-hashed-in-telemetry-only-when-they-are-your-","heading":"Skill names are hashed in telemetry only when they are your own","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/skill-names-are-hashed-in-telemetry-only-when-they-are-your-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Skill names are hashed in telemetry only when they are your own\n\nOnly your own skills get hashed names in telemetry; built-in and MCP skills report real names.\n\n**What**\n\nThe hashed skill name attached to skill telemetry is now emitted only for user-authored skills; MCP, built-in, bundled and official skills already report their real names, so the hash is redundant for them.\n\n**Details**\n\n- The hash is included only when the sanitized skill source resolves to \"custom\".\n- Three fields were added to the telemetry redaction allowlist: `skill_name_hashes`, `parent_skill_name_hash` and `item_name_hash`, used by the plugin name-collision event and by aggregate skill reporting.\n\n**Evidence**\n\n`parent_skill_name_hash`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}