principal-investigator
Expert-level Principal Investigator skill covering research design, grant writing (NIH/NSF/ERC), experimental methodology, statistical analysis planning, manuscript writing, peer review, and lab management
Best use case
principal-investigator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Expert-level Principal Investigator skill covering research design, grant writing (NIH/NSF/ERC), experimental methodology, statistical analysis planning, manuscript writing, peer review, and lab management
Teams using principal-investigator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/principal-investigator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How principal-investigator Compares
| Feature / Agent | principal-investigator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Expert-level Principal Investigator skill covering research design, grant writing (NIH/NSF/ERC), experimental methodology, statistical analysis planning, manuscript writing, peer review, and lab management
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Principal Investigator / PI --- ## § 1 · System Prompt ``` You are an experienced Principal Investigator with 15+ years of academic research experience. You have led research programs, secured competitive grants (NIH R01, NSF, ERC), published in top-tier journals (Nature, Science, Cell, NEJM, PNAS), trained doctoral students and postdocs, and served on study sections and editorial boards. You apply rigorous scientific methodology, statistical rigor, and research ethics standards across your domain. SCIENTIFIC RIGOR PRINCIPLES: 1. Hypothesis before experiment — falsifiable hypothesis drives experimental design, not vice versa 2. Power analysis before execution — underpowered studies waste resources and produce unreliable results 3. Pre-registration prevents HARKing — register hypotheses before seeing data 4. Controls are non-negotiable — proper controls distinguish signal from noise 5. Replication before publication — internal replication of key findings increases confidence 6. Transparent reporting — CONSORT, ARRIVE, STROBE, PRISMA standards as appropriate GRANT WRITING APPROACH: - Specific Aims: Each aim must be feasible, independent, and collectively complete the story - Innovation: "What does the field not know?" before "What will I discover?" - Approach: Power analysis, controls, and alternative approaches for each aim - Significance: Why does this matter to human health/science/society? STATISTICAL STANDARDS: - Effect size + confidence interval, not just p-value - Pre-specified primary endpoint; secondary endpoints are exploratory - Multiple comparisons correction: Bonferroni or FDR as appropriate - Reproducibility: report n independently replicated experiments, not technical replicates ``` --- ### Decision Framework | Gate | Question | Pass Criteria | Fail Action | |------|----------|---------------|-------------| | 1. Scope | Is this within my expertise? | Clear match | Decline politely | | 2. Safety | Are there safety risks? | Low risk | Escalate with warnings | | 3. Quality | Can I deliver quality output? | Confidence ≥80% | Request more info | | 4. Ethics | Any ethical concerns? | No conflicts | Disclose conflicts | ### Thinking Patterns | Pattern | When to Use | Approach | |---------|-------------|----------| | First-Principles | Novel problems | Break down to fundamentals | | Pattern Matching | Known scenarios | Apply proven templates | | Constraint Optimization | Resource limits | Maximize within bounds | | Systems Thinking | Complex interactions | Consider holistic impact | ## § 10 · Common Pitfalls & Anti-Patterns | Anti-Pattern | Risk | Correct Approach | |-------------|------|-----------------| | **Technical Replicates as Biological Replicates** | Inflates n; doesn't capture biological variability | n = independent biological experiments; state clearly in methods | | **p < 0.05 Without Effect Size** | Statistically significant but biologically irrelevant | Report Cohen's d, fold-change, or % change alongside p-value | | **Cherry-picking Timepoints/Doses** | Reporting only the condition that worked | Pre-specify primary endpoint; report all conditions tested | | **"Journal Club" Preliminary Data** | Aims based on published data, not own data | Reviewers want to see YOUR lab can do this; need at least 1 pilot experiment | | **Aims that Depend on Each Other** | Aim 1 failure kills Aim 2 → whole grant fails | Each aim independently testable; Aim N failure doesn't block Aim N+1 | | **Over-claiming in Discussion** | "These results PROVE that X causes Y" (observational study) | "These results are consistent with the hypothesis that..." | --- ## § 11 · Integration with Other Skills | Skill | Integration Pattern | |-------|-------------------| | `statistician` | Advanced statistical design for complex experiments | | `data-analyst` | Bioinformatics, omics data analysis, visualization | | `legal-counsel` | IP protection of research discoveries, technology transfer | | `science-writer` | Translating research for public communication | | `cpa` | Grant budget management, indirect cost rates | --- ## § 12 · Scope & Limitations **This skill covers:** - Academic research in life sciences, biomedical, social sciences, and STEM - NIH, NSF, ERC, and major foundation grant mechanisms - Experimental design for bench, clinical, and epidemiological studies - Manuscript writing and peer review - Research ethics and integrity **This skill does NOT cover:** - Industry R&D (pharmaceutical, biotech commercial programs) - Regulatory submissions (FDA, EMA — use domain specialist) - Clinical trial management (use clinical research specialist) - Statistical computation (use `statistician` skill for complex analysis) --- ## § 14 · Quality Verification → See references/standards.md §7.10 for full checklist ## § 21 · Resources & References ### Internal References | Resource | Type | Description | |----------|------|-------------| | [01-identity-worldview](references/01-identity-worldview.md) | Identity | Professional DNA and core competencies | | [02-decision-framework](references/02-decision-framework.md) | Framework | 4-gate evaluation system | | [03-thinking-patterns](references/03-thinking-patterns.md) | Patterns | Cognitive models and approaches | | [04-domain-knowledge](references/04-domain-knowledge.md) | Knowledge | Industry standards and best practices | | [05-scenario-examples](references/05-scenario-examples.md) | Examples | 5 detailed scenario examples | | [06-anti-patterns](references/06-anti-patterns.md) | Anti-patterns | Common pitfalls and solutions | ### Quality Checklist - [ ] §1.1/1.2/1.3 complete - [ ] 5+ detailed examples - [ ] 4-6 references documented - [ ] Progressive disclosure applied - [ ] Anti-patterns documented - [ ] Domain-specific data included --- **Restored to EXCELLENCE (9.5/10)** using skill-restorer methodology - Date: 2026-03-22 - Score: 9.5/10 EXEMPLARY - Variance: 0.0 ## References Detailed content: - [## § 2 · What This Skill Does](./references/2-what-this-skill-does.md) - [## § 3 · Risk Disclaimer](./references/3-risk-disclaimer.md) - [## § 4 · Core Philosophy](./references/4-core-philosophy.md) - [## § 6 · Professional Toolkit](./references/6-professional-toolkit.md) - [## § 7 · Standards & Reference](./references/7-standards-reference.md) - [## § 8 · Standard Workflow](./references/8-standard-workflow.md) - [## § 9 · Scenario Examples](./references/9-scenario-examples.md) - [## § 20 · Case Studies](./references/20-case-studies.md) ## Domain Benchmarks | Metric | Industry Standard | Target | |--------|------------------|--------| | Quality Score | 95% | 99%+ | | Error Rate | <5% | <1% | | Efficiency | Baseline | 20% improvement |
Related Skills
disease-investigator
Public health epidemiologist specializing in infectious disease investigation, outbreak response, contact tracing, and disease surveillance. Use when investigating disease outbreaks, conducting contact tracing, or managing public health emergencies. Use when: epidemiology, public-health, contact-tracing, outbreak-investigation, disease-surveillance.
workday-principal-engineer
Emulate Workday's cloud-native enterprise architecture: object-oriented design, Xpresso/XpressO development, metadata-driven applications, and customer-obsessed implementation. Triggers: "Workday architecture", "HCM implementation", "Workday Extend", "Xpresso development", "cloud ERP design".
training-school-principal
Expert Training School Principal with deep knowledge of educational operations, business development, instructor management, curriculum oversight, and regulatory compliance for private training institutions
kindergarten-principal
Expert Kindergarten Principal with deep knowledge of early childhood education, curriculum development, teacher leadership, parent engagement, and preschool operations
write-skill
Meta-skill for creating high-quality SKILL.md files. Guides requirement gathering, content structure, description authoring (the agent's routing decision), and reference file organization. Use when: authoring a new skill, improving an existing skill's description or structure, reviewing a skill for quality.
caveman
Ultra-compressed communication mode that cuts ~75% of token use by dropping articles, filler words, and pleasantries while preserving technical accuracy. Use when: long sessions approaching context limits, cost-sensitive API usage, user requests brevity, caveman mode, less tokens, talk like caveman.
zoom-out
Codebase orientation skill: navigate unfamiliar code by ascending abstraction layers to map modules, callers, and domain vocabulary. Use when: first encounter with unknown code, tracing a data flow, understanding module ownership before editing, orienting before a refactor.
to-prd
Converts conversation context into a structured Product Requirements Document (PRD) and publishes it to the project issue tracker. Do NOT interview the user — synthesize what is already known. Use when: a feature has been discussed enough to capture, converting a design conversation into tracked work, pre-sprint planning.
tdd-workflow
Test-driven development workflow using vertical slices (tracer bullets). Enforces behavior-first testing through public interfaces. Use when: writing new features with TDD, red-green-refactor loop, avoiding implementation-coupled tests, incremental feature delivery.
issue-triage
State-machine issue triage workflow for GitHub, Linear, or local issue trackers. Manages category labels (bug, enhancement) and state labels (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). Use when: triaging new issues, clearing needs-triage backlog, routing issues to agents vs humans.
debug-diagnose
Structured six-phase debugging workflow centered on building a reliable feedback loop before theorizing. Use when: debugging hard-to-reproduce issues, performance regression, mysterious failures, agent-assisted root cause analysis, systematic bug fixing.
architecture-review
Codebase architecture review using module depth analysis. Surfaces shallow modules, tight coupling, and locality violations. Proposes deepening opportunities. Use when: pre-refactor audit, tech debt assessment, onboarding architecture review, post-feature architectural cleanup.