Screener porter

A Claude skill that checks a recruitment screener before launch and helps you copy it into another study or tool without losing which answers qualify people.

RecruitingOctober 12, 2026

Download the skill

Enter your details to download the skill file.

What it does

Copying a recruitment screener between studies or tools by hand loses its logic: which answers qualify someone, and where the answers get saved.

You give it a screener exported from any tool. It tells you whether the screener has problems before you launch it, such as questions that are easy to guess or sensitive questions with no consent, plus a step-by-step plan to copy it into the new study or tool without losing anything. Use it when you're reusing or moving a screener.

What you get back

  • A clean copy of your screener in one standard format, readable by people and by other tools.
  • A pre-launch check with warnings for guessable questions, sensitive data and missing consent text.
  • A nudge to add at least one open question for interview recruiting, so you can hear how people express themselves.
  • A step-by-step plan for copying it into the new study or tool, with the answers that qualify or rule people out kept intact.
  • A note of where each answer gets saved on the participant's profile, and a warning for any branching you'll need to rebuild by hand.
  • A record of red-herring questions, so their reuse gets caught next time.

Install it in Claude, ChatGPT, Copilot or Gemini

The same skill file works in all four. Pick your tool for the steps.

Install in Claude

  1. 1

    Download the skill

    Fill in the short form to get the .skill file.

  2. 2

    Add it to Claude

    In the Claude app go to Settings → Capabilities → Skills and upload the file. In Claude Code, run the npx command shown after the form, or drop the folder into your project's skills folder.

  3. 3

    Just ask

    Ask in plain language. Claude picks up the skill on its own when the request matches.

How to use it

Once it's installed, ask in plain language. Your AI follows the skill's method when the request matches.

Example prompt 1
Copy the screener from last quarter's admin study into the new one.
Example prompt 2
Check this screener before we launch it. Anything that will let the wrong people through?
Example prompt 3
Convert this survey-tool export into something I can import into Great Question.

What it won't do

It won't write a screener from a brief; that is a different job. It also won't write to a research platform without showing you the full plan first, and it won't pass through a question type the destination doesn't support. Those are left for you to decide.

Questions

Which tools can it read screeners from?

Any tool that exports JSON or CSV, plus screeners pasted from a document. It recognises common field names across tools, and reads Great Question screeners directly through the MCP.

Does it need the Great Question MCP?

No. It works on files on its own. With the MCP connected it can also read a screener from a study in your account and plan the import into another one.

What does it check before launch?

Whether questions screen for the research need without giving away the right answer, how many are open-ended, whether sensitive questions have consent and a "prefer not to say" option, whether there is a privacy notice, and length against published drop-off data.