User Interview Playbook
v1.0.0User Interview Playbook — Battle-tested framework from HeyGen's 937 interviews to PMF. Complete methodology for user screening, interview execution, question...
⭐ 0· 74·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill is an interview playbook and only contains templates, questions, cadences, and debrief formats. It requests no binaries, env vars, installs, or system access — which aligns with its stated purpose.
Instruction Scope
Instructions stay within interview methodology (questions, scripts, recording recommendations, outreach channels). They explicitly recommend mandatory recording (with consent) and screen sharing; these are appropriate for interviews but carry privacy and sensitive-data exposure risks. The SKILL.md does not instruct the agent to access local files, credentials, or to transmit recordings to any specific external service.
Install Mechanism
No install spec or code files are present (instruction-only). This is low-risk: nothing will be written to disk or executed by installation.
Credentials
No environment variables, credentials, or config paths are requested. The external links (GitHub, Telegram) are references only and not required for operation.
Persistence & Privilege
The skill does not request always:true, nor does it attempt to modify agent/system settings. Autonomous invocation is allowed by default but not excessive for an instruction-only skill.
Assessment
This playbook is instruction-only and appears coherent for running user interviews. Before using it: 1) Be careful with screen recordings and screen-sharing — get explicit consent, avoid asking participants to show passwords or private content, and redact or securely store recordings. 2) When contacting users via multiple channels (Telegram/LinkedIn/Discord/email), follow privacy laws and your own privacy policy; do not solicit or collect sensitive credentials. 3) The SKILL.md links to an external GitHub repo and a Telegram handle — verify the repository and author if you plan to follow external materials or contact the author. 4) If you plan to store recordings or notes in a central location, ensure access controls and retention policies are in place (GDPR/CCPA considerations). Overall technical risk is low, but pay attention to operational and privacy safeguards.Like a lobster shell, security has layers — review code before you run it.
latestvk977f3v1x2w68hjphqqw3c7svd83jeec
License
MIT-0
Free to use, modify, and redistribute. No attribution required.