About participant-operations-hub
A participant operations skill for research teams coordinating recruitment, screening, scheduling, compliance, and incentives for qualitative or quantitative studies. It provides an end-to-end workflow and templates for communications, while covering privacy and audit records.
Key features
- 01Capture recruitment profiles, quotas, and consent needs
- 02Screening, manual review, and stakeholder sign-off
- 03Scheduling, reminders, backups, and localization support
- 04Agreements, data retention, and anonymization workflows
- 05Incentives, tax forms, and audit logs
- 06Recruiting tracker, email sequences, and fulfillment checklists
Use cases
- 01Coordinating participants for qualitative or quantitative studies
- 02Managing privacy, NDAs, and incentive tax compliance
- 03Centralizing participant communications across projects
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ gtmagents/ gtm-agents --skill participant-operations-hubAfter installing, type/participant-operations-hubin Claude Code to confirm it loaded.
Details
From the project READMEParticipant Operations Hub Skill
When to Use
- Running qualitative or quantitative studies that require participant coordination.
- Ensuring compliance with privacy, NDAs, and incentive tax regulations.
- Centralizing communications with participants across multiple projects.
Framework
- Recruiting Intake – capture persona, quota, source, incentive, consent requirements.
- Screening & Approval – automated screeners, manual reviews, and stakeholder sign-off.
- Scheduling & Logistics – calendars, reminders, backups, language/localization support.
- Consent & Compliance – template agreements, data retention policy, anonymization workflow.
- Incentive Fulfillment – payment processor, W-9 or tax forms, fulfillment SLA, audit log.
Templates
- Recruiting tracker with status, notes, and consent links.
- Email sequences for invite, confirmation, reminder, thank-you.
- Incentive fulfillment checklist + finance handoff doc.
Tips
- Keep participant PII in a restricted workspace; expose IDs/tags externally.
- Track over-contact frequency to avoid panel fatigue.
- Pair with
orchestrate-qualitative-labandlaunch-quantitative-surveyfor hands-free logistics.
Comments
Markdown supported