Build and share
Build a survey from a brief
Describe what you need in plain words, and the assistant builds the survey in your SurveyNinja account as a draft
SurveyNinja agent skills are free SKILL.md files that teach Claude Code, Codex, Cursor or Gemini CLI one survey job: build a survey from a brief, check it before launch, find what the results say. The assistant does the work in your SurveyNinja account through the MCP server.
Showing 25 of 25
Build and share
Describe what you need in plain words, and the assistant builds the survey in your SurveyNinja account as a draft
Build and share
Sets up survey logic so that no respondent ever hits a dead end
Build and share
Rewrites your questions so people finish the survey, starting from the data rather than taste
Build and share
Gets the survey ready to hand out so you can still tell which channel each response came from
Build and share
Puts the whole launch together at once: labeled links, announcement copy for each channel and a QR code
Check before launch
Finds what will break on real respondents while the link is still unsent
Check before launch
Tells you whether the responses can be trusted before anyone builds conclusions on them
Understand results
Answers "so what did the survey say" with figures and a conclusion instead of a raw export
Understand results
Turns a hundred lines of free text into a handful of themes with numbers and quotes
Understand results
Tells you whether the difference between variants is real or just noise
Understand results
Compares a survey with its own past, because one figure means little and a change says a lot
Understand results
Tells you whether what you have is enough and how many more responses you need before conclusions hold
Understand results
Answers “why did responses stop” by lining up collection against the edit history
Understand results
Shows which channel brought the right people and which only brought numbers
Understand results
Turns survey results into something you can send: a link, a file or a report with conclusions
Understand results
Tidies up what people see from outside: the survey theme, the report colors and the logo
Deliver responses
Sets up where new responses are announced, by email or in Telegram, and fixes it when they stop arriving
Deliver responses
Sends survey responses to your own address and checks that the receiver accepted them
Deliver responses
Finds why responses never reach your Telegram, Google Sheet, Zapier or webhook, and what to do about it
Keep the account tidy
Shows in one report where your workspace is losing responses, storage and attention
Keep the account tidy
Sorts, archives, copies and cleans, and knows which of those cannot be undone
Keep the account tidy
Finds out why a colleague cannot see the surveys and grants exactly the rights they need
Keep the account tidy
Removes test runs and duplicates from your results and shows you the list before anything goes
Try another word or clear a filter.
A skill stores and runs nothing itself. The assistant reads your surveys through the SurveyNinja MCP server, with your permissions, and the skill tells it how to do the job well.
Works with Claude CodeCodexCursorGemini CLI
Step-by-step setup for Claude, ChatGPT, Cursor and VS Code →
No SurveyNinja account yet? Create one free →
Add this address in your assistant, then choose Allow access or paste a key from the API / MCP page. Every plan includes it, Free too.
https://mcp.surveyninja.io/mcp/v1Download one skill from its page or the whole set and unzip it into your agent's skills folder: .claude/skills/ in Claude Code, .agents/skills/ in Codex, Cursor and Gemini CLI. Restart the agent.
The assistant picks the right skill up when the task fits. For example:
Check my survey before launch
A SKILL.md file is the agent skills format that Claude Code, Codex, Cursor and Gemini CLI read: a short description that tells the assistant when to use the skill, then plain-language steps and rules. Each SurveyNinja skill is one such file, sometimes with a reference file next to it.
Most people start with Build a survey from a brief, then Pre-launch check before the survey goes out and Survey results summary once responses come in. Download all skills at once and the assistant picks the right one for each request.
A tool gives access: call a method, get data. A skill explains the order of work: where to start, what to ask the person, which tools to call in what sequence and what never to do.
No. A skill is plain text with nothing executable in it. The work is done by the MCP server tools, and you grant access to them yourself with Allow access or an API key. Remove the connector in the assistant or delete the key, and the access ends.
No code. You need an assistant that loads skills from a folder, such as Claude Code, Codex, Cursor or Gemini CLI. Unzip the archive into its skills folder (.claude/skills/ in Claude Code, .agents/skills/ in the others) and restart it. Changing a skill means editing a text file.
Any assistant that supports the Model Context Protocol and loads skills from a folder: Claude Code, Codex, Cursor and Gemini CLI. In Claude Code that folder is .claude/skills/.
The skills are free and download without signing up. The MCP server comes with every SurveyNinja plan, including Free.
The MCP server works on every plan, Free included. Sign up, allow access and ask your assistant to build the first survey.