本文へ移動
cccskills
無料GitHub で公開

hypothesis-framing

Write or refine a research hypothesis. Use when the user says "write a hypothesis", "frame my hypothesis", "is my hypothesis testable", "null and alternative hypothesis", "research hypothesis", "refine my hypothesis", "hypothesis statement", "H0 and H1", "operationalize my hypothesis", "turn my research question into a hypothesis", or needs to convert a research question or intuition into a falsifiable, testable hypothesis with clear variables and predictions - even if they don't explicitly say "hypothesis".

インストール方法を見る

含まれるファイル(1)

  • SKILL.md6.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Overview

Based on Research Design (Creswell & Creswell) and Research Methodology: A Step-by-Step Guide (Ranjit Kumar). A hypothesis is a falsifiable prediction about the relationship between variables. Kumar's rule: a hypothesis that cannot be proven wrong is not a hypothesis - it is a belief. Creswell's standard: every hypothesis must specify the population, the variables, and the predicted direction of the relationship.

The test: can a different researcher, given only the hypothesis, design a study to test it?

Workflow

Step 1: Identify the research question

Start with the question before writing the hypothesis. The hypothesis is the answer you predict the study will find.

Research question: [what are you trying to find out?]
Domain: [field of study]
Context: [setting, population, conditions]
Prior evidence: [what makes this prediction plausible? what is it based on?]

A good research question has:

  • A specific population (not "people" but "adults over 65 with Type 2 diabetes")
  • A specific phenomenon or variable being studied
  • A clear "compared to what" or "under what conditions"

Step 2: Identify and operationalize variables

Variables must be measurable. For each variable, define how it is measured:

Independent variable (IV): [what you manipulate or group by]
  Operationalization: [how exactly it is measured or defined]
  Levels/values: [if categorical: list levels. if continuous: range and units]

Dependent variable (DV): [what you measure as an outcome]
  Operationalization: [specific measure, scale, or instrument]
  Units: [e.g. seconds, score 1-7 on Likert scale, binary yes/no]

Control variables: [variables held constant or statistically controlled]
  [variable]: [how controlled]

Potential confounds: [variables that could explain results without being your IV]
  [confound]: [how you plan to address it]

Step 3: Write the directional hypothesis

A well-formed hypothesis has three components:

  1. Population: who or what
  2. Predicted relationship: direction and nature
  3. Variables: IV and DV named precisely

Format: "In [population], [IV manipulation or condition] will result in [predicted change in DV direction] compared to [control or comparison condition]."

Examples:

  • "Participants who receive spaced-repetition training will score significantly higher on a 30-item vocabulary test at 2-week follow-up than participants who receive massed-practice training."
  • "Remote engineering teams using structured async standup tools will report lower meeting fatigue (measured by the Meeting Load Index) than teams using synchronous daily standups."

Step 4: Write null and alternative hypotheses

H₀ (Null hypothesis): There is no significant difference/relationship between [IV] and [DV]
in [population].

H₁ (Alternative hypothesis - directional): [IV] is associated with [higher/lower/more/less]
[DV] in [population].

Or (non-directional):
H₁ (Alternative hypothesis): There is a significant difference in [DV] between [IV
conditions] in [population].

Use directional H₁ when: prior theory or evidence strongly predicts the direction
Use non-directional H₁ when: this is exploratory or direction is genuinely uncertain

Step 5: State the theoretical basis

Explain what mechanism you expect to be driving the predicted effect:

Theoretical basis: [What theory or prior finding predicts this result?]
Mechanism: [Why would X cause Y? What is the causal pathway?]
Prior evidence: [1-3 citations showing related findings that support this prediction]
Boundary conditions: [Under what conditions do you expect this to hold? Under what conditions might it not?]

Step 6: Check falsifiability and precision

Run through these questions before finalizing:

  1. Falsifiable: What result would prove this hypothesis wrong? (If you can't answer, it's not falsifiable)
  2. Specific: Does it name the population, IV, DV, and direction?
  3. Testable: Can the variables be measured with available instruments?
  4. Grounded: Is there a theoretical or empirical reason to predict this relationship?
  5. Appropriately scoped: Is it narrow enough to test in one study?

If any answer is "no" or "I'm not sure," revise before proceeding to study design.

Anti-Patterns

1. Research question disguised as hypothesis Bad: "Does social media use affect mental health?" Good: "Adolescents aged 13-17 who use social media for more than 3 hours/day will report significantly higher levels of anxiety (GAD-7 scale) than those who use social media for less than 1 hour/day."

2. Unmeasurable variables Bad: "Students who feel more motivated will learn better." Good: "Students in the gamified learning condition (IV) will score higher on the Unit 4 end-of-module test (DV, 20 items, % correct) than students in the standard condition."

3. No stated direction Bad: "There will be a relationship between exercise and mood." Good: "Adults who engage in 30 minutes of aerobic exercise 5 days per week will report lower depressive symptoms (PHQ-9) than sedentary controls after 8 weeks."

4. Hypothesis without mechanism Bad: Hypothesis states a prediction with no theory behind it. Good: Include the theoretical mechanism (e.g., cognitive load theory predicts..., self-determination theory suggests...) so reviewers can evaluate the rationale.

Quality Checklist

  • Research question is specific (named population, phenomenon, comparison)
  • IV and DV are both operationalized with specific measurement definitions
  • Control variables and potential confounds are listed
  • H₀ and H₁ are both stated explicitly
  • H₁ is directional when prior evidence supports a direction
  • Hypothesis names population, IV, DV, and predicted direction
  • Theoretical basis and causal mechanism are stated
  • Hypothesis is falsifiable (can state what would disprove it)
  • Variables are measurable with available instruments

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Design clean and consistent APIs. Use when the user says "design an API", "API design review", "design these endpoints", "REST API for X", "GraphQL schema", "API contract", "how should this endpoint work", "review my API design", or wants to create or improve an API interface - even if they don't explicitly say "API design".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

qa-aman のスキルをすべて見る

このスキルの問題を報告する