Hypothesis
Checked<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
Install on your platform
Showing OpenClaw.
- 1
Run this in your terminal
terminal$
What we know about this skill
Publisher
product-on-purpose
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.
Automated safety checks
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 product-on-purpose/pm-skills at 1cef1a9eae.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 1cef1a9eae
- Scanned
- 5 files, 479 lines
About this skill
What it does
The product-on-purpose-hypothesis skill helps users articulate and validate the core hypothesis behind a product or feature. It facilitates defining the problem being solved, identifying key assumptions about user behavior, and outlining measurable indicators of success. This process ensures alignment on purpose before significant development effort is expended.
When to use it
- New Product Ideas: Before building anything, use this skill to clarify if your idea addresses a real need and how you'll know if it’s successful.
- Feature Development: When adding a new feature, ensure it directly supports the product's core purpose and that its impact can be measured.
- Pivot Decisions: If a product isn't performing as expected, use this skill to re-evaluate the initial hypothesis and identify potential adjustments.
- Team Alignment: Facilitate discussions with stakeholders to establish a shared understanding of the product’s underlying assumptions and goals.
Key capabilities
- Problem Definition: Clearly articulates the problem being solved by the product or feature.
- Assumption Identification: Identifies key assumptions about user behavior and motivations.
- Success Metrics: Defines measurable indicators that will determine if the hypothesis is valid.
- Hypothesis Formulation: Structures these elements into a testable hypothesis statement.
Example prompts
- "Help me define the problem we're solving with our new mobile app."
- "What are the key assumptions underlying our approach to personalized recommendations?"
- "Formulate a product hypothesis for a feature that allows users to share their progress with friends."
Tips & gotchas
The quality of the output depends heavily on the clarity and specificity of your initial input. Be prepared to iterate on the hypothesis as you gather more information or user feedback.