skills/research-protocol/SKILL.md
Write a structured research protocol or study design document. Use when asked to write a research protocol, study protocol, research plan, methodology section, or research proposal. Produces a complete protocol with objectives, methodology, ethical considerations, and analysis plan.
npx skillsauth add mohitagw15856/pm-claude-skills research-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.
Produces structured research protocols for academic, clinical, social science, or market research studies.
Version: 1.0 | Date: [Date] | PI: [Name, institution]
Primary: [One clear answerable question or hypothesis] Secondary: [Additional questions]
Inclusion criteria: [List] Exclusion criteria: [List] Sample size: [n] — Basis: [Power calculation or saturation rationale] Recruitment: [Method and source]
For interventional: intervention description, control, randomisation, blinding For observational/qualitative: data collection methods, tools, data collectors
Primary outcome: [Measure], assessed by [method], at [timepoint] Secondary outcomes: [Measure], [method], [timepoint]
Quantitative: [Statistical test], [missing data handling], [software] Qualitative: [Framework — e.g. Braun & Clarke], [quality assurance]
| Phase | Activities | Start | End | |---|---|---|---| | Setup | Ethics, approvals, tool development | | | | Recruitment | | | | | Data collection | | | | | Analysis | | | | | Write-up | | | |
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.