Skip to main content
skill CX Codex

mechanical-engineering-research — Claude Code skill: guide

Coordinates mechanical engineering research, thermofluid analysis, and scientific writing with strict verification gates.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add hanhuark/mechanical-engineering-research-skill --skill mechanical-engineering-research -a claude-code
Open on GitHub

What mechanical-engineering-research does

This skill acts as a coordinator across mechanical engineering tasks, focusing on thermodynamics, heat transfer, fluid mechanics, and CFD. It sets technical invariants for units, coordinate frames, sign conventions, and conservation checks before interpreting numerical or experimental data.

The framework routes tasks to focused specialist skills when writing manuscripts, drafting proposals, or building publication schematics. A core integrity constraint forbids masking scientific inconsistencies behind polished prose: when conflicting evidence arises, the assistant must address physical assumptions and boundary conditions directly instead of generating speculative figures or unverified citations.

What it helps with

  • verify dimensional consistency and conservation laws across analysis code
  • classify research datasets by evidence quality before synthesis
  • audit engineering assumptions against limiting cases and analytical bounds
  • coordinate multi-step manuscript drafting and technical revision loops

Example prompts for the agent

  • Review the boundary conditions and energy conservation in this pipe flow simulation
  • Classify the evidence types for these heat exchanger experimental runs before plotting
  • Outline a research brief for turbomachinery trade-offs using the standard verification steps

How to install mechanical-engineering-research

1Skills CLI (Vercel)

npx skills add hanhuark/mechanical-engineering-research-skill --skill mechanical-engineering-research -a claude-code

2Manually: put the files in place

~/.claude/skills/mechanical-engineering-research/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/mechanical-engineering-research/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about mechanical-engineering-research

How to install mechanical-engineering-research in Claude Code?

Run npx skills add hanhuark/mechanical-engineering-research-skill --skill mechanical-engineering-research -a claude-code in your terminal.

What does mechanical-engineering-research do?

It enforces rigorous scientific workflows for thermofluid analysis, research writing, and model validation across engineering projects.

How does it handle unverified parameters or missing tools?

It requires flagging missing evidence explicitly rather than guessing distributions or inputs, keeping unresolved items open until validated.

Source text

SKILL.md · MIT
---
name: mechanical-engineering-research
description: Apply source-aware mechanical-engineering judgment to research, analysis, coding, writing, teaching, research identity, and release work. Use for thermal-fluid systems, heat transfer, fluid mechanics, thermodynamics, HVAC, energy systems, turbomachinery, piping, multiphase flow, experiments, correlations, CFD, reduced-order models, AI/ML, uncertainty, engineering datasets, literature reviews, citations, manuscripts, reviewer revisions, Overleaf packages, figures, proposals, research software, reproducibility, public releases, engineering teaching materials, or a research-project logo and visual identity.
---

# Mechanical Engineering Research

## Skill Suite

Use this skill as the cross-cutting coordinator when a request spans multiple research activities. For a focused deliverable, use the specialist skill that owns it:

- [thermal-fluid-analysis](../thermal-fluid-analysis/SKILL.md): thermal-fluid physics, experiments, CFD, correlations, uncertainty, scaling, and design tradeoffs.
- [research-writing-literature](../research-writing-literature/SKILL.md): literature synthesis, citations, introductions, manuscript sections, and figure-led discussion.
- [research-proposal-development](../research-proposal-development/SKILL.md): solicitation-aligned proposals, review criteria, preliminary results, milestones, risks, and proposal figures.
- [research-data-analysis](../research-data-analysis/SKILL.md): baseline cases, hypothesis-driven DOE, reproducible analysis, plots, CFD/experimental data, and ML evaluation.
- [research-slide-design](../research-slide-design/SKILL.md): research talks, posters, visual logic, speaker notes, and presentation QA.
- [research-schematic-design](../research-schematic-design/SKILL.md): publication-quality editable facility, mechanism, workflow, and graphical-abstract schematics.
- [research-mentor-review](../research-mentor-review/SKILL.md): constructive student-facing feedback with prioritized, actionable next steps.
- [reviewer-author-loop](../reviewer-author-loop/SKILL.md): iterative reviewer critique, author revision, verification, and re-review.

The coordinator retains the evidence and integrity gates below. Do not load all specialist skills by default; select the smallest combination that fits the actual deliverable.

For a substantial manuscript, review article, proposal, thesis chapter, or major revision, use the integrated workflow in [research-workflow-and-revision.md](references/research-workflow-and-revision.md). It coordinates the specialist skills around a shared evidence map, narrative architecture, revision roadmap, and final verification. Do not force a focused task through the full workflow.

When AI will draft or substantially revise research writing, use [author-guided-ai-writing.md](references/author-guided-ai-writing.md) to retain author control of the scientific story before drafting and at the revision decision gate. It standardizes author guidance and author review without treating style as evidence of authorship.

## Core Workflow

1. Define the engineering decision or research question.
   - Identify the system, geometry, materials or fluid, operating regime, boundary and initial conditions, outputs, constraints, and intended user.
   - Ask only for missing information that materially changes scientific validity or the work path. Otherwise state bounded assumptions and proceed.

2. Classify the evidence before interpreting it.
   - Label important inputs and results as measured, reported, simulated, derived, assumed, inferred, illustrative, screening-level, proposed, or independently validated.
   - Preserve source identity, applicability, uncertainty, and limitations. Treat search results and AI summaries as discovery aids, not evidence.

3. Establish the technical invariants.
   - Define symbols, dimensions, units, sign conventions, coordinate frames, time bases, system boundaries, property-evaluation states, and data ordering.
   - Keep these definitions consistent across equations, code, tables, figures, and prose.

4. Select the simplest credible method.
   - Begin with analytical bounds, conservation checks, accepted correlations, or a representative baseline case.
   - Add experiments, CFD, reduced-order modeling, or AI/ML only when they answer the physical question or overcome a stated limitation.

5. Verify in proportion to claim strength and consequence.
   - Check dimensional consistency, limiting cases, conservation, uncertainty, sensitivity, repeatability, numerical convergence, validation, leakage, domain shift, and failure modes as applicable.
   - When a result changes materially, identify whether data, code, assumptions, definitions, or boundaries caused the change before treating it as a physical trend.

6. Produce and verify the actual deliverable.
   - Trace claims, equations, figures, and tables to sources, data, transformations, code, environment, and limitations.
   - Run feasible tests, compile or render documents, inspect visual artifacts, and report exactly what was and was not verified.

## Integrity Gates

- Do not repair a scientific-validity problem only by polishing or weakening prose. Revise the analysis, model, experiment, code, data, or evidence chain when required.
- Do not invent a citation, source detail, engineering input, tool result, uncertainty distribution, or completion state. Preserve an unresolved item explicitly when verification is unavailable.
- When sources conflict, compare definitions, regimes, methods, dates, and evidence quality. Prefer primary evidence and later accepted user corrections; surface consequential conflicts that remain unresolved.
- When an engineering assumption is uncertain, state it, bracket it with a sensitivity or limiting case when feasible, and explain how it affects the conclusion.
- When a required tool or source is unavailable, use a credible non-destructive alternative if one exists. Otherwise state the blocked verification and the evidence needed to complete it.
- Distinguish local edits, staged changes, commits, pushes, releases, deployments, archives, and independent review.

## Task Router

Read only the references needed for the task.

| Task | Read |
| --- | --- |
| Research brief or trade study | [brief-template.md](references/brief-template.md) |
| End-to-end manuscript, review, proposal, thesis chapter, or major revision | [research-workflow-and-revision.md](references/research-workflow-and-revision.md) |
| AI-assisted manuscript, proposal, report, review, or response | [author-guided-ai-writing.md](references/author-guided-ai-writing.md) |
| Technical analysis, DOE, plotting, or results discussion | [technical-writing-analysis.md](references/technical-writing-analysis.md) |
| Equation explanations, claim-evidence audit, methods completeness, or figure/equation narrative | [technical-argument-audit.md](../research-writing-literature/references/technical-argument-audit.md) |
| Reader-focused technical-prose audit | [technical-prose-clarity.md](../research-writing-literature/references/technical-prose-clarity.md) |
| Abstract, manuscript, proposal, or reviewer-response editorial pass | [anti-formulaic-writing.md](references/anti-formulaic-writing.md) |
| Paper drafting or structural revision | [paper-writing-style.md](references/paper-writing-style.md) |
| Review article drafting, revision, or evidence-mapped narrative/scoping review | [review-article-workflow.md](references/review-article-workflow.md) |
| Reviewer response, highlighted manuscript, Overleaf package, or submission audit | [manuscript-revision-submission.md](references/manuscript-revision-submission.md) |
| Literature review or research-gap synthesis | [literature-review.md](references/literature-review.md) |
| Citation repair, bibliography audit, or claim verification | [citation-integrity.md](references/citation-integrity.md) |
| Dataset, software, benchmark, or repository-centered review | [dataset-software-review.md](references/dataset-software-review.md) |
| Experiment planning or uncertainty analysis | [experimental-design-and-uncertainty.md](references/experimental-design-and-uncertainty.md) |
| CFD, ROM, surrogate, or ML credibility | [model-verification-and-ml-credibility.md](references/model-verification-and-ml-credibility.md) |
| Material result change or construct redefinition | [result-change-and-construct-audit.md](references/result-change-and-construct-audit.md) |
| Data provenance, benchmark design, research package, or public release | [data-provenance-and-release.md](references/data-provenance-and-release.md) |
| Figure, table, Word, PDF, spreadsheet, or slide QA | [scientific-figure-and-artifact-qa.md](references/scientific-figure-and-artifact-qa.md) |
| Scientific schematic, graphical abstract, facility, workflow, or system diagram | [research-schematic-design](../research-schematic-design/SKILL.md) |
| Thermal-fluid AI/ML workflow | [ai-tools-thermal-fluids.md](references/ai-tools-thermal-fluids.md) |
| Research code, pipeline, notebook, or package | [research-coding.md](references/research-coding.md) |
| Overleaf, VS Code, GitHub, git, or archival toolchain | [research-toolchain.md](references/research-toolchain.md) |
| Federal proposal or technical narrative | [proposal-development.md](references/proposal-development.md) |
| Proposal budget, budget justification, or subaward budget | [budget-and-justification.md](references/budget-and-justification.md) |
| Research presentation or poster | [presentation-slides.md](references/presentation-slides.md) |
| Mechanical-engineering teaching material | [teaching-mechanical-engineering.md](references/teaching-mechanical-engineering.md) |
| Invention disclosure or commercialization support | [innovation-commercialization.md](references/innovation-commercialization.md) |
| Research-project logo, laboratory or software identity, icon, wordmark, or brand asset pack | [research-logo-and-identity.md](references/research-logo-and-identity.md) |
| Explicit request to match Han Hu's established research-writing style | [han-hu-research-style.md](references/han-hu-research-style.md) |
| Calibrated Han Hu manuscript drafting or revision with a private corpus | [han-hu-style-calibration-protocol.md](references/han-hu-style-calibration-protocol.md) |

For document, PDF, spreadsheet, or presentation files, also use any available format-specific skill for file manipulation and rendering. Keep this skill responsible for engineering validity and scientific interpretation.

For a manuscript authored or supervised by Han Hu, read [han-hu-research-style.md](references/han-hu-research-style.md) together with the task-specific paper and figure references even when the request does not explicitly ask for style matching. When the user provides or configures a private style-calibration corpus, also read [han-hu-style-calibration-protocol.md](references/han-hu-style-calibration-protocol.md), retrieve only genre-matched evidence, and report the evidence status of the exemplars used.

For iterative peer-review work, use `reviewer-author-loop` as the process scaffold when available. Apply this skill to physics, equations, instrumentation, uncertainty, data reduction, figures, modeling assumptions, and claim support.

## Output Contract

- Lead with the engineering answer, finding, or decision.
- State material assumptions, definitions, units, validity ranges, and evidence class.
- Explain the governing mechanism and compare credible alternatives or bounds.
- Report uncertainty, validation, failure modes, and residual risk at the level needed by the claim.
- Provide traceable artifacts and exact verification results when files or code are involved.
- End with the smallest useful next calculation, experiment, simulation, source check, or author decision.

© hanhuark · MIT · hanhuark/mechanical-engineering-research-skill

Similar skills

All skills for Science and research →

From the same set9

thermal-fluid-analysis This skill guides analysis of thermal-fluid systems, experiments, and CFD. Use it to connect numerical results with physical mechanisms, assumptions, and limits of applicability. CX Codex +1 ★ 22repo stars reviewer-author-loop A skill that runs a reviewer, an author and a verifier in a loop over your manuscript. Useful when you need it revised until it passes. CX Codex +1 ★ 22repo stars research-writing-literature Guides academic manuscripts, literature syntheses, methodology sections, and figure discussions into evidence-backed research narratives. CX Codex +1 ★ 22repo stars research-slide-design This skill shapes technical talks and posters around clear visual claims and a logical slide sequence. Use it for seminars, conference talks, or defenses. CX Codex +1 ★ 22repo stars research-schematic-design Turns a figure request into a technical brief, then builds an editable vector schematic with exact labels and units. Useful when the drawing has to match the manuscript and the data. CX Codex +1 ★ 22repo stars research-proposal-development Structures research proposals around sponsor solicitations, testable aims, and reviewer logic. Useful for grant applications. CX Codex +1 ★ 22repo stars research-mentor-review This skill reviews research writing, methods, analysis, code, figures, and presentations, then turns critique into next steps. Use it for evidence-based mentoring feedback without unsupported scientific claims. CX Codex +1 ★ 22repo stars research-data-analysis Gives the agent a routine for baseline cases, hypothesis-driven DOE and plots that show uncertainty. Built for engineering experiments and simulations. CX Codex +1 ★ 22repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor