CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

patient-consent-simplifier

Simplifies informed consent documents into patient-friendly language while maintaining regulatory compliance. Readability assessment targeting 6th-8th grade level, risk/benefit clarification in table format, and FDA 21CFR50/ICH-GCP/HIPAA compliance validation.

Quality

65%

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/patient-consent-simplifier/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

55%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.

The workflow itself is excellent — well-sequenced with explicit user checkpoints, iteration loops, and a fallback — but the skill is undermined by code and CLI examples that don't match the bundled script, plus substantial generic boilerplate padding. The body needs to be reconciled with scripts/main.py's real API and trimmed of template sections.

Suggestions

Reconcile all code examples with the actual bundle: import from scripts.main (the only script present), document the real simplify(text)/calculate_grade_level(text) API and the actual CLI flags (--input, --text, --output, --target-grade), and delete references to the nonexistent scripts/consent_simplifier.py, --grade-level, and --check.

Cut the generic 'Output Requirements', 'Input Validation', 'Error Handling', and 'Response Template' boilerplate down to the few lines that are specific to consent simplification, and remove the duplicated py_compile command from 'Quick Check' since 'Audit-Ready Commands' already covers it.

Move the fabricated capability examples (clarify_risks, check_compliance) into a references/ file once implemented, or replace them with real usage of the readability output (grade level, word counts, terms replaced) that main.py actually produces.

DimensionReasoningScore

Conciseness

Several padded sections add no skill-specific value: 'Quick Check' duplicates the py_compile command already in 'Audit-Ready Commands', and the generic 'Output Requirements', 'Input Validation', 'Error Handling', and 'Response Template' sections (~40 lines) are boilerplate any skill could carry rather than consent-simplification guidance. This matches anchor 2 — noticeably verbose with several unnecessary or padded sections — rather than 3, since the padding is substantial, not incidental.

2 / 5

Actionability

The guidance looks concrete but is not executable against the actual bundle: 'from scripts.consent_simplifier import ConsentSimplifier' points to a module that doesn't exist (the bundle has scripts/main.py), the methods simplify_section, clarify_risks, assess_readability, and check_compliance are absent, simplify() is shown with keyword args it doesn't accept, and the CLI section uses '--grade-level'/'--check' flags while main.py defines '--target-grade' and no --check. Only the Audit-Ready Commands actually run. Anchor 3 — concrete guidance but incomplete/incorrect, not copy-paste executable; not 4 because the majority of the code examples fail against the real script.

3 / 5

Workflow Clarity

The 10-step workflow has a clear sequence with explicit validation checkpoints ('Checkpoint: Verify with user that all required legal elements are captured', 'Checkpoint: User confirms that risk/benefit balance is accurately preserved'), feedback loops ('If target grade not met, iterate on complex sections'; 'If risk is downplayed, revise'), a required-elements checklist, and a fallback path. This matches anchor 5 for document manipulation with explicit validation and error recovery; nothing is missing that anchor 4's 'minor validation gaps' would describe.

5 / 5

Progressive Disclosure

All content lives inline in a single SKILL.md with no references/ files in the bundle, and the body points to a nonexistent 'scripts/consent_simplifier.py' while burying the actual entry point. The Core Capabilities API examples and Best Practices lists are content that could live in a reference file, and no references are clearly signaled. Anchor 3 — some structure but content that should be separate is inline and references are not clearly signaled; not 4 because the one reference the body does make is broken.

3 / 5

Total

13

/

20

Passed

Description

62%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, domain-distinct description with concrete capabilities, but it omits any 'when to use' trigger guidance, which limits both completeness and discoverability via natural user phrases. The trigger phrases exist in the body's 'When to Use' section and should be surfaced into the description itself.

Suggestions

Append an explicit trigger clause to the description, e.g. 'Use when the user asks to simplify a consent form, write a plain-language consent, or adapt clinical trial information for patients.'

Add natural user phrasings such as 'simplify consent', 'plain language consent', and 'consent form' to the description's trigger terms, not just the body's When to Use section.

Convert the trailing noun-phrase fragments ('Readability assessment targeting...') into parallel third-person verb statements so each capability reads as a concrete action.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Simplifies informed consent documents into patient-friendly language', 'Readability assessment targeting 6th-8th grade level', 'risk/benefit clarification in table format', 'FDA 21CFR50/ICH-GCP/HIPAA compliance validation' — which is comprehensive for this niche. Not a 5 because the actions are terse noun-phrase fragments with minor gaps (no input formats, no output artifacts mentioned).

4 / 5

Completeness

The 'what' is clearly stated (simplification, readability assessment, risk/benefit tables, compliance validation), but there is no 'Use when...' clause or any trigger guidance in the description itself — the rubric guideline explicitly caps completeness at 3 for a missing 'Use when...' clause. Not 4 because 'when' is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

It includes relevant keywords like 'informed consent documents', 'patient-friendly language', and 'readability assessment', but misses the natural phrases a user would actually say such as 'simplify consent', 'plain language consent', or 'consent form' (these appear only in the body, not the description). Anchor 3 — some relevant keywords but missing common variations and synonyms.

3 / 5

Distinctiveness Conflict Risk

This is a clear niche with distinct triggers: 'informed consent documents', 'FDA 21CFR50/ICH-GCP/HIPAA' are domain-specific and would not plausibly trigger a general document or writing skill. Minimal conflict risk, matching the score-5 anchor.

5 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/patient-consent-simplifier/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.