CtrlK
BlogDocsLog inGet started
Tessl Logo

ehr-semantic-compressor

1. Confirm the user objective, required inputs, and non-negotiable constraints before doing detailed work. 2. Validate that the request matches the documented scope and stop early if the task would require unsupported as.

31

Quality

25%

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/Academic Writing/ehr-semantic-compressor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The body is highly actionable — concrete commands, a real script, parameter docs, and I/O schemas — but it is bloated with generic template sections and redundant verification blocks that inflate the context window without adding skill-specific value. Progressive disclosure is undercut by inlining content that also exists as reference files.

Suggestions

Remove or relocate generic boilerplate (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Response Template, Output Requirements) that does not add skill-specific knowledge, keeping only the concise technical core.

De-duplicate verification content (merge Quick Check into Audit-Ready Commands) and replace the inline sample input/output JSON with a pointer to references/sample_input.json and references/sample_output.json to shorten the body and strengthen progressive disclosure.

Add validation checkpoints tied to the actual pipeline (e.g., verify output JSON schema and compression ratio after running scripts/main.py) so the workflow reflects the real EHR processing rather than generic scope-control steps.

DimensionReasoningScore

Conciseness

The body is heavily padded with template boilerplate (Risk Assessment tables, Security Checklist, Evaluation Criteria, Lifecycle Status, Response Template, Output Requirements) and duplicates content (Quick Check vs Audit-Ready Commands both run py_compile; sample input/output shown inline AND referenced as files), violating the token-budget principle with material Claude already understands.

1 / 3

Actionability

It provides copy-paste-ready executable commands ('python scripts/main.py --input ehr_document.txt --output summary.json', py_compile, a concrete audit sample), a complete parameter table, and concrete input/output JSON schemas backed by a real scripts/main.py.

3 / 3

Workflow Clarity

A sequenced 5-step Workflow with a fallback path and a py_compile/--help verification checkpoint exists, but the steps are generic process boilerplate rather than the actual processing pipeline, and the real EHR pipeline lacks validation checkpoints on its output (e.g., schema/compression validation).

2 / 3

Progressive Disclosure

References are one level deep, clearly signaled in a dedicated References section, and all real (guidelines.md, requirements.txt, sample_input.json, sample_output.json, scripts/main.py exist), but the SKILL.md is a long monolithic file that duplicates sample input/output inline rather than deferring to the bundled reference files.

2 / 3

Total

8

/

12

Passed

Description

0%

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

The description is a corrupted, truncated copy of the workflow procedure rather than a capability statement: it omits what the skill does, when to use it, and any EHR/clinical trigger terms. It reads as boilerplate that could describe almost any scoped task skill.

Suggestions

Rewrite the description as a third-person capability statement naming concrete actions, e.g. 'Summarizes lengthy Electronic Health Record (EHR) documents into structured bullet-point summaries and extracts clinical sections (allergies, medications, diagnoses). Use when compressing medical records or extracting structured clinical information from EHR text.'

Add an explicit 'Use when...' trigger clause with natural terms users would say (EHR, medical records, clinical summary, patient notes) so it is both complete and distinguishable from other skills.

Ensure the description is not truncated and uses third-person voice ('Summarizes', 'Extracts') instead of imperative workflow-step numbering.

DimensionReasoningScore

Specificity

The description names only generic process actions ('Confirm the user objective', 'Validate that the request matches the documented scope') that apply to any scoped task skill, with no mention of the skill's actual EHR summarization/extraction capabilities; it also truncates mid-word ('unsupported as.').

1 / 3

Completeness

It answers neither 'what does this do' (no capability described) nor 'when should Claude use it' (no 'Use when...' trigger clause), satisfying the missing-trigger cap and going further by omitting both halves.

1 / 3

Trigger Term Quality

There are no natural keywords a user would say (no 'EHR', 'medical records', 'clinical summary', etc.); the text is procedural jargon rather than recognizable trigger terms.

1 / 3

Distinctiveness Conflict Risk

The generic procedural language ('confirm the user objective', 'validate scope') would conflict with many scoped-task skills and provides no distinguishing niche for the EHR compressor.

1 / 3

Total

4

/

12

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.

Validation15 / 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
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.