Skip to content
Agentmart
Submit a tool

hypothesis

Turn a product opportunity or proposed change into a falsifiable product hypothesis with target user, expected behavior, success and guardrail measures, risk…

Skill by ThorStarlord

IndexedMIT
Write a review

Chalk Labs

Need help deploying hypothesis?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/thorstarlord-hypothesis

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Turn a product opportunity or proposed change into a falsifiable product hypothesis with target user, expected behavior, success and guardrail measures, risk assumptions, validation approach, and kill criteria. Use when the active agent has a product-hypothesis responsibility and needs a testable bet before implementation. Produce hypothesis_statement and never treat a validation plan as experiment evidence.

Use cases: agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/hypothesis

What's inside

Skill name
hypothesis
Description
Turn a product opportunity or proposed change into a falsifiable product hypothesis with target user, expected behavior, success and guardrail measures, risk assumptions, validation approach, and kill criteria. Use when the active agent has a product-hypothesis responsibility and needs a testable bet before implementation. Produce hypothesis_statement and never treat a validation plan as experiment evidence.
License
MIT
Instructions
39 lines in SKILL.md · view on GitHub

Files (3)

  • SKILL.md
  • methodology.md · references/
  • output-contract.md · references/

SKILL.md (first lines)

# Hypothesis

Satisfy a `product_hypothesis` responsibility by producing `hypothesis_statement`.

## Inputs

Require a target user/segment, an opportunity/problem, and a proposed intervention or belief to test. Prefer an `opportunity_map` and relevant evidence when available.

## Procedure

1. Read [references/methodology.md](references/methodology.md).
2. Express one falsifiable belief linking intervention, target, expected user behavior/outcome, measure, and decision horizon.
3. Separate user behavior from internal business metric where possible.
4. Define a primary measure plus secondary or guardrail measures only when useful and observable.
5. Identify consequential assumptions across value, usability, viability, and feasibility.
6. Define the evidence need and a bounded validation approach, preferring the lowest-cost sufficient evidence source. If empirical work is material, apply `../using-sensemaking/references/experiment-economy-v1.md` before recommending an experiment.
7. Preserve explicit success, pivot, and kill criteria before results exist.
8. Cite supporting evidence and label unsupported premises as assumptions.
9. Render [references/output-contract.md](references/output-contract.md) and return control.

## Stop or downgrade

- If success cannot be falsified under any result, rewrite the hypothesis before returning it.
- If baseline or target values are unknown, keep them unknown or explicitly proposed; do not present invented numbers as observations.
- Do not claim the hypothesis passed or failed without actual experiment or operational evidence.
- Do not launch the test without separate external-action authority when the test changes external state.

## Boundary

```text
hypothesis != experiment warrant
validation approach != experiment requirement
validation approach != validation evidence
hypothesis card != experiment result
```

This Skill may describe what evidence would discriminate the hypothesis, but Experiment Economy owns whether an experiment is warranted.

From ThorStarlord/sensemaking-skills, MIT.

More from ThorStarlord/sensemaking-skills

Signals

Stars
0
Forks
0
Open issues
7
Last commit (this folder)
Sep 21, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from ThorStarlord

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get hypothesis running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying hypothesis?

CallGet help
Cite this page

hypothesis skill. Agent Mart. https://agentmart.dev/skills/thorstarlord-hypothesis (last updated 2026-10-24)