Skip to content
cccskills
FreePublished on GitHub

scientific-problem-selection

Choose research problems, refine new ideas, or rethink stalled projects through structured conversation. Assess feasibility, potential impact, and risks, then develop success criteria, decision points, and backup plans for a clearer research strategy.

OriginalShow the original description

This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".

See how to install

Good for

  • Choosing a thesis research topic
  • Assessing risks in a new research idea
  • Finding alternatives for a stalled project
  • Preparing a research plan for discussion

Files included (11)

  • SKILL.md10.9 KB
  • LICENSE.txt10.0 KB
  • references/01-intuition-pumps.md12.2 KB
  • references/02-risk-assessment.md12.9 KB
  • references/03-optimization-function.md17.7 KB
  • references/04-parameter-strategy.md14.1 KB
  • references/05-decision-tree.md3.2 KB
  • references/06-adversity-planning.md4.6 KB
  • references/07-problem-inversion.md5.5 KB
  • references/08-integration-synthesis.md5.3 KB
  • references/09-meta-framework.md16.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Review a design or web page against WCAG 2.1 AA, an accessibility standard. Organize findings on contrast, keyboard access, forms, and screen reader behavior, with severity levels and practical recommendations for fixes.

  • Review accessibility before design handoff
  • Check text and interface color contrast
  • Review keyboard navigation and focus behavior
anthropics/knowledge-work-plugins30.5KUpdated Oct 19, 2026

account-context

FreeSummary

Build a single brief on an existing customer using available sales records, emails, documents, call notes, and internal chat. Understand the current situation, key contacts, recent discussions, and gaps that may need attention.

  • Preparing for a meeting with an existing customer
  • Catching up on an account during a handover
  • Reviewing recent discussions and stalled opportunities
anthropics/knowledge-work-plugins30.5KUpdated Oct 19, 2026

account-plan

FreeSummary

Build or refresh a strategic customer account plan from sales records, emails, and meeting transcripts. Organize goals, stakeholders, growth opportunities, risks, and dated actions into a document, then sync approved highlights to the customer relationship management system.

  • Creating a quarterly plan for a key customer
  • Refreshing an existing account plan
  • Reviewing stakeholder coverage and growth opportunities
anthropics/knowledge-work-plugins30.5KUpdated Oct 19, 2026

account-research

FreeSummary

Research sales accounts using Common Room data to summarize company details, buying signals, ownership, and key contacts. Answer specific questions directly or prepare a broader briefing with evidence-based next steps, clearly identifying missing information.

  • Prepare a company briefing before a sales conversation
  • Check buying signals and recent account activity
  • Find account owners and key contacts
anthropics/knowledge-work-plugins30.5KUpdated Oct 19, 2026

account-research

FreeSummary

Research prospective companies and contacts, check existing customer records, and assess fit against your ideal customer profile. Receive a sourced brief covering recent developments, likely priorities, outreach talking points, and a suggested next step.

  • Researching a company before a sales approach
  • Checking existing account records and ownership
  • Assessing fit against your ideal customer profile
anthropics/knowledge-work-plugins30.5KUpdated Oct 19, 2026

account-tiering

FreeSummary

Score and group accounts by customer fit and engagement, such as recent contact and open sales opportunities. Identify where to focus sales effort, choose next actions, and spot promising accounts with neglected outreach or missing information.

  • Prioritize a portfolio of assigned accounts
  • Find strong-fit accounts that need outreach
  • Identify promising accounts with no recent activity
anthropics/knowledge-work-plugins30.5KUpdated Oct 19, 2026

See all skills by anthropics

Report a problem with this skill