Scientific Problem Selection
AnthropicOfficialPublished by Anthropic
- Skill
- Guidelines
- Science and research
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
Scientific Problem Selection provides a structured, conversational approach to navigating the research lifecycle. Based on the principles of problem choice over execution quality, this skill helps researchers move from initial ideation to strategic planning. It guides users through nine specific modules—including intuition pumps, risk assessment, and decision tree navigation—to ensure that time is invested in high-impact, feasible problems. By treating research as a series of testable assumptions and strategic decision points, the framework helps scientists avoid common pitfalls, manage adversity, and optimize their research strategy.
What it does
- Facilitates project ideation using structured intuition pumps.
- Performs rigorous risk assessment and assumption analysis.
- Defines success metrics through optimization functions.
- Navigates complex decision trees for project troubleshooting.
- Provides strategies for adversity response and problem inversion.
- Synthesizes research plans into coherent communication packages.
When to use it
- When choosing a new thesis, postdoc, or lab research direction.
- When a project is stuck and requires a strategic pivot.
- When evaluating the feasibility and impact of a new research idea.
- When planning long-term research strategy or navigating career transitions.
- When preparing for committee meetings or grant applications.
Advantages
- Increases research impact by prioritizing problem selection over incremental execution.
- Reduces time wasted on dead-end projects through early risk identification.
- Provides a repeatable, evidence-based framework for scientific decision-making.
- Helps transform crises into opportunities for project growth.
- Encourages objective evaluation of biological and technical assumptions.
Usage examples
- “I have an idea for a new project involving CRISPR, but I am not sure if it is worth pursuing.”
- The agent initiates the ideation workflow, asking for a summary and guiding the user through intuition pumps to refine the idea and assess its potential impact.
- “My current experiment is failing and I am stuck. Can you help me troubleshoot?”
- The agent shifts to the troubleshooting workflow, helping the user identify the core problem, analyze assumptions, and navigate the decision tree to find a path forward.
- “I need to evaluate the risks of my proposed research strategy.”
- The agent leads the user through a systematic risk assessment, helping to list assumptions, score them by risk level and time-to-test, and identify potential red flags.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/anthropics/scientific-problem-selection/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip scientific-problem-selection.zip -d .agents/skills
Documentation by Anthropic
Scientific Problem Selection Skills
A conversational framework for systematic scientific problem selection based on Fischbach & Walsh's "Problem choice and decision trees in science and engineering" (Cell, 2024).
Getting Started
Present users with three entry points:
1) Pitch an idea for a new project — to work it up together
2) Share a problem in a current project — to troubleshoot together
3) Ask a strategic question — to navigate the decision tree together
This conversational entry meets scientists where they are and establishes a collaborative tone.
Option 1: Pitch an Idea
Initial Prompt
Ask: "Tell me the short version of your idea (1-2 sentences)."
Response Approach
After the user shares their idea, return a quick summary (no more than one paragraph) demonstrating understanding. Note the general area of research and rephrase the idea in a way that highlights its kernel—showing alignment and readiness to dive into details.
Follow-up Prompt
Then ask for more detail: "Now give me a bit more detail. You might include, however briefly or even say where you are unsure:
What exactly you want to do
How you currently plan to do it
If it works, why will it be a big deal
What you think are the major risks"
Workflow
From there, guide the user through the early stages of problem selection and evaluation:
Skill 1: Intuition Pumps - Refine and strengthen the idea
Skill 2: Risk Assessment - Identify and manage project risks
Skill 3: Optimization Function - Define success metrics
Skill 4: Parameter Strategy - Determine what to fix vs. keep flexible
See references/01-intuition-pumps.md, references/02-risk-assessment.md, references/03-optimization-function.md, and references/04-parameter-strategy.md for detailed guidance.
Option 2: Troubleshoot a Problem
Initial Prompt
Ask: "Tell me a short version of your problem (1-2 sentences or whatever is easy)."
Response Approach
After the user shares their problem, return a quick summary (no more than one paragraph) demonstrating understanding. Note the context of the project where the problem occurred and rephrase the problem—highlighting its core essence—so the user knows the situation is understood. Also raise additional questions that seem important to discuss.
Follow-up Prompt
Then ask: "Now give me a bit more detail. You might include, however briefly:
The overall goal of your project (if we have not talked about it before)
What exactly went wrong
Your current ideas for fixing it"
Workflow
From there, guide the user through troubleshooting and decision tree navigation:
Skill 5: Decision Tree Navigation - Plan decision points and navigate between execution and strategic thinking
Skill 4: Parameter Strategy - Fix one parameter at a time, let others float
Skill 6: Adversity Response - Frame problems as opportunities for growth
Skill 7: Problem Inversion - Strategies for navigating around obstacles
Always include workarounds that might be useful whether or not the problem can be fixed easily.
See references/05-decision-tree.md, references/06-adversity-planning.md, references/07-problem-inversion.md, and references/04-parameter-strategy.md for detailed guidance.
Option 3: Ask a Strategic Question
Initial Prompt
Ask: "Tell me the short version of your question (1-2 sentences)."
Response Approach
After the user shares their question, return a quick summary (no more than one paragraph) demonstrating understanding. Note the broader context and rephrase the question—highlighting its crux—to confirm alignment with their thinking.
Follow-up Prompt
Then ask: "Now give me a bit more detail. You might include, however briefly:
The setting (i.e., is this about a current or future project)
A bit more detail about what you're thinking"
Workflow
From there, draw on the specific modules from the problem choice framework most appropriate to the question:
Skills 1-4 for future project planning (ideation, risk, optimization, parameters)
Skills 5-7 for current project navigation (decision trees, adversity, inversion)
Skill 8 for communication and synthesis
Skill 9 for comprehensive workflow orchestration
See the complete reference materials in the references/ folder.
Core Framework Concepts
The Central Insight
Problem Choice >> Execution Quality
Even brilliant execution of a mediocre problem yields incremental impact. Good execution of an important problem yields substantial impact.
The Time Paradox
Scientists typically spend:
Days choosing a problem
Years solving it
This imbalance limits impact. These skills help invest more time choosing wisely.
Evaluation Axes
For Evaluating Ideas:
X-axis: Likelihood of success
Y-axis: Impact if successful
Skills help move ideas rightward (more feasible) and upward (more impactful).
The Risk Paradox
Don't avoid risk—befriend it
No risk = incremental work
But: Multiple miracles = avoid or refine
Balance: Understood, quantified, manageable risk
The Parameter Paradox
Too many fixed = brittleness
Too few fixed = paralysis
Sweet spot: Fix ONE meaningful constraint
The Adversity Principle
Crises are inevitable (don't be surprised)
Crises are opportune (don't waste them)
Strategy: Fix problem AND upgrade project simultaneously
The 9 Skills Overview
| Skill | Purpose | Output | Time |
|---|---|---|---|
| 1. Intuition Pumps | Generate high-quality research ideas | Problem Ideation Document | ~1 week |
| 2. Risk Assessment | Identify and manage project risks | Risk Assessment Matrix | 3-5 days |
| 3. Optimization Function | Define success metrics | Impact Assessment Document | 2-3 days |
| 4. Parameter Strategy | Decide what to fix vs. keep flexible | Parameter Strategy Document | 2-3 days |
| 5. Decision Tree Navigation | Plan decision points and altitude dance | Decision Tree Map | 2 days |
| 6. Adversity Response | Prepare for crises as opportunities | Adversity Playbook | 2 days |
| 7. Problem Inversion | Navigate around obstacles | Problem Inversion Analysis | 1 day |
| 8. Integration & Synthesis | Synthesize into coherent plan | Project Communication Package | 3-5 days |
| 9. Meta-Framework | Orchestrate complete workflow | Complete Project Package | 1-6 weeks |
Skill Workflow
SKILL 1: Intuition Pumps
| (generates idea)
v
SKILL 2: Risk Assessment
| (evaluates feasibility)
v
SKILL 3: Optimization Function
| (defines success metrics)
v
SKILL 4: Parameter Strategy
| (determines flexibility)
v
SKILL 5: Decision Tree
| (plans execution and evaluation)
v
SKILL 6: Adversity Planning
| (prepares for failure modes)
v
SKILL 7: Problem Inversion
| (provides pivot strategies)
v
SKILL 8: Integration & Communication
| (synthesizes into coherent plan)
v
SKILL 9: Meta-Skill
(orchestrates complete workflow)Key Design Principles
Conversational Entry - Meet users where they are with three clear starting points
Thoughtful Interaction - Ask clarifying questions; low confidence prompts additional input
Literature Integration - Use PubMed searches at strategic points for validation
Concrete Outputs - Every skill produces tangible 1-2 page documents
Building Specificity - Progressive detail emerges through targeted questions
Flexibility - Skills work independently, sequentially, or iteratively
Scientific Rigor - Claims about generality and feasibility should be evidence-based
Who Should Use These Skills
Graduate Students (Primary Audience)
When: Choosing thesis projects, qualifying exams, committee meetings
Focus: Skills 1-3 (ideation, risk, impact) + Skill 9 (complete workflow)
Timeline: 2-4 weeks for comprehensive planning
Postdocs
When: Starting new position, planning independent projects, fellowship applications
Focus: All skills, emphasizing independence and risk management
Timeline: 1-2 weeks intensive planning
Principal Investigators
When: New lab, new direction, mentoring trainees, grant cycles
Focus: Skills 1, 3, 4, 6 (ideation, impact, parameters, adversity)
Timeline: Ongoing, integrate into lab culture
Startup Founders
When: Company inception, pivot decisions, investor pitches
Focus: Skills 1-4 (ideation through parameters) + Skill 8 (communication)
Timeline: 1-2 weeks for initial planning, revisit quarterly
Reference Materials
Detailed skill documentation is available in the references/ folder:
| File | Content | Search Patterns |
|---|---|---|
01-intuition-pumps.md | Generate research ideas | Intuition Pump #, Trap #, Phase [0-9] |
02-risk-assessment.md | Risk identification | Risk.*1-5, go/no-go, assumption |
03-optimization-function.md | Success metrics | Generality.*Learning, optimization, impact |
04-parameter-strategy.md | Parameter fixation | fixed.*float, constraint, parameter |
05-decision-tree.md | Decision tree navigation | altitude, Level [0-9], decision |
06-adversity-planning.md | Adversity response | adversity, crisis, ensemble |
07-problem-inversion.md | Problem inversion strategies | Strategy [0-9], inversion, goal |
08-integration-synthesis.md | Integration and synthesis | narrative, communication, story |
09-meta-framework.md | Complete workflow | Phase, workflow, orchestrat |
Expected Outcomes
Immediate (After Completing Workflow)
Clear project vision
Honest risk assessment
Contingency plans
Communication materials ready
Confidence in problem choice
6-Month
Faster decisions (have framework)
Productive adversity handling
No existential crises (risks mitigated)
2-Year
Published results or strong progress
Avoided dead-end projects
Career aligned with goals
Time well-spent (ultimate measure)
Foundational Reference
Fischbach, M.A., & Walsh, C.T. (2024). "Problem choice and decision trees in science and engineering." Cell, 187, 1828-1833.
Based on course BIOE 395 taught at Stanford University.
Files
- ATTRIBUTION.mdAdded by AutoGineer1004 B
- LICENSE.txt10.0 KiB
- SKILL.md10.9 KiB
- references/01-intuition-pumps.md12.2 KiB
- references/02-risk-assessment.md12.9 KiB
- references/03-optimization-function.md17.7 KiB
- references/04-parameter-strategy.md14.1 KiB
- references/05-decision-tree.md3.2 KiB
- references/06-adversity-planning.md4.6 KiB
- references/07-problem-inversion.md5.5 KiB
- references/08-integration-synthesis.md5.3 KiB
- references/09-meta-framework.md16.2 KiB
references/02-risk-assessment.md
SKILL 2: Risk Assessment and Assumption Analysis
Overview
This skill helps scientists systematically identify, quantify, and manage project risk through rigorous assumption analysis. The goal is not to eliminate risk—risk-free projects tend to be incremental—but to name it, quantify it, and work steadily to chip away at it. This skill builds directly on the Problem Ideation Document from Skill 1.
Core Principle
"Don't avoid risk; befriend it."
The most important concept in problem choice is the two-axis evaluation:
X-axis: Likelihood of success
Y-axis: Impact if successful
This skill focuses on the X-axis, helping users move their project rightward through systematic risk analysis.
Why This Matters
A project with a high-risk assumption that won't read out for >2 years is problematic. One that requires multiple miracles to succeed should be avoided or refined. The human tendency is to stay in a safe local space, work laterally, and put off facing existential risks—like an ostrich burying its head in the sand. This skill helps users face risk head-on.
The Skill Workflow
Phase 1: Extract Project Assumptions (10-15 minutes)
First, Claude should gather information about the user's project from Skill 1:
Project Summary (from Skill 1):
The biological question
The technical approach
What's novel about it
Project Horizon:
How long is this project expected to take? (months/years)
What is the user's role? (graduate student, postdoc, PI, startup founder)
Initial Risk Sense:
What keeps the user up at night about this project?
What's the scariest assumption?
Phase 2: Comprehensive Assumption Listing
Claude should work with the user to list EVERY assumption the project makes from inception through conclusion. Assumptions fall into two categories:
Type A: Assumptions About Biological Reality
These are facts about the world that either are or aren't true. They won't change during the project.
Examples:
New cell types exist beyond what's currently known
A particular gene regulates the process being studied
Two proteins physically interact
A pathway functions in the organism of interest
The biological effect size is detectable
Type B: Assumptions About Technical Capability
These are about whether technology can do what's needed. These CAN change during the project as methods improve.
Examples:
A specific cell type can be isolated
Sequencing will generate high-quality data
An assay has sufficient throughput
Computational analysis can distinguish signal from noise
Gene editing will work in the system
Claude should ask:
What must be true about the biology for this to work?
What must the technology be able to do?
What about the experimental design—what assumptions are built in?
What about the analysis—can it deliver what's needed?
If everything works, can the findings be validated?
Will the findings be interpretable and meaningful?
Phase 3: Risk Scoring (The Assumption Analysis Table)
For each assumption, Claude should help the user assign two scores:
Risk Level (1-5 scale):
1 = Very likely to be true/work (>90% confidence)
2 = Likely (70-90% confidence)
3 = Uncertain (40-70% confidence)
4 = Unlikely (10-40% confidence)
5 = Very unlikely (<10% confidence)
Time to Test (months):
How long before the user will know if this assumption is valid?
Critical Rules:
Be brutally honest—try to convince oneself of being WRONG, not right
Distinguish between biological vs. technical assumptions
Consider whether technical assumptions might improve over time
Note which assumptions depend on earlier assumptions succeeding
Phase 4: Risk Profile Evaluation
Once the complete table is ready, Claude should analyze the risk profile:
Red Flags to Identify:
The Late High-Risk Problem: Risk level 4-5 assumption that won't read out until >18 months
The Multiple Miracles: More than 2-3 assumptions with risk level 4-5
The Dependency Chain: High-risk assumptions stacked in sequence
The Ostrich Pattern: Starting with low-risk work while avoiding the high-risk tests
Green Lights:
Early Go/No-Go: Highest-risk assumption testable in <6 months
Multiple Candidates: Project can succeed with several different outcomes
Graceful Degradation: If assumption X fails, assumption Y provides alternative path
Risk Distribution: High-risk assumptions balanced across timeline
Rule of Thumb: If you have a risk level 5 assumption three years out, pick another project.
Phase 5: Risk Mitigation Strategies
For each high-risk assumption (level 4-5), Claude should help develop mitigation strategies:
Strategy 1: Move High-Risk Tests Earlier
Question: Can a quicker, cruder test be designed that answers most of what's needed?
Example: Instead of waiting 2 years to validate a new cell type exists, consider:
Using existing markers as a proxy
Testing in a simpler model system first
Using computational predictions to increase confidence
Strategy 2: Multiple Candidates Approach
Question: Can multiple candidates be tested in parallel to increase likelihood of success?
Example: Instead of:
Testing one kinase → Test a panel of 10 kinases
Building one engineered organism → Build and test a library
Pursuing one therapeutic target → Pursue 3 related targets
Strategy 3: Reframe the Question
Question: Can the project scope be adjusted to reduce critical assumptions while maintaining impact?
Example from lecture:
Original: Identify NEW enteroendocrine cell types (high risk: they may not exist)
Reframed: Better characterize KNOWN but incompletely understood cell types (lower risk)
Strategy 4: Change the System
Question: Is there a different biological system with similar scientific value but lower technical risk?
Example from lecture:
Original: Intestinal epithelium (hard to manipulate genetically)
Alternative: Liver (easier genetic manipulation options exist)
Strategy 5: Add Complementary Approaches
Question: Can a parallel approach be added that de-risks the main assumption?
Example from lecture:
Add spatial transcriptomics to scRNA-seq
This provides biogeographic context and validates cell type existence earlier
Phase 6: Go/No-Go Experiment Design
For the top 3 highest-risk assumptions, Claude should help design the critical go/no-go experiments:
For each, specify:
The Question: Exactly what is being tested?
The Experiment: Most direct test possible (even if crude)
Success Criteria: What result means "go"?
Failure Response: What result means "pivot" or "stop"?
Timeline: How soon can this be run?
Resources: What is needed?
Key Principle: Cut right to the critical go/no-go experiment. Don't just start with easy stuff—the risk points aren't going away.
Phase 7: Literature Validation
Claude should search PubMed to help calibrate risk assessments:
Search for:
Precedents: Has anyone done something similar? (Reduces technical risk)
Biological Evidence: What's known about the system? (Informs biological risk)
Technical Benchmarks: How well do the methods work in practice?
Adjacent Successes: Has anyone solved related problems?
Questions to ask the user:
What specific searches would help calibrate risk?
Are there particular papers that informed the assumptions?
Are there technical benchmarks to look up?
Phase 8: Revised Project Plan
Based on the risk analysis, Claude should help create a revised plan:
Option A: De-Risk the Current Plan
Reorder experiments to test high-risk assumptions early
Add complementary approaches
Design multiple-candidate strategies
Option B: Reframe the Project
Adjust scope while maintaining impact
Change biological system
Modify technical approach
Option C: Pick a Different Project
Sometimes the honest answer is: "This has too many miracles." That's valuable to know BEFORE investing years.
Output Deliverable
Claude should produce a 2-page Risk Assessment Document:
Page 1: Assumption Analysis Table
| Assumption | Type* | Risk† | Time‡ | Notes |
|---|---|---|---|---|
| [Assumption 1] | Bio/Tech | 1-5 | X mo | [Rationale for score] |
| [Assumption 2] | Bio/Tech | 1-5 | X mo | [Rationale for score] |
| ... | ... | ... | ... | ... |
*Bio = Biological reality, Tech = Technical capability
†Risk: 1=very likely to 5=very unlikely
‡Time to test in months
Risk Profile Summary:
Total Assumptions: X
High Risk (4-5): X assumptions
Late High Risk (>18mo): X assumptions
Critical Path: [Identify the chain of dependent assumptions]
Overall Assessment: [Green/Yellow/Red light with explanation]
Page 2: Risk Mitigation Plan
Top 3 High-Risk Assumptions:
For each:
The Assumption: [Stated clearly]
Current Risk Level & Timeline: X (risk) at Y months
Why This Risk Exists: [Explanation]
Mitigation Strategy: [From Strategies 1-5 above]
Go/No-Go Experiment:
Experiment design
Success criteria
Timeline
What you'll do if it fails
Revised Project Timeline:
Month 0-6: [Early go/no-go experiments]
Month 6-12: [Based on go/no-go results]
Month 12-18: [...]
Month 18+: [...]Contingency Plans:
If assumption X fails: [Plan B]
If assumption Y fails: [Plan C]
Multiple success paths: [How project can succeed different ways]
Decision Points:
Month X: Evaluate [assumptions A, B] → Go/Pivot/Stop decision
Month Y: Evaluate [assumptions C, D] → Go/Pivot/Stop decision
Practical Examples
Example 1: ScRNA-Seq for Enteroendocrine Cells
High-Risk Assumptions Identified:
"New cell types can be validated experimentally" (Risk 5, 24 months)
"Knockout will yield biologically relevant phenotype" (Risk 5, 30 months)
Problem: Two risk-5 assumptions at 24+ months = RED FLAG
Mitigation Applied:
Reframe to study known but poorly characterized cells (reduces Risk 5→3)
Switch to liver instead of intestine (improves validation timeline: 30→18 months)
Add spatial transcriptomics (provides earlier validation checkpoint at 16 months)
Example 2: Bacterial Therapy for Chronic Kidney Disease
High-Risk Assumption Identified: "Key uremic toxins leading to effects can be determined" (Risk 4, unknown timeline)
Problem: Critical assumption with unclear path to resolution
Mitigation Applied:
Focus on known lead toxins (IS and PCS) rather than discovering new ones
Add parallel track: test multiple toxin candidates
Design study where learning toxin identity IS the outcome (multiple success paths)
Key Principles to Remember
Try to Convince Yourself You're Wrong: The goal is critical evaluation, not confirmation bias.
Ignore Everything But Key Risk Points: Don't get distracted by easy tasks. The high-risk assumptions aren't going away.
Early and Often: Design go/no-go experiments at the earliest feasible moment.
Be Candid About Risk: When presenting ideas, acknowledging risk makes your case MORE convincing, not less.
No Risk, No Interest: The goal isn't zero risk—it's understood, quantified, manageable risk.
Risk Can Change: Technical assumptions may improve as methods advance. Build this into your planning.
Compare Risk Profiles: Evaluate multiple projects in parallel to compare risk profiles and make better choices.
Watch for the Ostrich Pattern: Are you avoiding the scary experiment? That's human nature, but a critical failure mode.
Warning Signs
Warning signs include:
Risk level 5 assumptions >2 years out
More than 3 assumptions at risk level 4-5
Highest-risk assumptions at the END of the timeline
Rationalizing why high-risk assumptions will "probably work out"
Planning to "start with the easy stuff" while avoiding risk tests
Inability to articulate clear go/no-go criteria
Good shape indicators:
Highest-risk tests happen in first 6 months
Multiple paths to success exist
Clear plans for what to do if key assumptions fail
Risk is distributed across the timeline
Testing assumptions, not confirming hopes
Getting Started
Claude should begin with Phase 1 by asking for:
The project summary from Skill 1
Project timeline expectations
What concerns the user most about this project
Together, Claude and the user will build a rigorous risk assessment that dramatically improves the likelihood of success by helping avoid years of work on projects with insurmountable obstacles.
Remember: Spending time on risk analysis is the most valuable investment a scientist can make. A well-understood risk profile enables moving forward with confidence or pivoting with clarity—both are valuable outcomes.
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Anthropic
- Publisher
- Anthropic (Official)
- Source
- anthropics/knowledge-work-plugins · bio-research/skills/scientific-problem-selection · commit e050c2e
- Licence
- Apache License 2.0 (redistribution allowed)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- anthropics/life-sciences
AutoGineer is not affiliated with or endorsed by Anthropic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download scientific-problem-selection.zip