CtrlK
BlogDocsLog inGet started
Tessl Logo

evaluating-with-leakage-gates

Evaluate an OpenMed de-identification or clinical NER model against the leakage-first release gates G1a through G8, which gate releases on residual PHI leakage rather than on F1. Use when the user wants to run the OpenMed eval harness on a synthetic golden set, decide whether a de-id model is RELEASABLE or QUARANTINED, enforce direct-identifier recall floors, require zero critical leakage, fit calibration thresholds, or produce a signed gate report. Trigger on "release gate", "leakage", "is this model safe to ship", "G1a", "G3", "quarantine", "recall floor", or "calibration thresholds" in an OpenMed de-id context.

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable eval skill body with executable examples, an explicit fail-closed workflow, and useful gotchas. Main improvement room is making the fix-and-retry loop explicit and trimming light rhetorical framing.

Suggestions

Add an explicit fix-and-retry step to the Workflow (e.g., after reading per-gate results, address the failing gate's labels/thresholds and re-run ReleaseGate.evaluate until RELEASABLE) to turn the implicit feedback loop into a concrete checklist.

Trim rhetorical framing in the intro ("beautiful F1", "there is no partial credit") to tighten token efficiency without losing the leakage-first emphasis.

Consider a short "If a gate fails" subsection or table mapping each failing gate to its remediation action, making error recovery navigable alongside the gate table.

DimensionReasoningScore

Conciseness

Largely lean and targeted to non-obvious domain specifics (per-milestone gate constants, read-only baselines, mandatory calibration), with only minor rhetorical padding ("beautiful F1", "there is no partial credit") that could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready code for run_suite, ReleaseGate.evaluate, write_calibration_artifacts, plus a CLI equivalent, covering the common end-to-end cases with concrete arguments.

5 / 5

Workflow Clarity

A clear numbered 1–7 sequence with explicit validation checkpoints (calibration_present check, "Fail closed... hard stop", G7 baseline regression); the fix-and-retry feedback loop is implied rather than spelled out as an explicit checklist.

4 / 5

Progressive Disclosure

Well-organized into distinct sections with clearly signaled one-level-deep references to sibling skills and source-of-truth files; no bundle files exist, and the body appropriately stays an overview rather than inlining reference bulk.

4 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A precise, third-person description that explicitly covers capabilities, use-conditions, and natural trigger phrases within a well-scoped niche. It is concise yet comprehensive and would be easy to route correctly.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (run the eval harness, decide RELEASABLE/QUARANTINED, enforce recall floors, require zero critical leakage, fit calibration thresholds, produce a signed gate report), giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both what (evaluate against leakage-first release gates G1a–G8, gating on residual PHI leakage not F1) and when ("Use when the user wants to..." plus a concrete trigger list).

5 / 5

Trigger Term Quality

Provides comprehensive natural triggers including synonyms and a natural user question — "release gate", "leakage", "is this model safe to ship", "G1a", "G3", "quarantine", "recall floor", "calibration thresholds".

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (OpenMed de-id leakage-first release gates, RELEASABLE/QUARANTINED decisions, G1a–G8) with distinct triggers and minimal overlap with adjacent skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
maziyarpanahi/openmed
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.