Skip to content
TrustedSkillsbeta
Back to all skills

Discovery Interview Prep

Checked
deanpeters·vlatest·other

This skill guides you through a structured "Discovery Interview" to uncover your core values and career goals, leading to more fulfilling job searches.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add deanpeters/product-manager-skills --skill discovery-interview-prep -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

deanpeters

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned deanpeters/product-manager-skills at cfcb697f14.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 421 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill helps users prepare for discovery interviews. It provides a framework and guidance to conduct effective interviews, ensuring key information is gathered and documented. The goal is to surface user needs and pain points that can inform product development decisions.

When to use it

  • When starting a new product or feature and needing to understand user problems.
  • To validate assumptions about existing products or features.
  • Before designing prototypes or conducting usability testing.
  • During exploratory research phases to uncover unmet needs.

Key capabilities

  • Interview framework guidance
  • Question suggestion
  • Documentation template

Example prompts

  • "Help me prepare for a discovery interview with potential users of our new mobile app."
  • "Give me some questions I can ask during a user interview about their current workflow."
  • “What should I document after conducting a discovery interview?”

Tips & gotchas

The skill assumes basic familiarity with user research principles. While it provides guidance, tailoring the interview approach to specific contexts is still crucial for optimal results.