medication-adherence-message-gen

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

Quality

41%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/medication-adherence-message-gen/SKILL.md

Quality

Content

65%

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

The body is genuinely actionable with concrete commands, examples, and output formats, but it is inflated with repetitive boilerplate and generic checklist sections, and its workflow/navigation are weakened by confusing forward-references and a thin reference file.

Suggestions

Remove the redundant boilerplate sections (e.g. merge "Quick Check" and "Audit-Ready Commands," drop the generic Risk/Security/Evaluation/Lifecycle checklists) to tighten the token budget.

Make the Workflow steps skill-specific (e.g. select principle -> build message from template -> output text/JSON) instead of generic process guidance.

Fix the confusing "See `## X` above" references — these point to sections that appear later — by reordering sections or converting them to actual links.

Dimension	Reasoning	Score
Conciseness	The body holds genuine usable content (options table, CLI/Python examples, output formats) but is padded with repeated boilerplate sections ("When to Use," "Key Features," "Implementation Details," "Quick Check," "Audit-Ready Commands") and generic checklists (Risk Assessment, Security Checklist, Lifecycle Status) that add little skill-specific value.	2 / 3
Actionability	It provides copy-paste-ready, executable guidance: concrete CLI examples, a complete options table, a Python API example using the verified `generate_message` function, and concrete text/JSON output samples.	3 / 3
Workflow Clarity	A numbered Workflow and Response Template are present with stop-early/fallback checkpoints, but the steps are generic ("Confirm the user objective," "Validate the request") rather than skill-specific, and confusing forward-references ("See `## Workflow` above") point to sections that appear later in the document.	2 / 3
Progressive Disclosure	One real one-level-deep reference exists and is linked (references/audit-reference.md, verified present), but the body is a long monolithic wall with redundant boilerplate that could be split out, and cross-references are confusing rather than clearly signaled.	2 / 3
	Total	9 / 12 Passed

Description

17%

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 frontmatter description is mismatched to the skill's real purpose — it frames a medication adherence message generator as a generic academic-writing workflow tool — and contains no concrete actions or natural trigger terms a user would actually say.

Suggestions

Rewrite the description to state the concrete action, e.g. "Generates personalized SMS/push medication reminder messages using behavioral psychology principles."

Add a natural-trigger "Use when..." clause referencing terms users would say: medication reminders, adherence messages, patient notifications, dose reminders.

Replace the generic "academic writing workflows" framing with the skill's actual medication-adherence niche to reduce conflict with unrelated skills.

Dimension	Reasoning	Score
Specificity	The description names a domain ("academic writing workflows") but lists only abstract process qualities ("structured execution, explicit assumptions, and clear output boundaries") rather than concrete actions; the skill's real action — generating medication adherence reminder messages — is never stated, matching the vague/abstract anchor.	1 / 3
Completeness	It includes an explicit "Use ... for ..." trigger clause, so it is not capped at 1 by the missing-trigger rule, but the "what" is generic and mismatched and the "when" targets academic writing rather than the skill's actual purpose.	2 / 3
Trigger Term Quality	Terms like "academic writing workflows," "structured execution," and "explicit assumptions" are not what a user would say to invoke a medication reminder generator, and the natural triggers (medication reminders, SMS/push notifications, adherence messages) are entirely absent.	1 / 3
Distinctiveness Conflict Risk	"Academic writing workflows that need structured execution, explicit assumptions, and clear output boundaries" is very generic and overlaps many writing skills, while failing to describe the medication-adherence niche, so it would conflict with other skills and miss its own trigger.	1 / 3
	Total	5 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: aipoch/medical-research-skills
Commit: 7cc5680

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.