{"id":42869,"plugin_id":"plugin_asdk_app_699e3e4e050881919b373090d3059dc5","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:07:35.549Z","digest":"af20197abbd6694ad5e4f9c6ba17670042b92f175c9877092d9aa89df0b31d58","against":null,"payload":{"description":"Design, draft, test, launch, and analyze BuildBetter native surveys with evidence-backed questions, audience controls, delivery safeguards, and response synthesis. Use when the user asks to create a survey, add recipients, schedule or activate delivery, configure an in-app intercept, inspect responses, or connect survey results to a BuildBetter View.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":260}],"name":"buildbetter-survey-research","skill_md_contents":"---\nname: buildbetter-survey-research\ndescription: Design, draft, test, launch, and analyze BuildBetter native surveys with evidence-backed questions, audience controls, delivery safeguards, and response synthesis. Use when the user asks to create a survey, add recipients, schedule or activate delivery, configure an in-app intercept, inspect responses, or connect survey results to a BuildBetter View.\n---\n\n# BuildBetter Survey Research\n\nFollow [buildbetter-start’s interaction guidance](../buildbetter-start/SKILL.md#interaction): complete supported work through chat; use optional UI only when it reduces effort or clarifies a decision.\n\n## Safety Contract\n\nSearch organization skills with list-skills and get-skill first. Treat survey creation, audience changes, activation, scheduling, invitations, respondent links, intercept configuration, settings, View connections, and deletion as mutations. Never activate, schedule, send, resend, or attach an audience without explicit approval and a readback of survey, recipients, channel, and timing.\n\nIf any named tool is absent from the registered MCP inventory, report that limitation. Do not use run-query to imitate survey mutations.\n\n## Workflow\n\n1. Define the research decision, target population, evidence gap, sample limitations, analysis plan, and action each result may trigger.\n2. Inspect existing surveys with list-surveys and get-survey. Reuse or update only when the user intends to change that exact survey.\n3. Draft questions manually or with suggest-survey-questions. Remove leading, double-barreled, unnecessary, or non-actionable questions. Put sensitive questions last and make them optional when possible.\n4. Create-survey in an inactive, audience-free state unless the user explicitly approved a bounded audience and activation in the same request.\n5. Review delivery copy, subject, preview text, branding, questions, required fields, consent, thank-you state, View connections, and target channel.\n6. Add recipients only after showing the exact count and identity source. Active email surveys may queue invitations immediately, so keep the survey inactive during audience assembly.\n7. Use send-survey-test-email only after approval of the exact preview address. A test email is a real external message.\n8. For a launch, read back channel, audience count, exclusions, timing, and survey state. Then use update-survey for activation or schedule-survey for one future launch. Verify with get-survey and list-survey-schedules.\n9. For in-app delivery, list-feedback-widgets before configure-survey-intercept. Target only verified recipient identities; review state with list-survey-intercepts.\n10. Analyze through list-survey-responses and get-survey-response. Separate response count, delivery state, answer evidence, AI follow-up text, nonresponse, and sample bias.\n\n## Tool Routes\n\n- Draft: suggest-survey-questions -> create-survey with activation off -> get-survey.\n- Questions and design: replace-survey-questions -> customize-survey -> get-survey.\n- Audience and launch: add-survey-recipients -> send-survey-test-email -> update-survey or schedule-survey -> list-survey-schedules.\n- In-app: list-feedback-widgets -> configure-survey-intercept -> list-survey-intercepts.\n- Results: list-survey-responses -> get-survey-response -> connect-survey-to-view when explicitly approved.\n\n## Output\n\nReport survey ID and state, research goal, question and audience review, channel, exact approved recipient scope, schedule or activation state, test evidence, response coverage, findings, bias, and next decision. Distinguish drafted, tested, scheduled, active, delivered, responded, and analyzed.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}