plugins/pm-health/skills/clinical-trial-protocol/SKILL.md
Draft a clinical trial protocol synopsis with the elements regulators and IRBs expect. Use when asked to write a clinical trial protocol, a study protocol synopsis, a trial design, or to structure endpoints/eligibility/statistics for an interventional study. Produces a structured protocol synopsis — objectives, design, population with eligibility, interventions, endpoints, statistics, and safety/ethics — for expert review. (For non-clinical/UX research, use research-protocol.)
npx skillsauth add mohitagw15856/pm-claude-skills clinical-trial-protocolInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A clinical trial protocol stands or falls on a few linked decisions: a clear objective, a design that can answer
it, endpoints that measure it, eligibility that defines who's studied, and a statistical plan that can detect the
effect. This skill drafts a protocol synopsis that makes those decisions explicit and internally consistent, in
the structure IRBs/ethics committees and regulators expect. (For a general academic or UX study, use
research-protocol.)
Safety & compliance note: this is a drafting aid for expert review, not regulatory, medical, or statistical sign-off. Real trials require qualified investigators, a statistician, and IRB/ethics and regulatory approval (e.g. GCP, ICH, local law). Do not invent efficacy/safety data; mark assumptions for the study team to set.
Given "a phase II trial of drug X for condition Y", produce the full synopsis anyway — infer a defensible design, endpoints, and eligibility appropriate to the phase and condition, and clearly label every inferred choice as a draft assumption for the study team and statistician to confirm. Never fabricate prior data or effect sizes; state them as placeholders to be set.
Ask for these only if they aren't already provided (else infer and label as draft):
Close with assumptions to confirm and a reminder that a qualified investigator and statistician must own the final protocol.
Clinical research practice — objective-endpoint-analysis alignment, explicit eligibility, sample-size justification, and ICH-GCP safety/ethics structure.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.