Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add liqiongyu/lenny_skills_plus --skill designing-surveysgit clone --depth 1 https://github.com/liqiongyu/lenny_skills_plusWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/designing-surveys)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/designing-surveys"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/designing-surveys/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/designing-surveys"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/designing-surveys.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.01990 |
| Opus 5 | $0.00016 | $0.00995 |
| Sonnet 5 | $0.00007 | $0.00398 |
| Haiku 4.5 | $0.00003 | $0.00199 |
Grade A, and why
designing-surveys scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designing Surveys
Scope
Covers
- Designing product surveys that answer a specific decision (not “general feedback”)
- Choosing the right audience, sampling, and timing (including “best customers” cohorts)
- Writing clear, unbiased questions and using good scales (CSAT vs NPS guidance)
- Building an instrument that works on mobile (logic, required fields, option visibility)
- Planning analysis and turning results into decisions and follow-ups
When to use
- “Design a customer survey for…”
- “Create an onboarding survey to profile users / separate buyer vs user.”
- “We need a CSAT/NPS/PMF survey.”
- “Draft a cancellation / churn survey.”
- “Help me write survey questions and an analysis plan.”
When NOT to use
- You need deep “why” stories and behavioral context (use
conducting-user-interviews); surveys capture what/how-much, not rich narratives - You already have feedback data to analyze (use
analyzing-user-feedback); this skill designs new collection instruments, not synthesis - You need to measure causal impact of a change (use an experiment/A/B test, not a survey)
- You need task-based usability evaluation of a flow or prototype (use
usability-testing) - You need a holistic PMF assessment beyond the survey instrument itself (use
measuring-product-market-fitfor the full framework) - Your reachable sample is extremely small (n < ~30) and you need directional insight — interviews may be better
- The topic is high-risk (legal/medical/safety) or requires formal survey science review; involve an expert
Inputs
Minimum required
- Product + target user(s)/segment(s)
- The decision to make (what will change based on the survey) + deadline
- Survey type (e.g., onboarding profiling, CSAT, NPS, PMF, churn, feature discovery)
- Distribution channel(s) (in-product, email, customer success, etc.) + sampling constraints
- Privacy/compliance constraints (what data you can/can’t collect)
Missing-info strategy
- Ask up to 5 questions from references/INTAKE.md.
- If still missing, proceed with explicit assumptions and list Open questions that would change the design.
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- eval/eval_config.json 809 B
- eval/SHOWCASE.md 5.3 KB
- eval/with_skill.md 19 KB
- eval/without_skill.md 5.5 KB
- README.md 1.8 KB
- references/CHECKLISTS.md 2.8 KB
- references/EXAMPLES.md 2.1 KB
- references/INTAKE.md 2.1 KB
- references/RUBRIC.md 5.2 KB
- references/SOURCE_SUMMARY.md 3.3 KB
- references/TEMPLATES.md 4.7 KB
- references/WORKFLOW.md 5.2 KB
- skillpack.json 375 B
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 134 lines · 33 tokens per session scan A 11b18953b8b6
designing-surveys is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (52 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,990 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
cangjie-skill
A process for turning a book, course, podcast, interview, long video, or other long material into reusable instructions for an AI agent. It extracts methods and principles, checks them, and packages them as skills.
plan
Use when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. One chain-starter that amplifies the prompt, designs the approach, and decomposes it into a batched task file, skipping whichever phases the request…
loop-library
Compatibility alias for Loopy. Use only when an existing installation or older instruction explicitly invokes loop-library; use Loopy for new installations and requests. Provides the same discovery, recommendation, audit, repair, adaptation, guided crafting, bounded execution, run debrief, project loop saving, and…
naval-almanack
A reference guide for applying ideas from The Almanack of Naval Ravikant, a book about wealth, work, happiness, judgment, and long-term thinking. It routes questions to the relevant topic guidance and notes when professional help is needed.
decision-heuristics
A set of heuristics for making difficult personal decisions such as changing jobs, buying a home, moving, forming a partnership, or getting married. It is intended for major choices, not everyday decisions.
hourly-rate-time
A time-management method based on assigning a high personal value to each hour. It treats time as a limited resource and uses that value to decide which tasks to do, outsource, or skip.