patient-recruitment-ad-gen

Generate ethical, compliant, and patient-friendly recruitment advertisements for clinical trials.

Quality

53%

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/patient-recruitment-ad-gen/SKILL.md

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 delivers specific, domain-relevant guidance on compliance requirements and usage, but it is weighed down by generic boilerplate, a non-portable example path, a missing output-validation checkpoint, and two broken reference paths. Tightening the template cruft and fixing navigation would lift all four dimensions.

Suggestions

Remove the generic template boilerplate (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria, Response Template, and the 'See `## X` above' placeholders) so every remaining token earns its place.

Fix the broken references: `references/plain_language_guide.pdf` is missing and `template_examples/` is actually `references/template_examples.md` — correct or remove these paths so navigation works.

Add an explicit output-validation checkpoint to the Workflow, e.g. 'verify the generated ad against the Essential Elements and Prohibited Content checklists before returning', since the deliverable is compliance-critical.

Dimension	Reasoning	Score
Conciseness	The body contains genuinely specific content (compliance elements, input parameters, output structure) but is padded with large amounts of generic template boilerplate — Risk Assessment table, Security Checklist, Lifecycle Status, Evaluation Criteria, Response Template — and repeated 'See `## X` above for related details' placeholders that could be removed. It is mostly useful but noticeably overweight.	2 / 3
Actionability	Concrete guidance is present (real CLI flags, a typed input-parameter block, executable checks like `python -m py_compile scripts/main.py`), but the main example uses a hardcoded personal path (`/Users/z04030865/.openclaw/...`) that is not portable, so it is not fully copy-paste ready and key details are missing.	2 / 3
Workflow Clarity	A sequenced 5-step Workflow exists with a scope-validation checkpoint (step 2), a Quick Check, and a fallback path (step 5 / Error Handling). However, for compliance-critical output there is no explicit checkpoint verifying the generated ad against the Essential Elements and Prohibited Content checklists before returning, leaving an output-side validation gap.	2 / 3
Progressive Disclosure	References are signaled with one-line descriptions and three of five map to real one-level-deep files, but two are broken against the actual bundle: `references/plain_language_guide.pdf` does not exist, and `template_examples/` is referenced as a directory when it is actually the file `template_examples.md`. The inaccurate navigation prevents a 3.	2 / 3
	Total	8 / 12 Passed

Description

57%

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 specific and distinctive with a clear niche, but it states only one action, omits common trigger-term variations, and lacks an explicit 'Use when...' clause. Adding trigger guidance and broader natural keywords would raise the weaker dimensions.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when creating patient recruitment ads or materials for clinical trials, IRB/EC ad submissions, or informed-consent advertising.'

List multiple concrete actions (e.g. 'draft, format, and compliance-check recruitment advertisements') instead of a single 'Generate' verb.

Include common trigger variations users would actually say, such as 'patient recruitment ads', 'clinical trial ads', and 'IRB-approved recruitment copy'.

Dimension	Reasoning	Score
Specificity	The description names a concrete domain (clinical trials) and one action ('Generate ... recruitment advertisements') with compliance adjectives, but it lists only a single action rather than multiple specific concrete actions. It is more concrete than vague examples like 'Helps with documents' but not comprehensive enough for a 3.	2 / 3
Completeness	It clearly answers 'what' (generate ethical, compliant, patient-friendly recruitment ads for clinical trials) but has no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	It includes relevant natural terms ('recruitment advertisements', 'clinical trials', 'patient-friendly') a user might say, but misses common variations such as 'ads', 'patient recruitment', 'IRB-approved copy', or 'informed consent advertising'. Coverage is partial rather than the broad variation set expected for a 3.	2 / 3
Distinctiveness Conflict Risk	The niche is specific and distinct — clinical-trial patient recruitment advertising with IRB/EC compliance — making it unlikely to trigger for unrelated skills. It is clearly distinguishable from generic ad-generation or academic-writing skills.	3 / 3
	Total	9 / 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.