{"version":"2.1.248","anchor":"skill-usage-report-says-when-the-transcript-scan-was-blocked","canonical_anchor":"skill-usage-report-says-when-the-transcript-scan-was-blocked","heading":"Skill usage report says when the transcript scan was blocked","tier":"notice","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/skill-usage-report-says-when-the-transcript-scan-was-blocked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Skill usage report says when the transcript scan was blocked\n\nThe skill usage report asks permission to scan transcripts and states the reason if refused.\n\n**What**\n\nThe skill doctor report counts weekly token usage by scanning session transcripts stored on your machine. It now asks permission first, and when refused it shows an empty count plus a note giving the reason instead of silently reporting nothing.\n\n**Details**\n\n- Accompanying text explains the counts are \"Not shown for HIPAA-regulated organizations\", because producing them requires scanning locally saved transcripts.\n- The `cli_skill_doctor` telemetry event records `scan_policy_denied` in that case, alongside the existing no-user-skills case.\n- What the permission check consults is not visible in this build.\n\n**Evidence**\n\n`scan_policy_denied`, `Not shown for HIPAA-regulated organizations: measured by scanning the session transcripts saved on this machine.`\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}