All skills
oaustegard avatar

/convening-experts

@5e58100

Convenes expert panels for problem-solving. Use when user mentions panel, experts, multiple perspectives, MECE, DMAIC, RAPID, Six Sigma, root cause analysis, strategic decisions, process improvement, or asks for philosophers/ancients (Socratic, Aristotelian, Stoic method experts).

Use this Skill: https://skilld.dev/gh/oaustegard/claude-skills/convening-experts

This session only. Nothing lands on disk.

examplestechnical-troubleshooting-example.md

≈2.9k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Example: ECL Background Signal Issue (Multi-Round)

User Query: "Our new cytokine multiplex assay is showing 3-4x higher background in serum samples compared to buffer. Same plates work fine with buffer controls."

Expert Panel: ECL Assay Troubleshooting

Panel Members:

  • Dr. Michael Rodriguez, Assay Scientist
  • Dr. Lisa Wang, Systems Thinker
  • Tom Anderson, Five Whys Facilitator

Round 1: Initial Analysis

Dr. Michael Rodriguez, Assay Scientist

Immediate Biochemical Suspects:

Serum introduces matrix complexity that buffer doesn't have. Three primary hypotheses:

  1. Non-specific antibody binding: Serum proteins (albumin, IgG) binding to capture or detection antibodies

    • Evidence needed: Does blocking buffer optimization help?
    • Test: Try different blocking agents (BSA vs casein vs fish gelatin)
  2. ECL signal interference: Serum components quenching or amplifying background ECL

    • Evidence needed: Dose-response with serum dilution
    • Expected: Linear reduction in background with dilution suggests matrix interference
  3. Antibody cross-reactivity: Detection antibody reacting with abundant serum proteins

    • Evidence needed: Run each cytokine individually vs multiplex
    • Expected: If one cytokine drives background, it's cross-reactivity

Critical Missing Data:

  • Serum dilution curve (1:2, 1:4, 1:10)?
  • Blocking buffer composition?
  • Background pattern across plate (uniform vs edge effects)?

Dr. Lisa Wang, Systems Thinker

System-Level Pattern Recognition:

This reads like a classic reinforcing feedback loop in assay development:

High background → Lower signal-to-noise → Push detection sensitivity up 
→ Amplifies background further → Higher background

Interconnections to Map:

  1. Sample prep → Blocking → Detection: Are we optimizing these in isolation or as a system?
  2. Plate coating → Capture antibody density → Non-specific binding sites: High capture density increases specific signal but also increases non-specific binding sites
  3. Detection antibody concentration → Signal vs Background ratio: There's usually an optimal concentration window

Emergence Observation: Multiplex assays show non-linear behavior. Background in multiplex ≠ sum of single-plex backgrounds because antibodies can interact.

Leverage Points:

  • Highest leverage: Sample dilution (reduces matrix effect exponentially)
  • Medium leverage: Blocking optimization (linear improvement)
  • Lowest leverage: Detection antibody concentration (narrow window)

System Hypothesis: You're likely in a "Limits to Growth" archetype—pushing sensitivity hits fundamental matrix limitations. The system wants you to either:

  1. Dilute samples more (accept lower sensitivity)
  2. Reduce matrix interference (pre-treatment)

Tom Anderson, Five Whys Facilitator

Root Cause Investigation:

Problem Statement: ECL background is 3-4x higher in serum than buffer.

Why #1: Why is background higher in serum? → Serum contains proteins/lipids that buffer doesn't have.

Why #2: Why do these serum components cause background signal? → They either bind non-specifically to the plate/antibodies OR interfere with ECL chemistry.

Why #3: Why isn't blocking preventing this non-specific binding? → Either blocking is insufficient OR the mechanism isn't binding-based.

Why #4: If blocking is insufficient, why? → Two possibilities: a) Blocking agent doesn't cover the right epitopes (wrong blocker) b) Blocking step is fine, but serum components displace blocker during incubation

Why #5: What allows serum components to displace blocker? → Incubation conditions (time, temperature, agitation) may favor displacement if serum proteins have higher affinity than blocker.

Diagnostic Tests:

  1. Extend blocking time: 2hr → 4hr (tests if coverage is incomplete)
  2. Add blocking agent to sample diluent (prevents displacement)
  3. Reduce sample incubation time (less time for displacement)

Causal Chain:

Serum proteins → Compete with blocker → Bind to plate/antibodies → 
Non-specific detection antibody binding → ECL background

Countermeasure Hypothesis: Add blocking agent (BSA/casein) to serum diluent to maintain blocking equilibrium during sample incubation.


Round 2: Cross-Examination

Dr. Rodriguez responds to Dr. Wang:

Lisa's reinforcing feedback loop insight is critical—I've been focused on individual variables, not the system dynamics.

Building on her point: If we're in a "Limits to Growth" archetype, we need to identify the limiting factor:

  • Is it the assay's fundamental sensitivity limit?
  • Or is it matrix interference we can engineer around?

Connecting to my hypothesis: Her leverage point analysis suggests I should prioritize:

  1. Highest impact: Increase sample dilution (1:2 → 1:4 or 1:10)
  2. Second priority: Optimize blocking
  3. Avoid: Increasing detection antibody concentration (low leverage, could worsen feedback loop)

Challenge to Tom's causal chain: His "displacement" hypothesis is testable and elegant. If true, adding BSA to sample diluent is a simple fix. But alternative hypothesis: What if the issue is ECL substrate interaction with serum lipids, not antibody binding? That wouldn't show displacement dynamics.

Proposed test to differentiate:

  • Run assay with streptavidin-HRP (no antibodies) on blocked plates with serum → If background persists, it's ECL chemistry interference, not antibody binding.

Dr. Wang responds to Tom:

Tom's Five Whys landed on "blocker displacement," which is mechanistically sound, but I want to question the boundary conditions:

The "Limits to Growth" archetype suggests there's a balancing feedback that will kick in:

Increase sample dilution → Lower matrix interference → Better S/N → 
BUT: Lower analyte concentration → Weaker signal → Worse S/N

So there's a sweet spot. Tom's countermeasure (add blocker to diluent) might shift that sweet spot, but won't eliminate the fundamental tension.

Integration with Michael's work: His streptavidin-HRP control test will tell us if we're dealing with:

  • Binding problem (Tom's displacement) → Blocker in diluent fixes it
  • Chemistry problem (ECL interference) → Need different approach (substrate change, lipid removal pre-treatment)

System-level recommendation: Don't optimize variables sequentially. Run a factorial experiment:

  • Sample dilution: 1:2, 1:4, 1:10
  • Blocker in diluent: Yes/No
  • Measure both signal and background

This maps the system behavior space rather than chasing one causal chain.


Tom responds to Dr. Rodriguez:

Michael's streptavidin-HRP control is brilliant—it's a classic root cause isolation technique. Cut out antibody variables entirely.

But I want to push back on the experimental complexity. Lisa's factorial experiment is thorough but requires 6+ plates. For troubleshooting, I prefer:

Sequential elimination with minimal experiments:

  1. Test 1: Add BSA to sample diluent (tests my displacement hypothesis)
    • If background drops → Root cause confirmed, move to optimization
    • If no change → Move to test 2
  2. Test 2: Streptavidin-HRP control (tests Michael's ECL interference hypothesis)
    • If background drops → Antibody-related, revisit blocking strategy
    • If background persists → ECL chemistry issue

Why sequential vs factorial? Each experiment gives diagnostic information that narrows the hypothesis space. If Test 1 solves it, we save 5 plates and 2 days.

However, I agree with Lisa's point about the "sweet spot." Once we identify root cause, we should run the factorial to optimize rather than tune variables one at a time.

Synthesis proposal:

  • Phase 1 (Diagnosis): Sequential tests (my approach)
  • Phase 2 (Optimization): Factorial design (Lisa's approach)

Round 3: Convergence

Dr. Rodriguez (Assay Scientist):

Consensus emerging: We've triangulated on a diagnostic workflow that combines our perspectives:

  1. Immediate test (Tom's sequential approach): Add BSA to serum diluent at same concentration as blocking buffer

    • Hypothesis: Blocker displacement
    • Decision point: If background reduces by 50%+, proceed to optimization
    • If not: Run streptavidin-HRP control (my test) to rule out ECL interference
  2. Optimization phase (Lisa's system approach): Factorial design on sample dilution × blocker concentration once mechanism is confirmed

Addressing Lisa's feedback loop concern: You're right that we can't eliminate the signal-vs-matrix tradeoff. But reframing the goal: We want S/N > 10 for lowest analyte concentration. That means:

  • 1:4 dilution with optimized blocking is likely optimal
  • Accept that we can't run serum at 1:2 dilution for this multiplex

Dr. Wang (Systems Thinker):

Agreement with convergence, but adding a systems safeguard:

Tom and Michael's workflow is sound, but we need to monitor for unintended consequences:

  • Increasing blocker in diluent might increase viscosity → worse mixing → inconsistent results
  • Higher dilution reduces matrix effects but also reduces dynamic range → check if that impacts customer use cases

Recommendation: Pilot with 3 customer serum samples (low, medium, high analyte) before committing to protocol change. This validates the system behavior across the input space.


Tom (Five Whys Facilitator):

Full agreement. Final workflow:

Phase 1: Root Cause Confirmation (1-2 days)

  • Test blocker-in-diluent modification
  • If inconclusive, run streptavidin control

Phase 2: Optimization (3-5 days)

  • Factorial experiment: dilution × blocker concentration
  • Measure signal, background, CV% across 3 customer serum pools

Phase 3: Validation (1 week)

  • Run optimized protocol with customer samples
  • Monitor for Lisa's unintended consequences (viscosity, dynamic range)

Risk mitigation: If we can't get S/N > 10 at practical dilutions, escalate to R&D for assay redesign (different antibody pairs, alternative blocking strategies, or pre-treatment methods).


Final Synthesis

Root Cause Hypothesis: Serum proteins displace blocking agent during sample incubation, leading to non-specific antibody binding and elevated ECL background (primary), with possible secondary contribution from ECL substrate interaction with serum lipids.

Three-Phase Resolution:

Immediate (Phase 1): Test blocker-in-diluent modification to confirm displacement mechanism. If inconclusive, isolate antibody vs ECL chemistry contribution via streptavidin-HRP control.

Optimization (Phase 2): Run factorial experiment on sample dilution (1:2, 1:4, 1:10) and blocker concentration to map system behavior and identify optimal S/N conditions.

Validation (Phase 3): Pilot optimized protocol with diverse customer serum samples, monitoring for unintended consequences (viscosity effects, dynamic range limitations).

Decision Framework:

  • If optimized protocol achieves S/N > 10 → Implement new SOP
  • If S/N remains < 10 → Escalate to assay redesign (different antibody pairs or sample pre-treatment)

Key Insight (Systems Perspective): This is a "Limits to Growth" scenario where increasing sensitivity amplifies background. The solution isn't higher sensitivity—it's shifting the system constraints through sample dilution and blocking equilibrium management.

Source: SKILL.md on GitHub

1 warning5mo4 checks · Risk SAFE
  • Gen Agent Trust Hub5mo

    The 'convening-experts' skill is a framework designed to help an AI agent simulate collaborative problem-solving between domain experts and strategic consultants. It provides structured templates for multi-round discussions and integrates established business frameworks and industry-specific context. The analysis found no evidence of malicious code, data exfiltration, or unauthorized command execution; the skill functions entirely through instructional guidance and provided reference documentation.

  • Socket5mo

    No alerts

  • Snyk5mo

    Risk: LOW · No issues

  • Runlayer7mo

    10/10 files flagged

Signed by skilld at 5e58100. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 weeks ago
metadata
{
  "version": "1.2.0"
}

README badge

README badge for oaustegard/claude-skills/convening-experts