CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

patient-recruitment-ad-gen

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

Quality

64%

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

Quality

Content

56%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 skill contains a strong domain core — IRB/EC essential elements, prohibited content rules, structured inputs, and an executable script path — wrapped in a large amount of template boilerplate that inflates token cost without adding guidance. The References section points at files that do not exist, and the main example embeds a non-portable personal path, both of which would confuse an executing agent.

Suggestions

Delete or collapse the boilerplate sections (Key Features, Dependencies, Implementation Details, Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) and the repeated scope statements; they roughly double the file without adding skill-specific instruction.

Fix the References section to match the actual bundle: remove the nonexistent 'plain_language_guide.pdf' and correct 'template_examples/' to the real file 'references/template_examples.md'.

Replace the hardcoded '/Users/z04030865/.openclaw/...' path in the example with the relative 'scripts/main.py' form already used elsewhere, and add an explicit output-validation step (check generated ad against the Prohibited Content list before returning it).

DimensionReasoningScore

Conciseness

The body is noticeably padded: the scope sentence is repeated verbatim in three sections; 'Key Features', 'Dependencies', 'Example Usage', and 'Implementation Details' open with self-referential filler ('See ## Prerequisites above for related details') that adds no information; and generic boilerplate (Risk Assessment table, Security Checklist, Evaluation Criteria, Lifecycle Status) consumes a large share of the file without teaching anything Claude doesn't know. It escapes score 1 only because the genuinely domain-specific material (IRB/EC essential elements, prohibited content, reading-level requirements) is not something Claude already knows and earns its place.

2 / 5

Actionability

Concrete guidance dominates the useful parts: an explicit input parameter block, a full multi-flag example invocation of scripts/main.py, an output structure specification, and executable verification commands ('python -m py_compile scripts/main.py', 'python scripts/main.py --help'). It falls short of 5 because the primary example hardcodes a personal absolute path ('/Users/z04030865/.openclaw/workspace/skills/...'), which is not copy-paste portable, and the referenced example directory '20260318/scientific-skills/...' does not exist in the bundle.

4 / 5

Workflow Clarity

The Workflow section gives a clear five-step sequence with an explicit validation checkpoint (Quick Check compile step), an early-stop rule for out-of-scope requests, and a fallback path when execution fails or inputs are incomplete ('If scripts/main.py fails, report the failure point... and provide a manual fallback'). Not a 5 because the workflow steps themselves are abstract ('Return a structured result that separates assumptions, deliverables, risks') rather than concrete per-step commands, and there is no validation of the generated output (e.g., checking the ad against the prohibited-content list).

4 / 5

Progressive Disclosure

References are one level deep and clearly signaled, but the file listing does not match the actual bundle: 'plain_language_guide.pdf' and the 'template_examples/' directory do not exist in references/, while the real file 'template_examples.md' is mislabeled. Meanwhile roughly 90 lines of detailed compliance checklists (Essential Elements, Prohibited Content) and generic admin sections are inlined in SKILL.md that could live in reference files. This sits between 'references present but not clearly signaled / content that should be separate is inline' (3) and 'references mostly clear, minor organization gaps' (4) — the phantom references push it to 3.

3 / 5

Total

13

/

20

Passed

Description

57%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 states a clear, well-scoped purpose in a niche domain with low conflict risk, but it omits any 'use when' trigger guidance and lacks the natural trigger phrases and synonym coverage that would let a user (or Claude) reliably select this skill. It reads as a single-action mission statement rather than a complete trigger description.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating patient recruitment ads, flyers, or study announcements for clinical trials that must pass IRB/EC review.'

Include natural synonyms users actually say: 'patient recruitment', 'trial flyer', 'study advertisement', 'IRB-approved ad'.

Enumerate the concrete actions offered (draft ad copy in plain language, check it against IRB/EC essential elements and prohibited-content rules, output print/digital/social-media formats) instead of the single verb 'generate'.

DimensionReasoningScore

Specificity

The description names the domain ('recruitment advertisements for clinical trials') and one concrete action ('Generate') with quality modifiers ('ethical, compliant, and patient-friendly'), matching the anchor for 1-2 concrete actions that are not comprehensive. It is above score 2 because the action is specific rather than generic processing, but below 4 because 'generate' is the only action listed — no mention of drafting variants, reviewing for compliance, or formatting for channels.

3 / 5

Completeness

The 'what' is clear (generate compliant recruitment ads for clinical trials), but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is not a 4 because 'when to use' is entirely absent rather than merely under-specified.

3 / 5

Trigger Term Quality

It contains relevant keywords ('recruitment advertisements', 'clinical trials', 'patient-friendly') but misses the most natural phrasing users would say, such as 'patient recruitment', 'trial flyer', 'study ad', or 'informed consent materials'. Fits 'some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

Clinical-trial patient recruitment advertising is a clear niche with distinct triggers (IRB/EC compliance, clinical trial ads) and minimal overlap risk with other skills. Matches the 'clear niche with distinct triggers' anchor.

5 / 5

Total

14

/

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