tooluniverse-clinical-trial-design
Strategic clinical trial design feasibility assessment. Analyzes 6 dimensions (endpoint, population, comparator, effect size, duration, regulatory pathway) using precedent trials and FDA guidance. Produces enrollment projections, endpoint recommendations, and approval-pathway analysis. Use for trial-protocol design, power/sample-size estimation, comparator selection, and FDA submission strategy. Driven by precedent-based reasoning rather than first-principles math.
What this skill does
# Clinical Trial Design Feasibility Assessment
Systematically assess clinical trial feasibility by analyzing 6 research dimensions. Produces comprehensive feasibility reports with quantitative enrollment projections, endpoint recommendations, and regulatory pathway analysis.
**IMPORTANT**: Always use English terms in tool calls (drug names, disease names, biomarker names), even if the user writes in another language. Only try original-language terms as a fallback if English returns no results. Respond in the user's language.
## Reasoning Before Searching
Trial design starts with the question, not the methods. Answer these four questions before running any tools — they determine everything else:
1. **What is the primary endpoint?** Is it overall survival (gold standard but slow), PFS (faster but surrogate), ORR (single-arm friendly but not always accepted), or a biomarker (needs validation as surrogate first)? The endpoint determines FDA pathway, statistical design, and duration.
2. **Who is the population?** Broad unselected vs. biomarker-enriched. Enriched populations have higher response rates, allowing smaller trials — but require a validated companion diagnostic and reduce the eligible patient pool.
3. **What is the comparator?** Placebo (only if no standard of care exists), active control (requires non-inferiority or superiority framing), or single-arm with historical control (acceptable for rare diseases or breakthrough designations, but FDA scrutiny is high).
4. **Is the effect size realistic given the mechanism?** A 20% improvement in ORR over SOC requires ~100 patients per arm. A 50% improvement requires ~30. If the mechanism only justifies a 10% improvement, the trial may be underpowered regardless of design. Check precedent effect sizes in similar trials before committing to an endpoint.
These four answers determine sample size, duration, and trial design. Look them up from precedent trials and FDA guidance — do not derive them from first principles.
**LOOK UP DON'T GUESS**: Never assume what the standard of care is for an indication — look it up with DrugBank and FDA tools. Never assume an endpoint is FDA-accepted — verify with `search_clinical_trials` precedents and `OpenFDA_get_approval_history`. Never estimate prevalence from memory — use OpenTargets, gnomAD, or COSMIC.
## Core Principles
### 1. Report-First Approach (MANDATORY)
**DO NOT** show tool outputs to user. Instead:
1. Create `[INDICATION]_trial_feasibility_report.md` FIRST
2. Initialize with all section headers
3. Progressively update as data arrives
4. Present only the final report
### 2. Evidence Grading System
| Grade | Symbol | Criteria | Examples |
|-------|--------|----------|----------|
| **A** | 3-star | Regulatory acceptance, multiple precedents | FDA-approved endpoint in same indication |
| **B** | 2-star | Clinical validation, single precedent | Phase 3 trial in related indication |
| **C** | 1-star | Preclinical or exploratory | Phase 1 use, biomarker validation ongoing |
| **D** | 0-star | Proposed, no validation | Novel endpoint, no precedent |
### 3. Feasibility Score (0-100)
Weighted composite score:
- **Patient Availability** (30%): Population size x biomarker prevalence x geography
- **Endpoint Precedent** (25%): Historical use, regulatory acceptance
- **Regulatory Clarity** (20%): Pathway defined, precedents exist
- **Comparator Feasibility** (15%): Standard of care availability
- **Safety Monitoring** (10%): Known risks, monitoring established
**Interpretation**: >=75 HIGH (proceed), 50-74 MODERATE (additional validation), <50 LOW (de-risking required)
---
## When to Use This Skill
Apply when users:
- Plan early-phase trials (Phase 1/2 emphasis)
- Need enrollment feasibility assessment
- Design biomarker-selected trials
- Evaluate endpoint strategies
- Assess regulatory pathways
- Compare trial design options
- Need safety monitoring plans
**Trigger phrases**: "clinical trial design", "trial feasibility", "enrollment projections", "endpoint selection", "trial planning", "Phase 1/2 design", "basket trial", "biomarker trial"
---
## Core Strategy: 6 Research Paths
Execute 6 parallel research dimensions. See `STUDY_DESIGN_PROCEDURES.md` for detailed steps per path.
```
Trial Design Query
|
+-- PATH 1: Patient Population Sizing
| Disease prevalence, biomarker prevalence, geographic distribution,
| eligibility criteria impact, enrollment projections
|
+-- PATH 2: Biomarker Prevalence & Testing
| Mutation frequency, testing availability, turnaround time,
| cost/reimbursement, alternative biomarkers
|
+-- PATH 3: Comparator Selection
| Standard of care, approved comparators, historical controls,
| placebo appropriateness, combination therapy
|
+-- PATH 4: Endpoint Selection
| Primary endpoint precedents, FDA acceptance history,
| measurement feasibility, surrogate vs clinical endpoints
|
+-- PATH 5: Safety Endpoints & Monitoring
| Mechanism-based toxicity, class effects, organ-specific monitoring,
| DLT history, safety monitoring plan
|
+-- PATH 6: Regulatory Pathway
Regulatory precedents (505(b)(1), 505(b)(2)), breakthrough therapy,
orphan drug, fast track, FDA guidance
```
---
## Report Structure (14 Sections)
Create `[INDICATION]_trial_feasibility_report.md` with all 14 sections. See `REPORT_TEMPLATE.md` for full templates with fillable fields.
1. **Executive Summary** - Feasibility score, key findings, go/no-go recommendation
2. **Disease Background** - Prevalence, incidence, SOC, unmet need
3. **Patient Population Analysis** - Base population, biomarker selection, eligibility funnel, enrollment projections
4. **Biomarker Strategy** - Primary biomarker, alternatives, testing logistics
5. **Endpoint Selection & Justification** - Primary/secondary/exploratory endpoints, statistical considerations
6. **Comparator Analysis** - SOC, trial design options (single-arm vs randomized vs non-inferiority), drug sourcing
7. **Safety Endpoints & Monitoring Plan** - DLT definition, mechanism-based toxicities, organ monitoring, SMC
8. **Study Design Recommendations** - Phase, design type, schema, eligibility, treatment plan, assessment schedule
9. **Enrollment & Site Strategy** - Site selection, enrollment projections, recruitment strategies
10. **Regulatory Pathway** - FDA pathway, precedents, pre-IND meeting, IND timeline
11. **Budget & Resource Considerations** - Cost drivers, timeline, FTE requirements
12. **Risk Assessment** - Feasibility risks, scientific risks, mitigation strategies
13. **Success Criteria & Go/No-Go Decision** - Phase 1/2 criteria, interim analysis, feasibility scorecard
14. **Recommendations & Next Steps** - Final recommendation, critical path to IND, alternative designs
---
## Tool Reference by Research Path
### PATH 1: Patient Population Sizing
- `OpenTargets_get_disease_id_description_by_name` - Disease lookup
- `OpenTargets_get_diseases_phenotypes_by_target_ensembl` - Prevalence data
- `ClinVar_search_variants` - Biomarker mutation frequency
- `gnomad_search_variants` - Population allele frequencies
- `PubMed_search_articles` - Epidemiology literature
- `search_clinical_trials` - Enrollment feasibility from past trials
### PATH 2: Biomarker Prevalence & Testing
- `ClinVar_get_variant_details` - Variant pathogenicity
- `COSMIC_search_mutations` - Cancer-specific mutation frequencies
- `gnomad_get_variant` - Population genetics
- `PubMed_search_articles` - CDx test performance, guidelines
### PATH 3: Comparator Selection
- `drugbank_get_drug_basic_info_by_drug_name_or_id` - Drug info
- `drugbank_get_indications_by_drug_name_or_drugbank_id` - Approved indications
- `drugbank_get_pharmacology_by_drug_name_or_drugbank_id` - Mechanism
- `FDA_OrangeBook_search_drug` - Generic availability
- `OpenFDA_get_approval_history` - Approval details
- `search_clinical_trials` - Historical control data
### PATH 4: Endpoint Selection
- `search_clinical_trials` - Precedent trials, endpoints used
- `PubMed_Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.