Agent skill

Propose Hypotheses

by NeoLabHQ in NeoLabHQ/context-engineering-kit

Execute complete FPF cycle from hypothesis generation to decision

GPL-3.0Auto-check passedResearch & Science

Install Propose Hypotheses

skills CLI

$ npx skills add NeoLabHQ/context-engineering-kit --skill propose-hypotheses -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install NeoLabHQ/context-engineering-kit propose-hypotheses --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/NeoLabHQ/context-engineering-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/propose-hypotheses .claude/skills/propose-hypotheses && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "propose-hypotheses" agent skill from https://github.com/NeoLabHQ/context-engineering-kit/tree/master/skills/propose-hypotheses into .claude/skills/propose-hypotheses/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "propose-hypotheses", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/NeoLabHQ/context-engineering-kit/tree/master/skills/propose-hypotheses

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add NeoLabHQ/context-engineering-kit --skill propose-hypotheses -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install NeoLabHQ/context-engineering-kit propose-hypotheses --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NeoLabHQ/context-engineering-kit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/propose-hypotheses .agents/skills/propose-hypotheses && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "propose-hypotheses" agent skill from https://github.com/NeoLabHQ/context-engineering-kit/tree/master/skills/propose-hypotheses into .agents/skills/propose-hypotheses/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "propose-hypotheses", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add NeoLabHQ/context-engineering-kit --skill propose-hypotheses -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install NeoLabHQ/context-engineering-kit propose-hypotheses --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NeoLabHQ/context-engineering-kit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/propose-hypotheses .cursor/skills/propose-hypotheses && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "propose-hypotheses" agent skill from https://github.com/NeoLabHQ/context-engineering-kit/tree/master/skills/propose-hypotheses into .cursor/skills/propose-hypotheses/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "propose-hypotheses", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/NeoLabHQ/context-engineering-kit.git --path skills/propose-hypotheses

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add NeoLabHQ/context-engineering-kit --skill propose-hypotheses -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install NeoLabHQ/context-engineering-kit propose-hypotheses --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NeoLabHQ/context-engineering-kit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/propose-hypotheses .gemini/skills/propose-hypotheses && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "propose-hypotheses" agent skill from https://github.com/NeoLabHQ/context-engineering-kit/tree/master/skills/propose-hypotheses into .gemini/skills/propose-hypotheses/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "propose-hypotheses", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install NeoLabHQ/context-engineering-kit propose-hypotheses

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add NeoLabHQ/context-engineering-kit --skill propose-hypotheses -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/NeoLabHQ/context-engineering-kit.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/propose-hypotheses .github/skills/propose-hypotheses && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "propose-hypotheses" agent skill from https://github.com/NeoLabHQ/context-engineering-kit/tree/master/skills/propose-hypotheses into .github/skills/propose-hypotheses/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "propose-hypotheses", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add NeoLabHQ/context-engineering-kit --skill propose-hypotheses -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install NeoLabHQ/context-engineering-kit propose-hypotheses --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NeoLabHQ/context-engineering-kit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/propose-hypotheses .opencode/skills/propose-hypotheses && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "propose-hypotheses" agent skill from https://github.com/NeoLabHQ/context-engineering-kit/tree/master/skills/propose-hypotheses into .opencode/skills/propose-hypotheses/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "propose-hypotheses", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: propose-hypotheses
GitHub stars: 1.7k
Token cost: ~1.5k tokens
SKILL.md length: 420 words
Files: 1
Skills in repo: 57
Repo updated: Aug 26, 2026
First seen: Oct 8, 2026
Licence: GPL-3.0

At a glance

Execute complete FPF cycle from hypothesis generation to decision

Works in 8 steps: Generate Hypotheses (FPF Agent) → Present Summary (Main Agent) → Add User Hypothesis (FPF Agent,… → …
Tasks that involve Hypothesis generation
SKILL.md covers User Input, Workflow Execution and Completion
Calls kind

What it does

Propose Hypotheses is an agent skill from NeoLabHQ/context-engineering-kit. Execute complete FPF cycle from hypothesis generation to decision

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science, covering Hypothesis generation. The repository describes itself as: Hand-crafted Claude Code Skills focused on improving agent results quality. Compatible with OpenCode, Cursor, Antigravity, Gemini CLI, and others. Includes CodeRabbit open-source… The licence is GPL-3.0.

When your agent uses it

Tasks that involve Hypothesis generation

Example prompts

“/propose-hypotheses”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Generate Hypotheses (FPF Agent)
Present Summary (Main Agent)
Add User Hypothesis (FPF Agent, Conditional Loop)
Verify Logic (Parallel Sub-Agents)
Validate Evidence (Parallel Sub-Agents)
Audit Trust (Parallel Sub-Agents)
Make Decision (FPF Agent)
Present Final Summary (Main Agent)

What it can do on your machine

Read from SKILL.md and the folder at commit 23e2428. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- kind
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Propose Hypotheses loads about 1.5k tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 420 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~21
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NeoLabHQ/context-engineering-kit at commit 23e2428, republished under its GPL-3.0 licence (© NeoLabHQ). 420 words, ~1,487 tokens.

Download SKILL.mdSave it as .claude/skills/propose-hypotheses/SKILL.md (or your agent's skills folder).

name: propose-hypotheses
description: Execute complete FPF cycle from hypothesis generation to decision

Propose Hypotheses Workflow

Execute the First Principles Framework (FPF) cycle: generate competing hypotheses, verify logic, validate evidence, audit trust, and produce a decision.

User Input

text

Problem Statement: $ARGUMENTS

Workflow Execution

Step 1a: Create Directory Structure (Main Agent)

Create .fpf/ directory structure if it does not exist:

bash

mkdir -p .fpf/{evidence,decisions,sessions,knowledge/{L0,L1,L2,invalid}}
touch .fpf/{evidence,decisions,sessions,knowledge/{L0,L1,L2,invalid}}/.gitkeep

Postcondition: .fpf/ directory scaffold exists.

Step 1b: Initialize Context (FPF Agent)

Launch fpf-agent with sonnet[1m] model:

Description: "Initialize FPF context"

Prompt:

Read ${CLAUDE_PLUGIN_ROOT}/tasks/init-context.md and execute.

Problem Statement: $ARGUMENTS

**Write**: Context summary to `.fpf/context.md`**

Step 2: Generate Hypotheses (FPF Agent)

Launch fpf-agent with sonnet[1m] model:

Description: "Generate L0 hypotheses"

Prompt:

Read ${CLAUDE_PLUGIN_ROOT}/tasks/generate-hypotheses.md and execute.

Problem Statement: $ARGUMENTS
Context: <summary from Step 1b>

**Write**: List of hypothesis IDs and titles to `.fpf/knowledge/L0/`

Reply with summary table in markdown format:

  | ID | Title | Kind | Scope |
  |----|-------|------|-------|
  | ... | ... | ... | ... |

Step 3: Present Summary (Main Agent)

Read all L0 hypothesis files from .fpf/knowledge/L0/
Present summary table from agent response.
Ask user: "Would you like to add any hypotheses of your own? (yes/no)"

Step 4: Add User Hypothesis (FPF Agent, Conditional Loop)

Condition: User says yes to adding hypotheses.

Launch fpf-agent with sonnet[1m] model:

Description: "Add user hypothesis"

Prompt:

Read ${CLAUDE_PLUGIN_ROOT}/tasks/add-user-hypothesis.md and execute.

User Hypothesis Description: <get from user>

**Write**: User hypothesis to `.fpf/knowledge/L0/`

Loop: Return to Step 3 after hypothesis is added.

Exit: When user says no or declines to add more.

Step 5: Verify Logic (Parallel Sub-Agents)

Condition: User finished adding hypotheses.

For EACH L0 hypothesis file in .fpf/knowledge/L0/, launch parallel fpf-agent with sonnet[1m] model:

Description: "Verify hypothesis: <hypothesis-id>"

Prompt:

Read ${CLAUDE_PLUGIN_ROOT}/tasks/verify-logic.md and execute.

Hypothesis ID: <hypothesis-id>
Hypothesis File: .fpf/knowledge/L0/<hypothesis-id>.md

**Move**: After you complete verification, move the file to `.fpf/knowledge/L1/` or `.fpf/knowledge/invalid/`.

Wait for all agents, then check that files are moved to .fpf/knowledge/L1/ or .fpf/knowledge/invalid/.

Step 6: Validate Evidence (Parallel Sub-Agents)

For EACH L1 hypothesis file in .fpf/knowledge/L1/, launch parallel fpf-agent with sonnet[1m] model:

Description: "Validate hypothesis: <hypothesis-id>"

Prompt:

Read ${CLAUDE_PLUGIN_ROOT}/tasks/validate-evidence.md and execute.

Hypothesis ID: <hypothesis-id>
Hypothesis File: .fpf/knowledge/L1/<hypothesis-id>.md

**Move**: After you complete validation, move the file to `.fpf/knowledge/L2/` or `.fpf/knowledge/invalid/`.

Wait for all agents, then check that files are moved to .fpf/knowledge/L2/ or .fpf/knowledge/invalid/.

Show full SKILL.md (240 more words)Show less

Step 7: Audit Trust (Parallel Sub-Agents)

For EACH L2 hypothesis file in .fpf/knowledge/L2/, launch parallel fpf-agent with sonnet[1m] model:

Description: "Audit trust: <hypothesis-id>"

Prompt:

Read ${CLAUDE_PLUGIN_ROOT}/tasks/audit-trust.md and execute.

Hypothesis ID: <hypothesis-id>
Hypothesis File: .fpf/knowledge/L2/<hypothesis-id>.md

**Write**: Audit report to `.fpf/evidence/audit-{hypothesis-id}-{YYYY-MM-DD}.md`

**Reply**: with R_eff score and weakest link

Wait for all agents, then check that audit reports are created in .fpf/evidence/.

Step 8: Make Decision (FPF Agent)

Launch fpf-agent with sonnet[1m] model:

Description: "Create decision record"

Prompt:

Read ${CLAUDE_PLUGIN_ROOT}/tasks/decide.md and execute.

Problem Statement: $ARGUMENTS
L2 Hypotheses Directory: .fpf/knowledge/L2/
Audit Reports: .fpf/evidence/

**Write**: Decision record to `.fpf/decisions/`

**Reply**: with decision record summary in markdown format:

| Hypothesis | R_eff | Weakest Link | Status |
|------------|-------|--------------|--------|
| ... | ... | ... | ... |

**Recommended Decision**: <hypothesis title>

**Rationale**: <brief explanation>

Wait for agent, then check that decision record is created in `.fpf/decisions/`.

Step 9: Present Final Summary (Main Agent)

Read the DRR from .fpf/decisions/
Present results from agent response.
Present next steps:
- Implement the selected hypothesis
- Use /fpf:status to check FPF state
- Use /fpf:actualize if codebase changes
Ask user if he agree with the decision, if not launch fpf-agent at step 8 with instruction to modify the decision as user wants.

Completion

Workflow complete when:

.fpf/ directory structure exists
Context recorded in .fpf/context.md
Hypotheses generated, verified, validated, and audited
DRR created in .fpf/decisions/
Final summary presented to user

Artifacts Created:

.fpf/context.md - Problem context
.fpf/knowledge/L0/*.md - Initial hypotheses
.fpf/knowledge/L1/*.md - Verified hypotheses
.fpf/knowledge/L2/*.md - Validated hypotheses
.fpf/knowledge/invalid/*.md - Rejected hypotheses
.fpf/evidence/*.md - Evidence files
.fpf/decisions/*.md - Design Rationale Record

Files

Just SKILL.md in skills/propose-hypotheses of NeoLabHQ/context-engineering-kit.

Open the folder on GitHubat commit 23e2428

Compare with similar skills

Propose Hypotheses next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Propose Hypotheses compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Propose Hypotheses this skillNeoLabHQ/context-engineering-kit	1.7k	—	~1.5k	Automated safety check: Pass	GPL-3.0	1 mo ago
Hypothesis Generationspacering-net/codeg	3.9k	14 repos	~3.6k	Automated safety check: Notes	MIT	today
Nature Paper CardYuan1z0825/nature-skills	47k	2 repos	~2.1k	Automated safety check: Pass	Apache-2.0	yesterday
Hypothesis GenerationK-Dense-AI/claude-scientific-writer	2.4k	2 repos	~3.9k	Automated safety check: Pass	MIT	yesterday
Good QuestionRimagination/good-question	305	1 repos	~4.3k	Automated safety check: Pass	MIT	17 days ago
High Stakes Analytics Decision Lablimingrui679-design/high-stakes-analytics-decision-lab	1k	—	~2.2k	Automated safety check: Pass	MIT	4 days ago

Similar skills

Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
3.9k GitHub starsUsed in 14 repos~3.6k tokens
Research & ScienceAuto-check: notes
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
47k GitHub starsUsed in 2 repos~2.1k tokens
Research & ScienceAuto-check passed
Hypothesis Generation
K-Dense-AI/claude-scientific-writer
Formulate evidence-bounded scientific questions, candidate hypotheses, rival explanations, causal or associational claims, discriminating predictions, measurements, and preregistration-ready…
2.4k GitHub starsUsed in 2 repos~3.9k tokens
Research & ScienceAuto-check passed
Good Question
Rimagination/good-question
A skill your agent uses when a researcher is choosing, framing, refining, or stress-testing a research question, hypothesis, thesis topic, project idea, grant direction, paper angle, or stalled…
305 GitHub starsUsed in 1 repo~4.3k tokens
Research & ScienceAuto-check passed
High Stakes Analytics Decision Lab
limingrui679-design/high-stakes-analytics-decision-lab
Build or review source-backed descriptive, diagnostic, predictive, and prescriptive analysis for consequential decisions.
1k GitHub stars~2.2k tokensUpdated 4 days ago
Research & ScienceAuto-check passed
Claim-Driven Experiment Planner
zjYao36/Auto-Research-Refine
Turns a refined research proposal into a claim-to-evidence-to-run-order roadmap instead of a sprawling benchmark wishlist.
128 GitHub starsUsed in 6 repos~2.3k tokens
Research & ScienceAuto-check: notes

More from NeoLabHQ/context-engineering-kit

All 57 skills in this repo

Git Notes
NeoLabHQ/context-engineering-kit
A skill your agent uses when adding metadata to commits without changing history, tracking review status, test results, code quality annotations, or supplementing commit messages post-hoc - provides…
1.7k GitHub stars~2.4k tokensUpdated 1 mo ago
Auto-check passed
Load PR Comments
NeoLabHQ/context-engineering-kit
A skill your agent uses to load open/unresolved PR review comments then aggregate them as tasks in .specs/comments/.md for parallel agents to fix.
1.7k GitHub stars~2.1k tokensUpdated 1 mo ago
Auto-check passed
Prompt Engineering
NeoLabHQ/context-engineering-kit
A skill your agent uses when you writing commands, hooks, skills for Agent, or prompts for sub agents or any other LLM interaction, including optimizing prompts, improving LLM outputs, or designing…
1.7k GitHub stars~4.2k tokensUpdated 1 mo ago
Auto-check passed
Multi Agent Patterns
NeoLabHQ/context-engineering-kit
Design multi-agent architectures for complex tasks. An agent skill from NeoLabHQ/context-engineering-kit.
1.7k GitHub starsUsed in 6 repos~6k tokens
Auto-check passed
Review PR
NeoLabHQ/context-engineering-kit
Review an existing GitHub pull request and post inline review comments on its diff.
1.7k GitHub stars~3.8k tokensUpdated 1 mo ago
Auto-check passed
Subagent Driven Development
NeoLabHQ/context-engineering-kit
A skill your agent uses when executing implementation plans with independent tasks in the current session or facing 3+ independent issues that can be investigated without shared state or…
1.7k GitHub stars~2.8k tokensUpdated 1 mo ago
Auto-check passed

Questions about Propose Hypotheses

What does Propose Hypotheses do?

Execute complete FPF cycle from hypothesis generation to decision. Propose Hypotheses is an agent skill from NeoLabHQ/context-engineering-kit.

When should I use Propose Hypotheses?

Propose Hypotheses fits situations like: tasks that involve Hypothesis generation.

How do I install Propose Hypotheses in Claude Code?

Run `npx skills add NeoLabHQ/context-engineering-kit --skill propose-hypotheses -a claude-code`. Or copy the skill folder (skills/propose-hypotheses in NeoLabHQ/context-engineering-kit) into .claude/skills/propose-hypotheses in your project. Claude Code loads it when a task matches its description.

How do I install Propose Hypotheses in Codex?

Run `npx skills add NeoLabHQ/context-engineering-kit --skill propose-hypotheses -a codex`. Or copy the skill folder (skills/propose-hypotheses in NeoLabHQ/context-engineering-kit) into .agents/skills/propose-hypotheses in your project. Codex loads it when a task matches its description.

Can I use Propose Hypotheses in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NeoLabHQ/context-engineering-kit --skill propose-hypotheses -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/propose-hypotheses, .gemini/skills/propose-hypotheses, .github/skills/propose-hypotheses and .opencode/skills/propose-hypotheses in your project.

What does Propose Hypotheses need to run?

Going by SKILL.md and its folder, Propose Hypotheses needs the command-line tools its instructions call (kind).

Does Propose Hypotheses access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Propose Hypotheses safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Propose Hypotheses use?

Propose Hypotheses is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Propose Hypotheses use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Propose Hypotheses?

Skills that share tags, products or a category with Propose Hypotheses: Hypothesis Generation (spacering-net/codeg, 3.9k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars), Hypothesis Generation (K-Dense-AI/claude-scientific-writer, 2.4k stars) and Good Question (Rimagination/good-question, 305 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Propose Hypotheses?

NeoLabHQ (a GitHub organization) maintains it in NeoLabHQ/context-engineering-kit, which has 1,749 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on August 26, 2026.

Source: NeoLabHQ/context-engineering-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Propose Hypotheses

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Propose Hypotheses Workflow

User Input

Workflow Execution

Step 1a: Create Directory Structure (Main Agent)

Step 1b: Initialize Context (FPF Agent)

Step 2: Generate Hypotheses (FPF Agent)

Step 3: Present Summary (Main Agent)

Step 4: Add User Hypothesis (FPF Agent, Conditional Loop)

Step 5: Verify Logic (Parallel Sub-Agents)

Step 6: Validate Evidence (Parallel Sub-Agents)

Step 7: Audit Trust (Parallel Sub-Agents)

Step 8: Make Decision (FPF Agent)

Wait for agent, then check that decision record is created in .fpf/decisions/.

Step 9: Present Final Summary (Main Agent)

Completion

Files

Compare with similar skills

Similar skills

More from NeoLabHQ/context-engineering-kit

Related

Questions about Propose Hypotheses

Wait for agent, then check that decision record is created in `.fpf/decisions/`.