Skip to content
TrustedSkillsbeta
Back to all skills

Epic Hypothesis

Checked
deanpeters·vlatest·data

Epic Hypothesis generates creative, unexpected hypotheses to spark innovation and challenge assumptions – a powerful tool for divergent thinking.

Repository

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 epic-hypothesis -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.

Commit
cfcb697f14
Manifest
skills/epic-hypothesis/SKILL.md
Scanned
4 files, 535 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

The epic-hypothesis skill enables AI agents to generate, refine, and validate product hypotheses using the Epic framework. It structures thinking around specific problem statements, desired outcomes, and measurable success criteria to drive strategic decision-making.

When to use it

  • Formulating initial ideas for new features or products during brainstorming sessions.
  • Validating assumptions before committing resources to development or market testing.
  • Aligning cross-functional teams on a shared definition of success and core problems.
  • Iterating on vague concepts into testable, data-driven product strategies.

Key capabilities

  • Structuring hypotheses using the Epic format (Problem, Outcome, Metric).
  • Identifying key variables and assumptions that require validation.
  • Generating specific experiments to test hypothesis validity.
  • Refining weak or ambiguous ideas into actionable strategic statements.

Example prompts

  • "Create an Epic hypothesis for a mobile app feature that reduces user churn."
  • "Critique this product hypothesis: 'We should add dark mode because users prefer it.' What are the missing elements?"
  • "Generate three alternative hypotheses to test the assumption that our customers need faster load times."

Tips & gotchas

Ensure you provide context about your target audience and current product state for more relevant hypotheses. Avoid using this skill for highly technical implementation details; it is designed for strategic ideation and validation only.