CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dicom-anonymizer

De-identify DICOM medical images by removing PHI tags for research sharing, with audit logging and study-linkage preservation support.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Other/dicom-anonymizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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, highly actionable skill body with real scripts, a complete parameter table, validation commands, and genuine scope boundaries including a responsible de-anonymization refusal policy. The main weaknesses are redundant meta-process sections that restate the same response template three times and a missing dependency-install note.

Suggestions

Consolidate the overlapping "Stress-Case Rules", "Output Requirements", and "Response Template" sections into a single response-structure section, and fold the duplicate de-anonymization text in "Scope Boundaries" into "De-anonymization Requests" (or vice versa).

Add a one-line dependency note (e.g. "pip install -r references/requirements.txt" for pydicom) so the usage commands are fully executable.

Add an explicit output-verification step to the workflow (e.g. re-scan anonymized output with the audit log or smoke test before reporting completion).

DimensionReasoningScore

Conciseness

The core content (parameter table, usage commands, error handling) is dense and assumes Claude's competence, but there is real redundancy: "Quick Check" duplicates a command from "Audit-Ready Commands", the de-anonymization text appears nearly verbatim in both "Scope Boundaries" and "De-anonymization Requests", and "Stress-Case Rules", "Output Requirements", and "Response Template" restate the same response structure three times. Mostly efficient but could be tightened fits the 3 anchor better than 2, since no conceptual over-explanation is present.

3 / 5

Actionability

Provides copy-paste-ready commands ("python scripts/main.py --input scan.dcm --output anonymized.dcm", batch, audit-log, and keep-tags examples) plus a full parameter table with defaults, covering the common cases. Minor gap: the pydicom dependency (references/requirements.txt) is never mentioned in the body, so the commands are not fully executable without unstated setup — fits 4 rather than 5.

4 / 5

Workflow Clarity

The 5-step Workflow sequence is clear with fallback handling ("if dependencies or files are missing, provide a bounded fallback") and error-recovery guidance ("If scripts/main.py fails, report the failure point... provide a manual fallback"). Validation commands exist (py_compile, smoke_test.py), so the batch-operation cap does not apply, but there is no explicit post-anonymization output-verification step — fits 4 rather than 5.

4 / 5

Progressive Disclosure

The body is a clear overview with well-signaled, one-level-deep references (references/phi_tags.json and references/audit-reference.md, both real files with descriptive labels), and the heavy logic lives in scripts/. Minor gaps: references/requirements.txt exists in the bundle but is never referenced, and phi_tags.json is only listed without workflow integration — good structure with minor organization gaps fits 4 rather than 5.

4 / 5

Total

15

/

20

Passed

Description

70%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 specific, well-targeted description that clearly states what the skill does in a distinct niche, with good natural trigger vocabulary. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which both caps completeness and omits natural synonyms like 'anonymize' and '.dcm'.

Suggestions

Add an explicit trigger clause, e.g. "Use when preparing DICOM files for research sharing, or when the user mentions de-identifying or anonymizing .dcm files."

Include common synonyms and file extensions ("anonymize", "de-identify", ".dcm", "DICOM files") to broaden natural trigger coverage.

Mention batch directory processing capability, which the body supports, so the description's action coverage matches the skill's scope.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("De-identify DICOM medical images by removing PHI tags", "audit logging", "study-linkage preservation"), matching the 4 anchor for several specific actions with minor coverage gaps. Not 5 because capabilities like batch processing and tag-level keep/remove control are absent; not 3 because more than 1-2 concrete actions are listed.

4 / 5

Completeness

Has a clear "what" (de-identify DICOM images by removing PHI tags, with audit logging and study-linkage preservation) but "for research sharing" is a purpose clause, not an explicit "Use when..." trigger. Per the guideline that a missing 'Use when...' clause caps completeness at 3, this cannot score above 3.

3 / 5

Trigger Term Quality

Includes natural terms users would say ("De-identify", "DICOM", "PHI tags", "research sharing") but omits common synonyms like "anonymize"/"anonymization" and the ".dcm" file extension. Good coverage with a few natural terms missing fits the 4 anchor, short of the comprehensive synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

DICOM/PHI de-identification is a clear niche with distinct triggers ("DICOM", "PHI tags", "de-identify") that would rarely conflict with other skills. Fits the 5 anchor for clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/dicom-anonymizer/SKILL.md

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.