scientific-problem-selection

작성자: anthropic

scientific-problem-selection — AI 에이전트를 위한 설치 가능한 스킬, anthropics/life-sciences에서 게시함.

npx skills add https://github.com/anthropics/life-sciences --skill scientific-problem-selection

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:

  1. What exactly you want to do
  2. How you currently plan to do it
  3. If it works, why will it be a big deal
  4. 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:

  1. The overall goal of your project (if we have not talked about it before)
  2. What exactly went wrong
  3. 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:

  1. The setting (i.e., is this about a current or future project)
  2. 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

SkillPurposeOutputTime
1. Intuition PumpsGenerate high-quality research ideasProblem Ideation Document~1 week
2. Risk AssessmentIdentify and manage project risksRisk Assessment Matrix3-5 days
3. Optimization FunctionDefine success metricsImpact Assessment Document2-3 days
4. Parameter StrategyDecide what to fix vs. keep flexibleParameter Strategy Document2-3 days
5. Decision Tree NavigationPlan decision points and altitude danceDecision Tree Map2 days
6. Adversity ResponsePrepare for crises as opportunitiesAdversity Playbook2 days
7. Problem InversionNavigate around obstaclesProblem Inversion Analysis1 day
8. Integration & SynthesisSynthesize into coherent planProject Communication Package3-5 days
9. Meta-FrameworkOrchestrate complete workflowComplete Project Package1-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

  1. Conversational Entry - Meet users where they are with three clear starting points
  2. Thoughtful Interaction - Ask clarifying questions; low confidence prompts additional input
  3. Literature Integration - Use PubMed searches at strategic points for validation
  4. Concrete Outputs - Every skill produces tangible 1-2 page documents
  5. Building Specificity - Progressive detail emerges through targeted questions
  6. Flexibility - Skills work independently, sequentially, or iteratively
  7. 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:

FileContentSearch Patterns
01-intuition-pumps.mdGenerate research ideasIntuition Pump #, Trap #, Phase [0-9]
02-risk-assessment.mdRisk identificationRisk.*1-5, go/no-go, assumption
03-optimization-function.mdSuccess metricsGenerality.*Learning, optimization, impact
04-parameter-strategy.mdParameter fixationfixed.*float, constraint, parameter
05-decision-tree.mdDecision tree navigationaltitude, Level [0-9], decision
06-adversity-planning.mdAdversity responseadversity, crisis, ensemble
07-problem-inversion.mdProblem inversion strategiesStrategy [0-9], inversion, goal
08-integration-synthesis.mdIntegration and synthesisnarrative, communication, story
09-meta-framework.mdComplete workflowPhase, 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.

anthropic의 다른 스킬

access
anthropic
Discord 채널 접근을 관리합니다 — 페어링 승인, 허용 목록 편집, DM/그룹 정책 설정. 사용자가 페어링 요청, 승인, 허용된 사람 확인 등을 요청할 때 사용합니다.
official
session-report
anthropic
~/.claude/projects 트랜스크립트에서 Claude Code 세션 사용량(토큰, 캐시, 하위 에이전트, 스킬, 고비용 프롬프트)에 대한 탐색 가능한 HTML 보고서를 생성합니다.
official
build-mcp-server
anthropic
이 스킬은 사용자가 "MCP 서버 구축", "MCP 생성", "MCP 통합 만들기", "Claude용 API 래핑", "도구 노출" 등을 요청할 때 사용해야 합니다.
official
cookbook-audit
anthropic
Anthropic Cookbook 노트북을 루브릭에 따라 감사합니다. 노트북 리뷰나 감사가 요청될 때마다 사용하세요.
official
handle-complaint
anthropic
들어오는 고객 불만을 처음부터 끝까지 처리합니다 — 맥락을 파악하고, 응답을 작성하며, 운영상의 수정을 제안합니다. 선택적으로 이메일이나 티켓 ID를 받습니다…
official
use-case-triage
anthropic
처리 활동이 PIA, 필수 GDPR DPIA가 필요한지 또는 진행 가능한지 신속히 판단하여 개인정보 처리방침 충돌을 표시하고 적절한 경로로 안내합니다…
official
board-minutes
anthropic
이사회 또는 위원회 회의록을 사내 형식으로 작성합니다. 캘린더에서 예정된 이사회 및 위원회 회의를 자동으로 감지하고, 안건을 요청한 후…
official
renewal-tracker
anthropic
유지 관리되는 갱신 등록부를 기반으로 취소 마감일이 다가오는 계약을 표시하고 통지 기간이 종료되기 전에 경고합니다. 사용자가 요청할 때 사용합니다.
official