peer-review
Systematic peer review toolkit. Evaluate methodology, statistics, design, reproducibility, ethics, figure integrity, reporting standards, for manuscript and grant review across disciplines.
What this skill does
# Scientific Critical Evaluation and Peer Review ## Overview Peer review is a systematic process for evaluating scientific manuscripts. Assess methodology, statistics, design, reproducibility, ethics, and reporting standards. Apply this skill for manuscript and grant review across disciplines with constructive, rigorous evaluation. ## When to Use This Skill This skill should be used when: - Conducting peer review of scientific manuscripts for journals - Evaluating grant proposals and research applications - Assessing methodology and experimental design rigor - Reviewing statistical analyses and reporting standards - Evaluating reproducibility and data availability - Checking compliance with reporting guidelines (CONSORT, STROBE, PRISMA) - Providing constructive feedback on scientific writing ## Visual Enhancement with Scientific Schematics **When creating documents with this skill, always consider adding scientific diagrams and schematics to enhance visual communication.** If your document does not already contain schematics or diagrams: - Use the **scientific-schematics** skill to generate AI-powered publication-quality diagrams - Simply describe your desired diagram in natural language - Nano Banana Pro will automatically generate, review, and refine the schematic **For new documents:** Scientific schematics should be generated by default to visually represent key concepts, workflows, architectures, or relationships described in the text. **How to generate schematics:** ```bash python scripts/generate_schematic.py "your diagram description" -o figures/output.png ``` The AI will automatically: - Create publication-quality images with proper formatting - Review and refine through multiple iterations - Ensure accessibility (colorblind-friendly, high contrast) - Save outputs in the figures/ directory **When to add schematics:** - Peer review workflow diagrams - Evaluation criteria decision trees - Review process flowcharts - Methodology assessment frameworks - Quality assessment visualizations - Reporting guidelines compliance diagrams - Any complex concept that benefits from visualization For detailed guidance on creating schematics, refer to the scientific-schematics skill documentation. --- ## Peer Review Workflow Conduct peer review systematically through the following stages, adapting depth and focus based on the manuscript type and discipline. ### Stage 1: Initial Assessment Begin with a high-level evaluation to determine the manuscript's scope, novelty, and overall quality. **Key Questions:** - What is the central research question or hypothesis? - What are the main findings and conclusions? - Is the work scientifically sound and significant? - Is the work appropriate for the intended venue? - Are there any immediate major flaws that would preclude publication? **Output:** Brief summary (2-3 sentences) capturing the manuscript's essence and initial impression. ### Stage 2: Detailed Section-by-Section Review Conduct a thorough evaluation of each manuscript section, documenting specific concerns and strengths. #### Abstract and Title - **Accuracy:** Does the abstract accurately reflect the study's content and conclusions? - **Clarity:** Is the title specific, accurate, and informative? - **Completeness:** Are key findings and methods summarized appropriately? - **Accessibility:** Is the abstract comprehensible to a broad scientific audience? #### Introduction - **Context:** Is the background information adequate and current? - **Rationale:** Is the research question clearly motivated and justified? - **Novelty:** Is the work's originality and significance clearly articulated? - **Literature:** Are relevant prior studies appropriately cited? - **Objectives:** Are research aims/hypotheses clearly stated? #### Methods - **Reproducibility:** Can another researcher replicate the study from the description provided? - **Rigor:** Are the methods appropriate for addressing the research questions? - **Detail:** Are protocols, reagents, equipment, and parameters sufficiently described? - **Ethics:** Are ethical approvals, consent, and data handling properly documented? - **Statistics:** Are statistical methods appropriate, clearly described, and justified? - **Validation:** Are controls, replicates, and validation approaches adequate? **Critical elements to verify:** - Sample sizes and power calculations - Randomization and blinding procedures - Inclusion/exclusion criteria - Data collection protocols - Computational methods and software versions - Statistical tests and correction for multiple comparisons #### Results - **Presentation:** Are results presented logically and clearly? - **Figures/Tables:** Are visualizations appropriate, clear, and properly labeled? - **Statistics:** Are statistical results properly reported (effect sizes, confidence intervals, p-values)? - **Objectivity:** Are results presented without over-interpretation? - **Completeness:** Are all relevant results included, including negative results? - **Reproducibility:** Are raw data or summary statistics provided? **Common issues to identify:** - Selective reporting of results - Inappropriate statistical tests - Missing error bars or measures of variability - Over-fitting or circular analysis - Batch effects or confounding variables - Missing controls or validation experiments #### Discussion - **Interpretation:** Are conclusions supported by the data? - **Limitations:** Are study limitations acknowledged and discussed? - **Context:** Are findings placed appropriately within existing literature? - **Speculation:** Is speculation clearly distinguished from data-supported conclusions? - **Significance:** Are implications and importance clearly articulated? - **Future directions:** Are next steps or unanswered questions discussed? **Red flags:** - Overstated conclusions - Ignoring contradictory evidence - Causal claims from correlational data - Inadequate discussion of limitations - Mechanistic claims without mechanistic evidence #### References - **Completeness:** Are key relevant papers cited? - **Currency:** Are recent important studies included? - **Balance:** Are contrary viewpoints appropriately cited? - **Accuracy:** Are citations accurate and appropriate? - **Self-citation:** Is there excessive or inappropriate self-citation? ### Stage 3: Methodological and Statistical Rigor Evaluate the technical quality and rigor of the research with particular attention to common pitfalls. **Statistical Assessment:** - Are statistical assumptions met (normality, independence, homoscedasticity)? - Are effect sizes reported alongside p-values? - Is multiple testing correction applied appropriately? - Are confidence intervals provided? - Is sample size justified with power analysis? - Are parametric vs. non-parametric tests chosen appropriately? - Are missing data handled properly? - Are exploratory vs. confirmatory analyses distinguished? **Experimental Design:** - Are controls appropriate and adequate? - Is replication sufficient (biological and technical)? - Are potential confounders identified and controlled? - Is randomization properly implemented? - Are blinding procedures adequate? - Is the experimental design optimal for the research question? **Computational/Bioinformatics:** - Are computational methods clearly described and justified? - Are software versions and parameters documented? - Is code made available for reproducibility? - Are algorithms and models validated appropriately? - Are assumptions of computational methods met? - Is batch correction applied appropriately? ### Stage 4: Reproducibility and Transparency Assess whether the research meets modern standards for reproducibility and open science. **Data Availability:** - Are raw data deposited in appropriate repositories? - Are accession numbers provided for public databases? - Are data sharing restrictions justified (e.g., patient privacy)? - Are data formats standard and accessible? **
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.