25 Questions for a Travel Agency Customer Satisfaction Survey Workspace audit
Shows in one report where your workspace is losing responses, storage and attention
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
- Works with
- Claude Code, Codex, Cursor, Gemini CLI
- MCP tools
- 13, all read only
- Version
- 1.0.1, October 20, 2026
- Made by
- SurveyNinja
- Price
- Free
- Skill file
- SKILL.md
What it does
- Finds responses nobody receives. A live survey with fresh responses and nowhere to send them is the most useful finding of an audit.
- Urgent things come first. Sections go by weight: what is losing data right now sits at the top, what is worth tidying comes after.
- Touches nothing. It is a report. The skill deletes nothing and changes no settings.
Example
You type
Audit my workspace: what is abandoned and where is storage running out?
What the assistant brings back
- 34
- Surveys12 published
- 11
- Draftsuntouched for six months
- 82%
- Storageof the plan's disk space
- 6
- Findings
- "Delivery feedback" collects into silence 47 responses this month, no notifications or integrations
- Webhook to the order system is off switched off automatically after failed deliveries
- Two published surveys with no responses since April the link is no longer shared, or it is broken
- 11 drafts count against the limit last edited in April or earlier
- One invitation is still not accepted sent in July
They are the only findings losing data right now: 47 responses nobody has read, and a webhook that stopped sending. The rest can wait for a calm afternoon.
The findings above are an example. The real report is built from your workspace, and the audit changes nothing.
How it works
- Finds surveys collecting into silencePublished, fresh responses, but no email notification, no integration and no working webhook. Data piles up and nobody knows.
- Checks that notifications really workAn address that never confirmed the letter, a webhook switched off after failed deliveries, an integration the plan no longer allows. Each looks set up and delivers nothing.
- Separates ghosts from draftsA published survey with no responses for months and a draft abandoned after the first question are different stories. Drafts also count against the survey limit.
- Counts storage, limits and accessHow much space is used and by what, which files are over the quota, which limits are close, and who still has an unaccepted invitation.
Try also
- Are there surveys collecting responses that nobody receives?
- Run a workspace audit and tell me where to start cleaning up
What it will not do
- Delete and change nothing during the audit
- Do not call a survey abandoned
- Do not show respondents' personal data
- 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 does the skill check?
Surveys and folders, plan limits, storage and hidden files, members and invitations, and for surveys with fresh responses, where those responses go: email, integrations and webhooks.
What is the most useful thing it finds?
A published survey with fresh responses and no notification, integration or working webhook. Responses pile up and nobody knows about them.
How is a ghost survey different from a draft?
A ghost is published but has had no responses for a long time, so the link is no longer shared or is broken somewhere. A draft was created and abandoned, and it still counts against the survey limit.
Will the skill delete or change anything?
No. Every tool it uses only reads. What to tidy up is your decision, and a cleanup is a separate step with its own confirmation.
Will it list a seasonal survey as abandoned?
No. If a survey looks seasonal, the assistant asks instead of calling it abandoned.
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
The account in one report
Accounts silt up: surveys collecting responses nobody reads, year-old drafts, storage running out, a webhook that switched itself off months ago. The job is to show all of it at once and change nothing.
Reply to the person in the language they write in.
What to gather
Start with get_workspace_list to get the account's workspace_id: most tools
below need it. In the SurveyNinja interface the survey folders are called
"Workspaces" and the whole account is the "account": use those words with the
person.
| What | Tool |
|---|---|
| Surveys and workspaces (folders) | get_quiz_list, get_folder_list |
| Account and the key owner's permissions | get_workspace_details |
| Plan, limits and what remains | get_workspace_tariff |
| Storage and files hidden over the quota | get_workspace_storage_usage, get_workspace_hidden_files |
| Members and invitations | get_workspace_members |
| What one member can actually do | get_workspace_member_access |
| Recent activity of a survey | get_quiz_summary |
| Where responses go | get_quiz_email_settings, get_quiz_integrations, get_quiz_webhooks |
There may be many surveys. Check where responses go for the ones with recent
responses, not for all of them. Archived surveys are not in the regular
get_quiz_list output; ask for the archive separately if it matters.
What to look for
Responses piling up unseen. A published survey with recent responses, no email notification to the author, no enabled integration and no working webhook. The most valuable finding of an audit.
Notifications that only look set up. A recipient address that was never confirmed with the code from the letter receives nothing. A webhook that was switched off automatically after a run of failed deliveries. An integration that is connected but no longer allowed by the plan.
Ghost surveys. Published, but no responses for a long time: the link is no longer shared, or it is broken somewhere.
Drafts. Created and abandoned. They count against the survey limit; archived surveys do not.
Storage. How much is used and by which surveys, and whether files have started to be hidden over the quota. Hidden files look to the author like attachments that disappeared from responses.
Plan limits. What is already hit or close: surveys, responses, members, disk space, email recipients.
Access. Invitations that were never accepted, members whose email is not
confirmed, members with wider access than their work needs. For a member who
looks over-privileged, get_workspace_member_access shows the effective
permissions, per-workspace overrides included; "Own only" in the interface means
the action works only on what that person created.
How to present
In sections, by weight: first what is losing data right now, then what is merely worth tidying.
For each finding: how many objects, which ones, and what specifically to do. Avoid a vague "clean it up". If the person wants the tidy-up done, that is a separate step with its own confirmation.
What not to do
- Delete and change nothing during the audit. It is a report, not a cleanup.
- Do not call a survey abandoned when it may simply be seasonal: ask.
- Do not show respondents' personal data in the report: counts and survey names are enough.
- Do not suggest a plan upgrade or lead to payment. When a limit is hit or files are hidden over the quota, state the fact and stop.
More skills
All skills- Members and access Finds out why a colleague cannot see the surveys and grants exactly the rights they need
- Tidying up the account Sorts, archives, copies and cleans, and knows which of those cannot be undone
- Cleaning up responses Removes test runs and duplicates from your results and shows you the list before anything goes
- Pre-launch check Finds what will break on real respondents while the link is still unsent
- Comparing with past results Compares a survey with its own past, because one figure means little and a change says a lot
- Why responses are not delivered Finds why responses never reach your Telegram, Google Sheet, Zapier or webhook, and what to do about it
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.