CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

medication-adherence-message-gen

Use medication adherence message gen for academic writing workflows that need structured execution, explicit assumptions, and clear output boundaries.

Quality

56%

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/medication-adherence-message-gen/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.

The body's core usage documentation is excellent — verified, copy-paste-ready CLI and Python API examples with real output formats — but it is buried in roughly 150 lines of generic template boilerplate (risk tables, security checklists, test cases, lifecycle status) that add nothing task-specific. The workflow has explicit scope validation and fallback handling, though it is fragmented across redundant sections. The bundle structure itself is sound: code in scripts/main.py and one real, clearly linked reference file.

Suggestions

Remove the generic template sections (Risk Assessment, Security Checklist, Evaluation Criteria, Test Cases, Lifecycle Status) or replace them with task-specific content; the boilerplate test cases and risk table do not apply to message generation.

Consolidate the sections that repeat the same two commands ("Quick Check", "Audit-Ready Commands", "Example Usage") into a single verification section, and delete the "See ## X above for related details" filler lines and the stale "Next Review Date: 2026-03-06".

Document the actual CLI surface completely (the --day and --progress options exist in main.py's argparse but are missing from the Options table) and merge the six overlapping workflow/response sections into one.

DimensionReasoningScore

Conciseness

The body is heavily padded with template boilerplate unrelated to the task: a generic Risk Assessment table, a Security Checklist, Evaluation Criteria and Test Cases ("Performance: Large dataset → Acceptable processing time" is irrelevant to message generation), and a Lifecycle Status block with a stale "Next Review Date: 2026-03-06". The same two commands are repeated across "Quick Check", "Audit-Ready Commands", and "Example Usage", "When to Use" bullets near-duplicate each other, and filler lines like "See ## Prerequisites above for related details" add tokens without content. It is not a 1 because it never explains concepts Claude already knows (there is no "what is a PDF" padding), but the padding is extensive rather than minor, so it cannot be 3.

2 / 5

Actionability

The usage guidance is fully executable and copy-paste ready: CLI examples (e.g. `python scripts/main.py -m "Atorvastatin" -n "Mr. Zhang"`) match the real argparse options, every documented principle/tone value (loss_aversion, social_norms, commitment, encouraging) matches the actual enums in scripts/main.py, the Python API example's keyword arguments exactly match the real `generate_message` signature (verified at scripts/main.py:391), and concrete text/JSON output examples are shown. The examples cover the common cases (basic, principle selection, JSON output, English), matching the anchor 5 pattern.

5 / 5

Workflow Clarity

The Workflow section gives a clear five-step sequence with checkpoints: validate scope before acting (step 2), a pre-run parse check (`python -m py_compile scripts/main.py`), and an explicit error-recovery fallback path ("If scripts/main.py fails, report the failure point... and provide a manual fallback"), plus an Input Validation section with a fixed out-of-scope response. Not a 5 because the sequence is fragmented across six overlapping sections (Workflow, Example run plan, Implementation Details, Output Requirements, Error Handling, Response Template) and there is no output-verification checkpoint on the generated messages themselves; not a 3 because scope validation and failure fallback are explicitly present.

4 / 5

Progressive Disclosure

Scored against the actual bundle: the 579-line implementation is properly externalized to scripts/main.py rather than inlined, and the single reference (references/audit-reference.md) is a real, clearly signaled, one-level-deep file linked from a dedicated References section. Structure is good with headers throughout and reference paths that all resolve. Not a 5 because the SKILL.md itself is cluttered with boilerplate sections that impede easy navigation, and references to `references/` in Key Features/Implementation Details are vague pointers rather than well-labeled navigation.

4 / 5

Total

15

/

20

Passed

Description

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

The description is auto-generated boilerplate that names the skill but misdescribes its purpose as "academic writing workflows" when the skill actually generates behavioral-psychology-based medication reminder messages. It provides no concrete capabilities, no natural trigger terms (reminder/notification/SMS are absent), and no "what" statement, giving it poor specificity, trigger quality, and completeness. Only the niche domain name keeps distinctiveness and overall score from being lower.

Suggestions

Rewrite the description in third person to state the actual capability: "Generates SMS/push notification medication reminder copy using behavioral psychology principles (social norms, loss aversion, implementation intentions, anchoring)."

Add a 'Use when...' clause with natural trigger phrases users would actually say, e.g. "Use when writing patient reminder texts, medication adherence messages, or push notification nudges for taking medication."

Delete the boilerplate phrases ("academic writing workflows", "structured execution, explicit assumptions, and clear output boundaries") which misdescribe the domain and create trigger conflict with academic-writing skills.

DimensionReasoningScore

Specificity

The description names a domain ("medication adherence message gen") but contains no concrete capability verbs — phrases like "structured execution, explicit assumptions, and clear output boundaries" are pure abstract boilerplate, and it never says the skill generates reminder messages. It scores above 1 only because a specific domain is named (closer to "Names the domain but actions are minimal or generic" than "Helps with documents"), but it cannot reach 3 since zero concrete actions are described.

2 / 5

Completeness

A when-style clause exists ("for academic writing workflows that need..."), but the "what" is completely missing — the description never states that the skill generates SMS/push medication reminder copy from behavioral psychology principles. This matches anchor 2 ("only 'when' is present without 'what'"), exemplified by "Use when working with documents"; it cannot reach 3 because there is no clear statement of what the skill does, and the when-clause points at the wrong domain (academic writing vs. patient medication reminders).

2 / 5

Trigger Term Quality

"medication adherence" and "message gen" are relevant domain keywords, but the natural phrases a user would actually say (reminder, notification, SMS, push message, patient reminder copy) are entirely absent, and the bulk of the text ("academic writing workflows", "structured execution", "explicit assumptions") is template filler that no user would utter as a trigger. This fits "one or two generic keywords; missing the natural phrases users say" better than the synonym-covered anchor 3.

2 / 5

Distinctiveness Conflict Risk

"medication adherence message gen" is a clear niche with few competing skills, but the trigger clause ("academic writing workflows that need structured execution, explicit assumptions, and clear output boundaries") is generic boilerplate that overlaps with any number of writing/workflow skills and invites wrong triggering. Somewhat specific but real overlap risk with similar generic skills — not 4, because the boilerplate trigger guidance would compete with actual academic-writing skills.

3 / 5

Total

9

/

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/Academic Writing/medication-adherence-message-gen/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.