Agent skill

Surveys

by davepoon in davepoon/buildwithclaude

Manages the founder's survey-based validation — crafting the right questions, deploying a survey to the internet, and analyzing results against hypotheses.

MITAuto-check passed

Install Surveys

skills CLI
$ npx skills add davepoon/buildwithclaude --skill surveys -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davepoon/buildwithclaude surveys --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/startup-superpowers/skills/surveys .claude/skills/surveys && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
surveys
GitHub stars
3.6k
Token cost
~1.5k tokens
SKILL.md length
715 words
Files
3 (incl. references)
Skills in repo
246
Repo updated
First seen
Licence
MIT

At a glance

Manages the founder's survey-based validation — crafting the right questions, deploying a survey to the internet, and analyzing results against hypotheses.

  • Works in 2 steps: Just the questions — crafting a tight,… → Active Tally mode — creating the survey…
  • The founder wants to run a survey
  • SKILL.md covers Before you start, Applicability assessment, When no surveys exist and When surveys already exist, plus 1 more section
  • Reaches tally.so

What it does

Surveys is an agent skill from davepoon/buildwithclaude. Manages the founder's survey-based validation — crafting the right questions, deploying a survey to the internet, and analyzing results against hypotheses. Use when the founder wants to run a survey, create survey questions, validate hypotheses at scale, check how a survey is going, understand whether a survey is the right tool right now, or deploy a question set to get quantitative signal. Also bring this up if you believe that creating a survey to collect quantitative evidence may be useful at this point.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/initial-survey-questions.md` and `references/tally-survey.md`).

The repository describes itself as: A single hub to find Claude Skills, Agents, Commands, Hooks, Plugins, and Marketplace collections to extend Claude Code, Claude Desktop, Agent SDK and OpenClaw. The licence is MIT.

When your agent uses it

  • The founder wants to run a survey
  • Create survey questions
  • Validate hypotheses at scale
  • Check how a survey is going

Example prompts

  • “Use the surveys skill to manage the founder's survey-based validation — crafting the right questions, deploying a survey to the internet, and…”
  • “/surveys”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Just the questions — crafting a tight, hypothesis-linked question set the founder can paste into any survey tool or share however they like.
  2. Active Tally mode — creating the survey in Tally via the Tally MCP, returning a shareable link, and later fetching and analyzing results.

What it can do on your machine

Read from SKILL.md and the folder at commit 616deb5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and yaml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • tally.so

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Surveys loads about 1.5k tokens when it runs, and up to ~6k if it reads all its reference files. Until then it costs about 130 tokens; SKILL.md has 715 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~130
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from davepoon/buildwithclaude at commit 616deb5, republished under its MIT licence (© davepoon). 715 words, ~1,532 tokens.

Download SKILL.mdSave it as .claude/skills/surveys/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
surveys
description
Manages the founder's survey-based validation — crafting the right questions, deploying a survey to the internet, and analyzing results against hypotheses. Use when the founder wants to run a survey, create survey questions, validate hypotheses at scale, check how a survey is going, understand whether a survey is the right tool right now, or deploy a question set to get quantitative signal. Also bring this up if you believe that creating a survey to collect quantitative evidence may be useful at this point.

Surveys

Help the founder use surveys as a quantitative validation layer — to confirm patterns found in interviews, prioritize among competing hypotheses, or reach people they can't interview one-on-one.

Surveys are powerful when they're targeted, short, and posted somewhere with the right audience. They're much weaker when deployed before any qualitative discovery, when the distribution channel is vague, or when the questions fish for validation instead of testing assumptions. Part of this skill's job is to help the founder assess fit before building anything.

This skill covers two modes:

  1. Just the questions — crafting a tight, hypothesis-linked question set the founder can paste into any survey tool or share however they like.
  2. Active Tally mode — creating the survey in Tally via the Tally MCP, returning a shareable link, and later fetching and analyzing results.

Before you start

Read startup/core.md to load project context.

Check prior qualitative work: scan startup/hypotheses/ and startup/interviews/. It is sometimes ok to go for a survey without doing interviews, especially if the user knows and/or has access to a good channel to distribute the survey to aquire diverse responses. Procceeding to survey without hypotheses is not recommended. If no hypotheses present, invoke the hypotheses skill and strongly suggest the user to talk about them first.

Scaffold the surveys folder if it doesn't exist yet:

bash
mkdir -p startup/surveys

Applicability assessment

Use judgment when assessing whether surveys make sense right now. This is advisory — never a gate.

Good signals:

  • The founder has run at least a few interviews (surveys confirm patterns, they rarely discover them)
  • There are untested or partially-tested hypotheses that quantitative signal would clarify
  • The founder has (or can reach) a channel with a relevant, targetable audience

Caution signals — raise these, don't block:

  • No interviews done yet: surveys without prior qualitative discovery often surface misleading signal — people answer what sounds good, not what they actually do
  • No identified distribution channel: a well-crafted survey shared with the wrong audience (or no audience) is wasted effort
  • The idea is still being shaped: surveys freeze assumptions; if core.md is still in flux, hypothesis-testing surveys may be premature

If the founder insists on a survey despite caution signals, help them build a good one. The goal is to inform, not gatekeep.


When no surveys exist

Share a brief applicability assessment (2–3 sentences): what's looking solid, what the risk is, whether this is a good moment for surveys. Then ask if they'd like to proceed.

If proceeding, load the reference file:

.claude/skills/surveys/references/initial-survey-questions.md

The reference file's instructions take over from this point.


Show full SKILL.md (300 more words)Show less

When surveys already exist

Load and read the relevant files for context. Infer intent from the conversation — don't mechanically ask "what do you want to do?" If the founder is:

  • Reviewing or editing a survey — load the file, discuss, propose the specific changes, get confirmation, write back
  • Adding a new survey — load initial-survey-questions.md
  • Activating a questions-only survey in Tally — load the relevant survey file to confirm the question set, then load:
    .claude/skills/surveys/references/tally-survey.md
  • Checking results or asking how a survey is going — for now, fetch the Tally submission count via the Tally MCP if configured and share a quick status. Full results analysis workflow (dispatching the survey-analyst subagent) is coming in a later version of this skill.
  • Archiving a survey — read the file, set status: archived, propose the change, get confirmation, write back

When adding or updating surveys, follow these file conventions:

File location: startup/surveys/{YYYY-MM-DD}-{short-descriptor}.md

Slug convention: lowercase, replace spaces and non-alphanumeric characters with hyphens, collapse multiples. "Invoice chasing validation" → invoice-chasing-validation.

Frontmatter:

yaml
---
status: draft|ready|active|closed|archived
mode: questions-only|tally
date_created: YYYY-MM-DD
target_persona: One-line segment descriptor
hypothesis_slugs:
  - slug-one
  - slug-two
response_goal: 30
tally_form_id: abc123          # tally mode only — omit if questions-only
tally_url: https://tally.so/r/abc123  # tally mode only — omit if questions-only
---

Required sections:

  • ## Purpose — why this survey exists and what decisions it will inform
  • ## Target Audience — who should fill it out, response goal, and why that sample size
  • ## Distribution Plan — where to post it and what value is offered to respondents
  • ## Questions — numbered list with question type annotated

Optional sections:

  • ## Notes — founder comments, links to related interviews, context for later
  • ## Results — populated after fetching Tally data

Read before writing, propose before saving, get confirmation.


After saving a survey

Briefly confirm: "Saved to startup/surveys/{slug}.md."

Mention natural next steps without pushing:

  • If mode: questions-only — when ready, the agent can deploy to Tally and return a shareable link
  • If mode: tally and status: active — remind the founder they can ask "how's the survey going?" at any time
  • Triangulating with interviews tends to give the strongest signal: survey results show what, interviews show why

© davepoon, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in plugins/startup-superpowers/skills/surveys of davepoon/buildwithclaude.

  • SKILL.md
  • references/initial-survey-questions.md
  • references/tally-survey.md

Open the folder on GitHubat commit 616deb5

Compare with similar skills

Surveys next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Surveys compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Surveys this skilldavepoon/buildwithclaude3.6k—~1.5kAutomated safety check: PassMIT
Idea Refinementaddyosmani/agent-skills103k6 repos~2kAutomated safety check: PassMIT
HTML PPT Studiolewislulu/html-ppt-skill8.6k4 repos~4.7kAutomated safety check: PassMIT
Agent Browserquran/quran.com-frontend-next1.9k40 repos~3.3kAutomated safety check: PassNone
Brag Launch Videolatent-spaces/brag14k1 repos~2.3kAutomated safety check: PassMIT
Perform Tasktelegramdesktop/tdesktop33k2 repos~3kAutomated safety check: PassGPL-3.0

Similar skills

  • Idea Refinement

    addyosmani/agent-skills

    Guides a conversation that takes a vague idea through divergent and convergent thinking and ends in a markdown one-pager covering scope and assumptions.

    103k GitHub starsUsed in 6 repos~2k tokens
    Agent WorkflowsAuto-check passed
  • HTML PPT Studio

    lewislulu/html-ppt-skill

    Authors static HTML presentations from a library of themes, layouts and animations, with keyboard navigation, for talks, pitch decks and reports.

    8.6k GitHub starsUsed in 4 repos~4.7k tokens
    Documents & OfficeAuto-check passed
  • Agent Browser

    quran/quran.com-frontend-next

    Automates browser interactions for web testing, form filling, screenshots, and data extraction.

    1.9k GitHub starsUsed in 40 repos~3.3k tokens
    Productivity & AutomationAuto-check passed
  • Brag Launch Video

    latent-spaces/brag

    Turns the current project website or app into a short, shareable launch video with Hyperframes, planned from the project code with options for tone, format and voiceover.

    14k GitHub starsUsed in 1 repo~2.3k tokens
    Media & CreativeAuto-check passed
  • Perform Task

    telegramdesktop/tdesktop

    Resolve, start or resume, implement, review, test, and publish exactly one existing ai-tdesktop task by short slug or full dated id, including rare blocked retries and split-required results.

    33k GitHub starsUsed in 2 repos~3k tokens
    Productivity & AutomationAuto-check passed
  • Dependency Watch

    telegramdesktop/tdesktop

    Audit Telegram Desktop dependencies on freshly fetched origin/dev for releases and security fixes, including upstream lag and backport candidates in patched forks.

    33k GitHub stars~2.2k tokensUpdated today
    Productivity & AutomationAuto-check passed

More from davepoon/buildwithclaude

All 246 skills in this repo
  • iOS Hig Design Guide

    davepoon/buildwithclaude

    Build, update, and apply iOS design specifications using Apple Human Interface Guidelines (HIG) source data.

    3.6k GitHub stars~735 tokensUpdated today
    Auto-check passed
  • Video Downloader

    davepoon/buildwithclaude

    Download YouTube videos with customizable quality and format options.

    3.6k GitHub starsUsed in 1 repo~871 tokens
    Auto-check passed
  • Qwen Vision

    davepoon/buildwithclaude

    A skill your agent uses when the user asks to "analyze video", "watch this video", "what happens in this video", "describe this clip", "review this footage", "classify these videos", "compare…

    3.6k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Atlas Cloud Media

    davepoon/buildwithclaude

    Discover Atlas Cloud image and video models, inspect their live schemas, and submit one confirmed media generation request with bounded GET polling.

    3.6k GitHub stars~852 tokensUpdated today
    Auto-check passed
  • Browser Extension Launch

    davepoon/buildwithclaude

    面向没有编程经验的用户,把想法做成可试用的浏览器插件,并完成检查、商店材料、审核提交和上线验证;也用于继续已有插件、排错和发布新版。用户说“帮我做个插件”“把插件上架”“继续我的插件”时使用。普通网站开发、仅查询插件知识不触发。

    3.6k GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Slack Gif Creator

    davepoon/buildwithclaude

    Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives.

    3.6k GitHub starsUsed in 12 repos~4.3k tokens
    Auto-check passed

Questions about Surveys

What does Surveys do?

Manages the founder's survey-based validation — crafting the right questions, deploying a survey to the internet, and analyzing results against hypotheses. Surveys is an agent skill from davepoon/buildwithclaude. Manages the founder's survey-based validation — crafting the right questions, deploying a survey to the internet, and analyzing results against hypotheses.

When should I use Surveys?

Surveys fits situations like: the founder wants to run a survey; create survey questions; validate hypotheses at scale; check how a survey is going.

How do I install Surveys in Claude Code?

Run `npx skills add davepoon/buildwithclaude --skill surveys -a claude-code`. Or copy the skill folder (plugins/startup-superpowers/skills/surveys in davepoon/buildwithclaude) into .claude/skills/surveys in your project. Claude Code loads it when a task matches its description.

How do I install Surveys in Codex?

Run `npx skills add davepoon/buildwithclaude --skill surveys -a codex`. Or copy the skill folder (plugins/startup-superpowers/skills/surveys in davepoon/buildwithclaude) into .agents/skills/surveys in your project. Codex loads it when a task matches its description.

Can I use Surveys in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davepoon/buildwithclaude --skill surveys -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/surveys, .gemini/skills/surveys, .github/skills/surveys and .opencode/skills/surveys in your project.

What does Surveys need to run?

SKILL.md names no scripts, command-line tools or credentials: Surveys is instructions for the agent only.

Does Surveys access the network?

SKILL.md names 1 domain. In commands or code: tally.so; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Surveys safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Surveys use?

Surveys is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Surveys use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.5k tokens, read only when the agent opens those files.

What are the alternatives to Surveys?

Skills that share tags, products or a category with Surveys: Idea Refinement (addyosmani/agent-skills, 103k stars), HTML PPT Studio (lewislulu/html-ppt-skill, 8.6k stars), Agent Browser (quran/quran.com-frontend-next, 1.9k stars) and Brag Launch Video (latent-spaces/brag, 14k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Surveys?

davepoon (a GitHub user) maintains it in davepoon/buildwithclaude, which has 3,605 GitHub stars. The repository holds 246 skills in this directory. The repository was last updated on October 9, 2026.

Source: davepoon/buildwithclaude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.