SKILL

engaging-survey

Design, review or rewrite a survey or questionnaire so busy people want to answer it AND the answers are worth having; stakeholder and partner surveys, user-needs assessments, post-workshop or kickoff follow-ups, customer and community feedback forms, Google Forms / Typeform / Qualtrics drafts. Use whenever someone shares a survey draft, asks to "make this survey better / shorter / less boring / more engaging", asks what questions to put to users or partners, is turning a meeting or kickoff into a follow-up form, or calls a questionnaire long, dry, or a slog; even if they never say "survey" (e.g. "what should we ask the working groups", "draft the form for the stakeholders"). Not for bias-only wording audits of a finished instrument (a linter does that) or for interview guides alone.

Target: Design & content creation. Automatically collected · unverified.

Excerpt from the author’s documentation

Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.

Read the original text

Topics in the source

  • Engaging surveys: excitement in the frame, neutrality in the questions
  • The one idea
  • Step 1. Name the decisions before touching a question
  • Step 2. Set an honest budget
  • Step 3. Sharpen the questions you kept
  • Step 4. Write the frame (this is where the excitement goes)
  • Step 5. Check the platform and the rules before anyone builds it
  • Step 6. Pilot it on two or three real respondents

People answer when trust × reward outweighs effort (Dillman's social exchange, as Caroline Jarrett puts it). A survey about something exciting usually fails by being long and dry. The fix is to put the energy in the frame: who is asking, the picture of what this makes possible, what happens next, the thank-you. The questions stay neutral, concrete and quick. An exciting frame with neutral questions gets both enthusiasm and honest data. Loaded or promotional questions get neither (AAPOR: a survey must not be used to sell or to produce a predetermined result). So for every draft you touch, do two separate jobs: cut and sharpen the questions, then write the frame. Don't mix them. The evidence behind each rule, with sources, is in references/evidence.md. Read it when you need to justify a recommendation to the survey's owners; quoting their own field's guidance persuades better than your opinion does. Ask, or infer from the material: what will the owners do differently depending on the answers? Write 3–6 decisions down (e.g. "which working groups to staff first", "which heat variable to prioritise for the first product"). Then go through every question in the draft: Keep it only if you

This is an excerpt. Refer to the complete source and its current requirements.

Source repository
Lmandrake/MandrakeWorkflows
Source file
skills/engaging-survey/SKILL.md
Fixed revision
1874105936272447e2f9c81ba1dac48dae6ed074
Read the complete original documentation ↗

Requirements

  • Only the author’s Skill metadata is included. Read the full instructions to check dependencies, licensing and conditions of use.

A small first task

先阅读原作者说明,再决定是否在自己的 AI 工具中使用。

Instructions for your AI tool

Author documentation is not live verification by this site. Without evidence, we do not mark a resource as compatible, safe or free.

Sources and evidence

This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.

Author: Lmandrake/MandrakeWorkflows · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-11T03:01:44.637Z.

Categories are inferred from names, descriptions and paths. They do not establish compatibility.

License and attribution

MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.

Original license ↗

Synchronization, copying and user-reported success do not mark a resource as runtime-tested.

Limitations and notes

  • Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.