Agent skill

scientific-problem-selection

Guides scientists through systematic research problem selection using a 9-skill framework based on Fischbach & Walsh (Cell, 2024). Use when pitching a new research idea, troubleshooting a stuck project, evaluating project risks, planning research strategy, or choosing what problem to work on. Covers ideation, risk assessment, optimization, parameter strategy, decision trees, adversity planning, and synthesis.

Stars 10
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/philoserf/claude-code-setup/tree/main/skills/scientific-problem-selection

SKILL.md

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.

See references/00-overview.md for core framework concepts (paradoxes, evaluation axes), audience guidance, and expected outcomes.


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

text
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

Reference Materials

Detailed skill documentation is available in the references/ folder:

File Content Search Patterns
00-overview.md Framework concepts, audience, outcomes Paradox, Graduate, Expected
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

Expand your agent's capabilities with these related and highly-rated skills.

philoserf/claude-code-setup

pre-release

Validates a project is ready to tag and ship. Use when tagging a release, cutting a version, shipping a package, or asking "are we ready to release?" Checks repo hygiene, CI status, docs, version sync, and build verification. Optimized for Obsidian plugins with fallback detection for other project types.

10 0
Explore
philoserf/claude-code-setup

local-issues

Reviews a codebase for bugs, design issues, and code cleanliness problems with specific file paths and line numbers. Use when auditing code quality, finding bugs, doing a code review, finding problems, or reviewing a project for issues. Creates issue files in `.issues/` directory.

10 0
Explore
philoserf/claude-code-setup

skill-improve

Generates prioritized improvement recommendations for Claude Code skills. Use when improving skills, enhancing customizations, or wanting actionable feedback on how to make a skill better. Provides impact/effort prioritization with specific fix suggestions.

10 0
Explore
philoserf/claude-code-setup

release

Executes the final release workflow for Obsidian plugins after pre-release checks pass. Use when tagging a release, publishing a version, or shipping an Obsidian plugin. Bumps version via bun run script, creates git tag, pushes to trigger GitHub Actions, and updates GitHub release notes from CHANGELOG.md.

10 0
Explore
philoserf/claude-code-setup

skill-quality

Scores Claude Code skills (1-5) across 6 weighted quality dimensions aligned with official Anthropic docs. Use when evaluating skill quality, rating skills, scoring customizations, comparing skill effectiveness, or checking if a skill follows best practices. Produces per-dimension scores with evidence, weighted totals, quality tier classification, and actionable improvement recommendations.

10 0
Explore
philoserf/claude-code-setup

obsidian-cli

Interacts with Obsidian vaults using the Obsidian CLI to read, create, and manage notes, tasks, properties, tags, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, add to daily note, find notes about a topic, check tasks, append to a note, query the vault, list tags, list files, manage bookmarks, check sync status, view file history, use templates, query bases, run QuickAdd, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.

10 0
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results