scientific-problem-selection

Name: scientific-problem-selection
Author: anthropics

1.7kinstalls2.7kforks

How to install scientific-problem-selection?

anthropics/knowledge-work-plugins/scientific-problem-selection

$npx -y skills add anthropics/knowledge-work-plugins --skill scientific-problem-selection

Installs into the current project.

Summary

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 r

Files · 1

View on GitHub

SKILL.md

1	# Scientific Problem Selection Skills
2
3	A conversational framework for systematic scientific problem selection based on Fischbach & Walsh's "Problem choice and decision trees in science and engineering" (Cell, 2024).
4
5	## Getting Started
6
7	Present users with three entry points:
8
9	1) Pitch an idea for a new project — to work it up together
10
11	2) Share a problem in a current project — to troubleshoot together
12
13	3) Ask a strategic question — to navigate the decision tree together
14
15	This conversational entry meets scientists where they are and establishes a collaborative tone.
16
17	---
18
19	## Option 1: Pitch an Idea
20
21	### Initial Prompt
22	Ask: "Tell me the short version of your idea (1-2 sentences)."
23
24	### Response Approach
25	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.
26
27	### Follow-up Prompt
28	Then ask for more detail: "Now give me a bit more detail. You might include, however briefly or even say where you are unsure:
29	1. What exactly you want to do
30	2. How you currently plan to do it
31	3. If it works, why will it be a big deal
32	4. What you think are the major risks"
33
34	### Workflow
35	From there, guide the user through the early stages of problem selection and evaluation:
36	- Skill 1: Intuition Pumps - Refine and strengthen the idea
37	- Skill 2: Risk Assessment - Identify and manage project risks
38	- Skill 3: Optimization Function - Define success metrics
39	- Skill 4: Parameter Strategy - Determine what to fix vs. keep flexible
40
41	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.
42
43	---
44
45	## Option 2: Troubleshoot a Problem
46
47	### Initial Prompt
48	Ask: "Tell me a short version of your problem (1-2 sentences or whatever is easy)."
49
50	### Response Approach
51	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.
52
53	### Follow-up Prompt
54	Then ask: "Now give me a bit more detail. You might include, however briefly:
55	1. The overall goal of your project (if we have not talked about it before)
56	2. What exactly went wrong
57	3. Your current ideas for fixing it"
58
59	### Workflow
60	From there, guide the user through troubleshooting and decision tree navigation:
61	- Skill 5: Decision Tree Navigation - Plan decision points and navigate between execution and strategic thinking
62	- Skill 4: Parameter Strategy - Fix one parameter at a time, let others float
63	- Skill 6: Adversity Response - Frame problems as opportunities for growth
64	- Skill 7: Problem Inversion - Strategies for navigating around obstacles
65
66	Always include workarounds that might be useful whether or not the problem can be fixed easily.
67
68	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.
69
70	---
71
72	## Option 3: Ask a Strategic Question
73
74	### Initial Prompt
75	Ask: "Tell me the short version of your question (1-2 sentences)."
76
77	### Response Approach
78	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.
79
80	### Follow-up Prompt
81	Then ask: "Now give me a bit more detail. You might include, however briefly:
82	1. The setting (i.e., is this about a current or future project)
83	2. A bit more detail about what you're thinking"
84
85	### Workflow
86	From there, draw on the specific modules from the problem choice framework most appropriate to the question:
87	- Skills 1-4 for future project planning (ideation, risk, optimization, parameters)
88	- Skills 5-7 for current project navigation (decision trees, adversity, inversion)
89	- Skill 8 for communication and synthesis
90	- Skill 9 for comprehensive workflow orchestration
91
92	See the complete reference ma

People who liked this also viewed

6 picks

Type

scientific-problem-selection

1.7kinstalls2.7kforks

View on GitHub

How to install scientific-problem-selection?

anthropics/knowledge-work-plugins/scientific-problem-selection

$npx -y skills add anthropics/knowledge-work-plugins --skill scientific-problem-selection

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Scientific Problem Selection Skills
2
3	A conversational framework for systematic scientific problem selection based on Fischbach & Walsh's "Problem choice and decision trees in science and engineering" (Cell, 2024).
4
5	## Getting Started
6
7	Present users with three entry points:
8
9	1) Pitch an idea for a new project — to work it up together
10
11	2) Share a problem in a current project — to troubleshoot together
12
13	3) Ask a strategic question — to navigate the decision tree together
14
15	This conversational entry meets scientists where they are and establishes a collaborative tone.
16
17	---
18
19	## Option 1: Pitch an Idea
20
21	### Initial Prompt
22	Ask: "Tell me the short version of your idea (1-2 sentences)."
23
24	### Response Approach
25	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.
26
27	### Follow-up Prompt
28	Then ask for more detail: "Now give me a bit more detail. You might include, however briefly or even say where you are unsure:
29	1. What exactly you want to do
30	2. How you currently plan to do it
31	3. If it works, why will it be a big deal
32	4. What you think are the major risks"
33
34	### Workflow
35	From there, guide the user through the early stages of problem selection and evaluation:
36	- Skill 1: Intuition Pumps - Refine and strengthen the idea
37	- Skill 2: Risk Assessment - Identify and manage project risks
38	- Skill 3: Optimization Function - Define success metrics
39	- Skill 4: Parameter Strategy - Determine what to fix vs. keep flexible
40
41	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.
42
43	---
44
45	## Option 2: Troubleshoot a Problem
46
47	### Initial Prompt
48	Ask: "Tell me a short version of your problem (1-2 sentences or whatever is easy)."
49
50	### Response Approach
51	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.
52
53	### Follow-up Prompt
54	Then ask: "Now give me a bit more detail. You might include, however briefly:
55	1. The overall goal of your project (if we have not talked about it before)
56	2. What exactly went wrong
57	3. Your current ideas for fixing it"
58
59	### Workflow
60	From there, guide the user through troubleshooting and decision tree navigation:
61	- Skill 5: Decision Tree Navigation - Plan decision points and navigate between execution and strategic thinking
62	- Skill 4: Parameter Strategy - Fix one parameter at a time, let others float
63	- Skill 6: Adversity Response - Frame problems as opportunities for growth
64	- Skill 7: Problem Inversion - Strategies for navigating around obstacles
65
66	Always include workarounds that might be useful whether or not the problem can be fixed easily.
67
68	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.
69
70	---
71
72	## Option 3: Ask a Strategic Question
73
74	### Initial Prompt
75	Ask: "Tell me the short version of your question (1-2 sentences)."
76
77	### Response Approach
78	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.
79
80	### Follow-up Prompt
81	Then ask: "Now give me a bit more detail. You might include, however briefly:
82	1. The setting (i.e., is this about a current or future project)
83	2. A bit more detail about what you're thinking"
84
85	### Workflow
86	From there, draw on the specific modules from the problem choice framework most appropriate to the question:
87	- Skills 1-4 for future project planning (ideation, risk, optimization, parameters)
88	- Skills 5-7 for current project navigation (decision trees, adversity, inversion)
89	- Skill 8 for communication and synthesis
90	- Skill 9 for comprehensive workflow orchestration
91
92	See the complete reference ma

People who liked this also viewed

6 picks

Type