benchmark-pii-recall

Measure PII extraction recall against synthetic gold spans with aggregate-only evidence.

5.0k|615|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/maziyarpanahi/openmed --skill benchmark-pii-recall
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark-pii-recall
Source: https://github.com/maziyarpanahi/openmed/tree/main/skills/benchmark-pii-recall
Command: npx skills add https://github.com/maziyarpanahi/openmed --skill benchmark-pii-recall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill measures whether a PII extraction model detects sensitive entities reliably, helping prevent privacy failures caused by missed direct identifiers before deployment.

Core Features & Use Cases

  • Synthetic Recall Benchmarking: Build fixtures with exact offsets, canonical labels, boundary cases, and multilingual or multiscript coverage.
  • Privacy-Safe Evaluation: Compare exact-span and grapheme-level recall while reporting aggregate metrics without emitting identifier surfaces.
  • Release Gating: Enforce recall floors, require zero misses for critical identifiers, compare quantized and full-precision models, and track device or label-specific slices.
  • Use Case: Evaluate a new threshold, backend, or quantized PII model and reject the release if it misses critical identifiers or falls below the required recall floor.

Quick Start

Use the benchmark-pii-recall skill to run the synthetic PII recall benchmark for the candidate model and report aggregate release-gate metrics without exposing identifier text.

Frequently Asked Questions about benchmark-pii-recall

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I measure PII extraction recall for clinical text models?

PII extraction recall is measured against synthetic gold spans using exact span and grapheme-level scoring to evaluate if models detect sensitive entities reliably before deployment, while reporting aggregate metrics without exposing identifier text.

Can I use recall benchmarking to block a model release if it misses critical identifiers?

Recall benchmarking can enforce release gating by requiring zero misses for critical identifiers and applying recall floors to reject model releases that fall below required privacy thresholds.

Does PII recall evaluation work with quantized models across different devices?

PII recall evaluation supports comparing quantized and full-precision models, tracking device-specific slices, and evaluating backend, language, and script variations for privacy-preserving clinical text processing.

What is privacy-safe evaluation in the context of PII detection?

Privacy-safe evaluation compares exact-span and grapheme-level recall while reporting aggregate metrics only, preventing identifier surfaces from appearing in evaluation output.

How do I set up synthetic recall benchmarking with multilingual coverage?

Synthetic recall benchmarking fixtures are built with exact offsets, canonical labels, boundary cases, and multilingual or multiscript coverage to test PII detection across diverse text formats.

What are the limitations of aggregate-only evidence in PII recall scoring?

Aggregate-only evidence limits debugging by restricting exposure to identifier text, requiring normalized labels and hard negatives to ensure PII recall scoring accuracy without compromising privacy.