Cleaning up responses

Removes test runs and duplicates from your results and shows you the list before anything goes

Free agent skill for Claude Code, Codex, Cursor and Gemini CLI. It works through the SurveyNinja MCP server, with your permissions.

Category
Keep the account tidy
Tags
cleanup, data quality
Works with
Claude Code, Codex, Cursor, Gemini CLI
MCP tools
10, 7 of them change data
Version
1.0, October 20, 2026
Made by
SurveyNinja
Price
Free
Skill file
SKILL.md

What it does

  • Statistics without junk. Test runs, random clicks and duplicates stop shifting your averages and distributions.
  • A list before any cleaning. You see how many responses, over which period and by which signal before anything changes.
  • Permanent only on your word. The skill starts with hiding, then the trash. Permanent deletion happens only when you ask for it directly.

Example

You type

Remove the test runs from this survey's statistics

What the assistant brings back

64
Selected
undoable
Hidestays in the list
restorable
Trashif you change your mind
on request
For goodonly when you ask
  1. Test runs before the survey was shared, 3 to 6 September the author's own runs while building
  2. Faster than one minute a nine-question survey
  3. Same option in every question straight-lining
  4. Duplicate email addresses one address twice or more
Nothing has been deleted yet

This is a list for your approval. Hiding from reports is the suggested start: the numbers update right away, and the responses stay in place if you need to undo it.

The groups above are an example. The selection rules are chosen for your survey.

How it works

  1. Shows first, acts secondThe list to clean comes with counts, the period and the signal it was selected by. Nothing happens until you have seen it.
  2. Builds groups by signalTest runs before the survey was shared, too-fast completions, straight-lining and duplicate contacts come as separate groups with numbers.
  3. Moves from reversible to finalHiding from reports comes first and can be undone. Then the trash, which can be restored. Permanent deletion happens only when you ask for it directly.
  4. Offers a tag instead of deletionA tagged response stays in the statistics and stands out. "Call back", "complaint" and "duplicate" are easier to work with than a spreadsheet export.

Try also

  • Find duplicate email addresses and show them before deleting anything
  • Tag everyone who left a phone number and a complaint as "call back"

What it will not do

  • Do not delete permanently without explicit consent
  • Do not clean "outliers" by answer value
  • Do not delete responses to improve the numbers
  • Do not suggest a plan upgrade or lead to payment

The skill works with your permissions. Tools that change data are marked, so you check what the assistant is about to do before you confirm. To cut access, remove the connector in the assistant or delete the API key.

In short

What junk does the skill look for?

Test runs made while building the survey, completions too fast to read the questions, straight-lining with the same option everywhere, and duplicates by email or phone.

Will it delete anything right away?

No. First it shows groups with the number of responses, the period and the selection signal. Cleaning starts only after you agree.

What is the difference between hiding and deleting?

A hidden response stays in the list but is left out of reports and the summary, and you can bring it back. A response in the trash can be restored. A permanently deleted response is gone, together with the files the respondent uploaded.

Will it remove low ratings?

No. A low rating is a real answer. The skill does not clean outliers by value and does not delete responses to make the numbers look better.

Why tags if I can delete?

A tagged response stays in the statistics and is marked: "call back", "complaint", "needs work". The skill reuses the tags you already have, so the same tag does not appear under three spellings.

What do I need to use it?

A SurveyNinja account and an assistant that supports MCP and loads skills from a folder, such as Claude Code, Codex, Cursor or Gemini CLI. The MCP server works on every plan, the free one included. You connect with "Allow access" in the assistant or with your own API key.

The full skill

The SKILL.md file the assistant reads, exactly as it is in the archive.

Show the full text

Cleaning up responses

Test runs, random clicks and duplicates distort the statistics. Cleaning brings the reports back to what respondents really said, but part of it cannot be undone, and that is the main thing to keep in mind.

Reply to the person in the language they write in.

Look first, act second

get_quiz_answers with filters (date, completion, sort by start or end time): show exactly what would be affected, meaning how many submissions, over what period, and selected by which signal. Act only after the person agrees.

Hidden responses and those screened out by the survey logic are not in the default output; ask for them with the matching filter when they matter.

What does what

Task Tool
Hide a response from reports and the summary without deleting it toggle_answer_visibility
A short note on a response (up to 100 characters) set_answer_note
Tags on a response tag_answer
Workspace tag list get_answer_tags, create_answer_tag, delete_answer_tag
Move to trash, restore, delete for good delete_quiz_answers
Question order inside a response card set_answers_order_mode

Three levels of removal

  1. Hide. The response stays in the list but leaves reports and the summary. Reversible. The right choice when unsure.
  2. Trash. The response leaves the list and the report but can be restored.
  3. Permanent. Nothing to recover, and the files the respondent uploaded go with it. It needs an explicit confirmation flag, and that confirmation must come from the person in words for the specific volume.

Start at level one. Offer level three only when permanent deletion is explicitly requested. Hidden responses are skipped by trash and permanent deletion: bring a response back into reports first if it really has to go.

What people usually look for

  • Test submissions: the author's own runs while building, usually the earliest ones, before the survey was shared.
  • Too fast: completed quicker than the questions can be read.
  • Straight-lining: the first option everywhere, or one rating throughout.
  • Duplicates by contact: the same email or phone number several times.

Show them as separate groups with counts, not one long list.

Tags and notes

The tag list belongs to the workspace, not to the survey, so the tag tools need the workspace id: take it from get_workspace_list.

Tags beat deletion: the response stays in the statistics but is marked. "Call back", "complaint", "needs work" are easier to work with than an exported sheet.

Read get_answer_tags first and reuse an existing tag. Create a new one only if nothing suitable exists, otherwise the workspace ends up with three spellings of the same thing. tag_answer replaces the tags of a response, so pass the ones it already has together with the new one.

set_answers_order_mode also changes the public link to responses and the Word export, so mention that before switching it.

What not to do

  • Do not delete permanently without explicit consent for the specific volume.
  • Do not clean "outliers" by answer value: a low rating is a real answer.
  • Do not delete responses to improve the numbers.
  • Do not suggest a plan upgrade or lead to payment. If a limit is hit, state the fact and stop.
The SurveyNinja ninja on a rocket

Connect SurveyNinja to your assistant

The MCP server works on every plan, Free included. Sign up, allow access and ask your assistant to build the first survey.