Individual skill
talk-to-users
Run developer customer discovery via a Technical Advisory Board (TAB). Use when the user has never interviewed a user who isn't a friend, is inventing messaging from a conference room, or is guessing at the roadmap instead of hearing the pain firsthand.
skills/03-talk-to-users/SKILL.md
Source commit 7919aa3d559bcf170c7ab20a8919d44eec5a7e2e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 340
- Repository last updated
- Nov 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-founders Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- dev-tools Repository topic
- developer-marketing Repository topic
- founder-tools Repository topic
- go-to-market Repository topic
- gtm Repository topic
- positioning Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,595 bytes
Read excerpt
# Talk to users (the TAB system)
> The best marketing to developers comes from talking to developers. That's it. Everything else in this repo is downstream of this skill.
**Use this when:** you've never done a real user interview, your messaging is clever but unverified, or you keep debating the roadmap internally instead of asking the people who feel the pain.
## The core idea
Stand up a **Technical Advisory Board**: 30-50 people who *represent your users and buyers*, not grey-haired advisors telling you how to build. You interview them, on repeat, and let their words become your positioning, roadmap, and homepage copy.
A TAB call is **not a demo and not a sales call.** It's an interview. You never mention the product.
## Framework: the TAB system (Frankl)
