← ClaudeAtlas

qualtrics-opslisted

Operate or audit a live Qualtrics survey via the v3 APIs without breaking fielding — publish gating, quotas, flow routing, embedded data, panel-vendor redirects, read-back verification, and a read-only pre-fielding audit. Use when publishing or patching a fielding instrument, when a quota counts but never blocks, when wiring panel-vendor redirects or flow gates, or when auditing a survey before launch (consent-before-anything gates, force-response completeness, quota and redirect checks, anti-bot instrumentation, and language-arm symmetry).
scdenney/open-science-skills · ★ 57 · AI & Automation · score 74
Install: claude install-skill scdenney/open-science-skills
# Qualtrics Live-Survey Operations ## Instructions ### 1. When to use This skill covers **operating** a survey already built and imported into Qualtrics — publishing, quotas, flow routing, live text patches, panel-vendor integration, security options — on an instrument that is or will be fielding real respondents. It is not survey design or QSF construction; assume the survey definition already exists and the question is how to change it without breaking what respondents currently see. Two modes. The default is **operations**: sections 2-8 below govern any write to a live instrument. **Audit mode** (`$qualtrics-ops audit`) is the read-only pre-fielding assessment in the section at the end — it produces ranked findings and makes no changes, and any repair it surfaces comes back through the operations sections as a separate, authorized change. The write-safety rules in section 2 are the shared frame for both: audit mode never writes at all, and operations never publish or activate by accident. ### 2. Non-negotiables **Backups first, always.** Pull and save the survey definition (and flow and options as separate JSON) before any write. Qualtrics version restore exists but is coarse and carries data-risk caveats; your pre-change snapshot is the only *precise* recovery path, and the only one that covers objects (quota counters, options) outside version history. **Verify by read-back, never by absence of error.** A 200 response proves the API accepted the request, not that r