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 whawkinsiv/solo-founder-skills --skill customer-researchgit clone --depth 1 https://github.com/whawkinsiv/solo-founder-skillsWrote 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/whawkinsiv/solo-founder-skills/customer-research)<a href="https://agentmods.dev/skills/whawkinsiv/solo-founder-skills/customer-research"><img src="https://agentmods.dev/badge/skills/whawkinsiv/solo-founder-skills/customer-research/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/whawkinsiv/solo-founder-skills/customer-research"><img src="https://agentmods.dev/badge/skills/whawkinsiv/solo-founder-skills/customer-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00099 | $0.02171 |
| Opus 5 | $0.00049 | $0.01086 |
| Sonnet 5 | $0.00020 | $0.00434 |
| Haiku 4.5 | $0.00010 | $0.00217 |
Grade A, and why
customer-research 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Research & Personas
Personas based on demographics are useless. Personas based on behaviors, goals, and constraints drive decisions. This skill helps you run interviews, apply Jobs-to-be-Done, and build personas that actually inform your product.
Core Principles
- Personas based on demographics are useless. "34-year-old male marketer" tells you nothing about product design.
- Personas based on behaviors, goals, and constraints drive decisions.
- The goal of research is to discover what users DO, not what they SAY they want.
- Five good interviews reveal 80% of usability issues.
- Jobs-to-be-Done > traditional personas for SaaS product decisions.
Jobs-to-be-Done Framework
A "job" is the progress a user is trying to make in a specific circumstance.
Job statement format: "When I [situation], I want to [motivation], so I can [desired outcome]."
Examples:
- "When I'm preparing for a board meeting, I want to pull together our key metrics quickly, so I can spend my time on the narrative, not the data."
- "When a new developer joins our team, I want to get them productive on day one, so I can maintain our shipping velocity."
Discover jobs by asking:
- "Walk me through the last time you [did the thing]."
- "What were you trying to accomplish?"
- "What did you try first? What happened?"
- "What was frustrating about that?"
- "What would 'good enough' look like?"
- "What would 'amazing' look like?"
Behavioral Persona Template
## [Persona Name] — [One-line role description]
### Behavioral Segment
What behavior defines this group? (e.g., "Uses the product daily for team
coordination" or "Evaluates tools quarterly for the team")
### Primary Job
[Job statement in JTBD format]
### Context
- Role and responsibilities (relevant to product usage)
- Team size and structure
- Tools they use alongside yours
- Technical sophistication level
- Decision-making authority (buyer, influencer, user)
### Current Workflow (without your product)
Step-by-step: How do they accomplish this job today?
Where are the friction points?
### Key Pain Points
1. [Specific, observed pain — not assumed]
2. [Another specific pain]
3. [Another specific pain]
### Success Criteria
How do they measure whether the job is done well?
What would make them say "this is working"?
### Objections / Barriers to Adoption
What would prevent them from trying or buying?
### Trigger Events
What circumstances push them to seek a new solution?
(Team growth, tool sunset, new mandate, frustration peak)
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 · 226 lines · 99 tokens per session scan A 615e14d11b10
customer-research is a skill published in the GitHub repository whawkinsiv/solo-founder-skills (243 stars, last pushed 16d ago), licensed MIT. It adds 99 tokens to every session and 2,171 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…