⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

v0.4.0

mechanical-engineering-research

hanhuark@hanhuark⭐ 25 stars· last commit 9d ago· 0 open issues

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.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐ 25 on GitHubGitHub ↗

Growing

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

Mechanical Engineering Research Skill | Thermal-Fluid Research Workflow Plugin

Repository scope, evidence, and reuse boundaries are also available in the NED3 resource manifest.

English | 简体中文 | 繁體中文

A domain-rigor layer and modular skill suite for thermal-fluid mechanical engineering research with AI agents.

Generic research agents can summarize papers and draft prose. This plugin helps them do the harder mechanical-engineering work: check heat-transfer and fluid-flow assumptions, catch invalid correlation use, question CFD validation, protect uncertainty analysis, explain mechanisms, and turn evidence into decision-ready research artifacts.

Use it when a thermal-fluid answer needs to be physically defensible, not just well written.

The suite keeps task-specific instructions small and discoverable while retaining one coordinator for work that crosses boundaries:

SkillPrimary use
mechanical-engineering-researchCross-cutting thermal-fluid research coordination and rigor gates
thermal-fluid-analysisPhysics, experiments, CFD, correlations, uncertainty, and trade studies
research-writing-literatureLiterature reviews, citations, manuscript sections, and figure discussion
research-proposal-developmentSolicitation-aligned narratives, milestones, risks, and proposal figures
research-data-analysisBaseline-first DOE, data processing, plots, and ML/CFD/experimental analysis
research-slide-designGraphics-first talks, posters, speaker notes, and visual QA
research-schematic-designEditable scientific schematics, graphical abstracts, and facility or workflow figures
research-mentor-reviewConstructive, actionable student-facing research feedback
reviewer-author-loopIterative peer review, revision, verification, and re-review

Version Codex Plugin Claude Code Skill Domain License: MIT GitHub stars

If this helps your research workflow, please star the repo so other mechanical-engineering researchers can find it.

Want the fastest path? Start with QUICKSTART.md.

You want to...Start here
Try the plugin on one research taskFollow QUICKSTART.md, then use a prompt you can independently check.
Improve a recurring lab workflowUse the focused-skill pilot table in the Adoption Guide.
Teach the underlying engineering AI practicesExplore the companion Machine Learning for Engineers curriculum.
Cite or improve the softwareUse CITATION.cff or read Contributing.

The plugin assists reasoning and workflow; it does not replace the investigator's scientific judgment, source verification, authorship responsibility, or data-rights obligations.

Two-Minute Demo

Paste a prompt like this after installing the skill:

Use the mechanical-engineering-research skill to review this claim:

"The CFD model proves that the new microchannel heat sink is optimal because
the average Nusselt number is 40% higher than the baseline. The simulation used
k-epsilon turbulence, a coarse wall mesh, constant water properties, and three
flow rates between Re = 350 and 900. Pressure drop is not discussed."

Expected style of response:

Bottom line: The claim is overconfident. The result may indicate better heat
transfer in the tested cases, but it does not prove optimality.

Key issues:
- Re = 350-900 may be laminar or transitional for the stated geometry, so a
  k-epsilon turbulence model needs justification.
- A coarse wall mesh weakens confidence in wall heat flux and Nusselt number.
- Constant water properties may be acceptable only over a small temperature
  range; the temperature span must be stated.
- A 40% Nusselt increase is incomplete without pressure drop, pumping power,
  and thermal resistance.
- "Optimal" requires a design space, objective function, constraints, and
  uncertainty or grid-independence evidence.

Next checks: compare against laminar correlations or a conjugate heat-transfer
baseline, report y+ or wall treatment, run mesh independence, include pressure
drop and pumping power, and rewrite the claim as evidence from a limited CFD
study rather than proof of global optimality.

Workflow

%%{init: {"theme": "base", "themeVariables": {"fontFamily": "Inter, Segoe UI, Arial, sans-serif", "primaryColor": "#ecfeff", "primaryTextColor": "#0f172a", "primaryBorderColor": "#0f766e", "lineColor": "#475569", "secondaryColor": "#fff7ed", "tertiaryColor": "#f8fafc", "clusterBkg": "#ffffff", "clusterBorder": "#cbd5e1", "edgeLabelBackground": "#ffffff"}}}%%
flowchart TB
    A["Research Request"]:::input
    B["Plugin Router"]:::core

    C["Academic Scaffold"]:::scaffold
    D["ME Judgment Layer"]:::core

    A --> B
    C -. "process" .-> B
    B --> D

    D --> E{"Mode"}:::gate

    E --> F1["Literature Map"]:::lane
    E --> F2["Analysis + DOE"]:::lane
    E --> F3["CFD + Tests"]:::lane
    E --> F4["Writing + Proposals"]:::lane
    E --> F5["Code + AI/ML"]:::lane
    E --> F6["Slides + IP"]:::lane

    F1 --> G
    F2 --> G
    F3 --> G
    F4 --> G
    F5 --> G
    F6 --> G

    G["Rigor Gate"]:::gate
    H["Decision Output"]:::output
    I["Reusable Artifact"]:::artifact

    G --> H --> I

    classDef input fill:#eff6ff,stroke:#2563eb,stroke-width:2px,color:#0f172a;
    classDef core fill:#ccfbf1,stroke:#0f766e,stroke-width:3px,color:#0f172a;
    classDef scaffold fill:#f8fafc,stroke:#64748b,stroke-width:2px,color:#0f172a;
    classDef lane fill:#fff7ed,stroke:#f97316,stroke-width:2px,color:#0f172a;
    classDef gate fill:#fef3c7,stroke:#d97706,stroke-width:3px,color:#0f172a;
    classDef output fill:#ecfdf5,stroke:#16a34a,stroke-width:3px,color:#0f172a;
    classDef artifact fill:#f5f3ff,stroke:#7c3aed,stroke-width:2px,color:#0f172a;

Editable Mermaid source: assets/workflow.mmd.

What It Catches

  • Correlations used outside their Reynolds, Prandtl, geometry, roughness, orientation, or phase-change validity range.
  • CFD claims without mesh independence, wall treatment, convergence, boundary-condition, property-model, or validation evidence.
  • Experiment plans missing sensor calibration, uncertainty propagation, repeatability, heat-loss correction, or flow-development checks.
  • AI/ML workflows with leakage across videos, surfaces, experiments, geometries, pressures, or simulation families.
  • Literature reviews that list papers chronologically instead of synthesizing mechanisms, methods, gaps, and benchmark evidence.
  • Prop

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • skills/mechanical-engineering-research/SKILL.md7.8 KBupstream ↗
    ---
    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.
    
    ## 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) |
    | Technical analysis, DOE, plotting, or results discussion | [technical-writing-analysis.md](references/technical-writing-analysis.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) |
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/hanhuark-mechanical-engineering-research-skill-skills-mechanical-engineering-res.md

// REPO STATS

25 stars
0 open issues
Last commit: 9d ago