davide/skills-hub
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor(repo): reorganize repo into skill package and script directories

Browse Source
This commit is contained in:
Davide Grilli
2026-03-19 14:50:28 +01:00
parent de74fc2fb5
commit fbc6ec4bd9
71 changed files with 332 additions and 2210 deletions
Download Patch File Download Diff File Expand all files Collapse all files

65
mechanical-skills/upload-md/bearings-seals-selection.md
View File

@@ -1,65 +0,0 @@
---
name: bearings-seals-selection
description: Bearing and seal selection for rotating equipment. Use this skill whenever the user asks about bearing type/life, preload, lubrication, sealing, contamination control, or shaft support architecture.
---
# Bearings And Seals Selection
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
choose bearing-seal architecture and life strategy.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- equivalent load and life model
- fits/preload thermal effects
- contamination ingress risk
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/calculation-report.md
View File

@@ -1,65 +0,0 @@
---
name: calculation-report
description: Calculation report preparation for auditable engineering calculations. Use this skill whenever the user needs formal calculation packs with equations, assumptions, units, and compliance-ready traceability.
---
# Calculation Report
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
produce auditable calculation packages with full traceability.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- equation/source traceability
- unit discipline and numerical reproducibility
- independent-check checklist
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/cnc-sheet-casting-forging.md
View File

@@ -1,65 +0,0 @@
---
name: cnc-sheet-casting-forging
description: Detailed manufacturing guidance for CNC machining, sheet metal, casting, and forging. Use this skill whenever the user requests geometry rules, draft/radii, tool access, or redesign for a specific process family.
---
# CNC Sheet Casting Forging Guidance
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
convert part geometry into process-specific design rules.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- process-specific geometric constraints
- allowance and stock strategy
- distortion and shrinkage controls
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/design-review-fmea.md
View File

@@ -1,65 +0,0 @@
---
name: design-review-fmea
description: Structured design review and FMEA for risk reduction. Use this skill whenever the user asks for design review checklists, failure prevention planning, or prioritization of design risks before release.
---
# Design Review And FMEA
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
run risk-driven design review and mitigation prioritization.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- function-failure-effect linkage
- severity/occurrence/detection rationale
- closure evidence for actions
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/dfm-dfa-review.md
View File

@@ -1,65 +0,0 @@
---
name: dfm-dfa-review
description: Design for manufacturing and assembly review for mechanical products. Use this skill whenever the user asks if a design is producible/assemblable, wants part-count reduction, or needs robust assembly flow.
---
# DFM DFA Review
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
improve producibility, assembly robustness, and cost-to-build.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- feature-process compatibility
- assembly sequence robustness
- mistake-proofing opportunities
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/dynamics-vibrations-analysis.md
View File

@@ -1,65 +0,0 @@
---
name: dynamics-vibrations-analysis
description: Rigid-body dynamics and vibration response analysis. Use this skill whenever the user asks about motion, acceleration loads, resonance, transmissibility, balancing, or dynamic amplification in machines.
---
# Dynamics And Vibrations Analysis
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
assess dynamic loads and vibration response.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- natural frequency separation
- damping assumptions
- transient shock and harmonic response checks
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/energy-efficiency-analysis.md
View File

@@ -1,65 +0,0 @@
---
name: energy-efficiency-analysis
description: Energy efficiency optimization for mechanical and thermo-fluid systems. Use this skill whenever the user wants to reduce energy consumption, compare efficiency options, or evaluate lifecycle energy impact of design choices.
---
# Energy Efficiency Analysis
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
quantify losses and rank efficiency improvements.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- loss tree by subsystem
- operating-point sensitivity
- payback-oriented prioritization
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/failure-root-cause-analysis.md
View File

@@ -1,65 +0,0 @@
---
name: failure-root-cause-analysis
description: Root cause analysis for field or test failures in mechanical systems. Use this skill whenever the user asks why a failure happened, needs 5-Why/fishbone evidence, or must define corrective actions.
---
# Failure Root Cause Analysis
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
isolate root causes and define corrective/preventive actions.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- evidence chain integrity
- competing hypothesis elimination
- verification of corrective actions
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/fatigue-fracture-analysis.md
View File

@@ -1,65 +0,0 @@
---
name: fatigue-fracture-analysis
description: Fatigue life and fracture risk assessment for cyclic loading. Use this skill whenever the user mentions S-N life, crack growth, endurance, variable amplitude cycles, weld fatigue, or brittle/ductile fracture concerns, even if test data is limited.
---
# Fatigue And Fracture Analysis
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
estimate durability and crack risk for cyclic duty.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- cycle counting assumptions
- mean stress correction
- damage accumulation and inspection interval
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/fea-cfd-review.md
View File

@@ -1,65 +0,0 @@
---
name: fea-cfd-review
description: Critical review of FEA/CFD models and simulation credibility. Use this skill whenever the user asks to validate simulation setup/results, challenge assumptions, or decide if analysis is decision-ready.
---
# FEA CFD Review
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
audit simulation credibility before design decisions.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- mesh/boundary-condition adequacy
- model validation against hand checks
- decision-readiness criteria
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/fluid-analysis.md
View File

@@ -1,65 +0,0 @@
---
name: fluid-analysis
description: Internal and external fluid flow analysis for engineering systems. Use this skill whenever the user asks about flow rate, pressure drop, Reynolds regime, valve/piping behavior, or fluid-system sizing.
---
# Fluid Analysis
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
evaluate flow regime and pressure-flow performance.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- compressible vs incompressible assumptions
- loss coefficient breakdown
- cavitation and NPSH risk
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/gear-design.md
View File

@@ -1,65 +0,0 @@
---
name: gear-design
description: Gear train design and verification for power transmission. Use this skill whenever the user asks about gear geometry, ratio selection, tooth stresses, micropitting/scuffing, or gearbox design tradeoffs.
---
# Gear Design
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
size and verify gears for strength, life, and efficiency.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- macro/micro geometry impacts
- contact and bending stress margins
- lubrication and thermal interaction
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/heat-treatment.md
View File

@@ -1,65 +0,0 @@
---
name: heat-treatment
description: Heat-treatment strategy for steels and alloys in mechanical design. Use this skill whenever the user asks about hardening, tempering, case depth, residual stresses, distortion, or hardness-toughness tradeoffs.
---
# Heat Treatment
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
define heat-treatment route tied to function and manufacturability.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- microstructure target by function
- distortion and crack risk controls
- verification plan for hardness/case depth
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/joints-design.md
View File

@@ -1,65 +0,0 @@
---
name: joints-design
description: Joint design for bolts, welds, adhesives, and hybrid joints. Use this skill whenever the user asks how to join parts or verify joint integrity under static, fatigue, thermal, or corrosive conditions.
---
# Joints Design
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
select and verify joining method and joint sizing.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- load path through joint stackup
- slip/leak/fatigue criteria
- assembly process sensitivity
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/machine-elements-selection.md
View File

@@ -1,65 +0,0 @@
---
name: machine-elements-selection
description: Integrated selection of machine elements for a mechanism or subsystem. Use this skill whenever the user asks to choose among bearings/gears/springs/joints/couplings under constraints of reliability, cost, and manufacturability.
---
# Machine Elements Selection
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
compare machine-element architectures and select justified configuration.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- multi-criteria trade study
- interface compatibility checks
- obsolescence and sourcing risk
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/material-failure-modes.md
View File

@@ -1,65 +0,0 @@
---
name: material-failure-modes
description: Material failure mode identification and prevention. Use this skill whenever the user asks about yielding, brittle fracture, creep, wear, corrosion-assisted cracking, or unexplained material degradation.
---
# Material Failure Modes
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
identify dominant failure mechanisms and controls.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- mechanism ranking by evidence
- threshold conditions
- preventive design/process controls
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/materials-metallurgy.md
View File

@@ -1,65 +0,0 @@
---
name: materials-metallurgy
description: Materials engineering and metallurgy guidance for design decisions. Use this skill whenever the user asks to choose metals/polymers/composites, compare material behavior, or evaluate metallurgical effects on performance.
---
# Materials And Metallurgy
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
select materials using performance, process, and risk criteria.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- temperature/environment compatibility
- anisotropy and processing state effects
- data confidence from sources
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/mechanical-orchestrator.md
View File

@@ -1,65 +0,0 @@
---
name: mechanical-orchestrator
description: Cross-domain mechanical engineering orchestration for complex design questions. Use this skill whenever a request spans multiple domains (stress, fatigue, thermal, fluid, materials, manufacturing, reliability), whenever requirements are incomplete, or whenever the user asks for a senior-level decision path and prioritization, even if they do not ask for an orchestrator explicitly.
---
# Mechanical Orchestrator
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
build a scoped decision flow across mechanics, materials, manufacturing, validation, and documentation.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- load-path decomposition
- cross-domain dependency map
- decision checkpoints with go/no-go criteria
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/modal-analysis.md
View File

@@ -1,65 +0,0 @@
---
name: modal-analysis
description: Modal behavior assessment for structures and assemblies. Use this skill whenever the user asks for mode shapes, eigenfrequencies, modal participation, or resonance avoidance strategies in design.
---
# Modal Analysis
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
identify modal risks and mitigation actions.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- mass/stiffness idealization quality
- mode participation relevance
- frequency margin to excitations
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/pressure-loss-pump-piping.md
View File

@@ -1,65 +0,0 @@
---
name: pressure-loss-pump-piping
description: Hydraulic network design including pressure losses, pumps, and piping. Use this skill whenever the user asks about line sizing, head losses, pump selection, NPSH, or piping layout effects.
---
# Pressure Loss Pump And Piping
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
size piping and pumping system at required duty.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- system curve construction
- NPSH/cavitation margin
- control valve authority checks
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/process-selection.md
View File

@@ -1,65 +0,0 @@
---
name: process-selection
description: Manufacturing process selection across machining, forming, casting, additive, and joining. Use this skill whenever the user asks which process should be used for a part under cost, tolerance, volume, and material constraints.
---
# Process Selection
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
select manufacturing route with explicit tradeoffs.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- volume-breakpoint logic
- capability vs tolerance mapping
- tooling and lead-time implications
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/quality-metrology-plan.md
View File

@@ -1,65 +0,0 @@
---
name: quality-metrology-plan
description: Quality control and metrology planning for mechanical parts and assemblies. Use this skill whenever the user asks how to inspect, validate, or control critical characteristics in production.
---
# Quality And Metrology Plan
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
define measurable CTQs and inspection strategy.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- measurement system capability
- sampling and control plan logic
- gauge and datum accessibility
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/reliability-analysis.md
View File

@@ -1,65 +0,0 @@
---
name: reliability-analysis
description: Reliability engineering for mechanical products and systems. Use this skill whenever the user asks about reliability targets, MTBF, warranty risk, mission profiles, or reliability growth plans.
---
# Reliability Analysis
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
quantify reliability and propose risk-reduction plan.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- mission profile decomposition
- series/parallel logic appropriateness
- confidence bounds on predictions
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/shafts-couplings-design.md
View File

@@ -1,65 +0,0 @@
---
name: shafts-couplings-design
description: Shaft and coupling design for torque and alignment demands. Use this skill whenever the user asks about shaft sizing, keyways/splines, critical speed, misalignment, or coupling selection.
---
# Shafts And Couplings Design
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
design shafts and couplings against static, fatigue, and dynamic limits.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- combined loading with stress raisers
- critical speed margin
- connection failure checks
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/should-cost-estimation.md
View File

@@ -1,65 +0,0 @@
---
name: should-cost-estimation
description: Should-cost and cost-driver analysis for mechanical components. Use this skill whenever the user asks for target cost, quote sanity check, supplier negotiation inputs, or cost reduction options.
---
# Should Cost Estimation
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
estimate cost structure and cost-down levers.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- cost model assumptions traceability
- sensitivity to volume/scrap/cycle time
- risk-adjusted ranges
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/spring-design.md
View File

@@ -1,65 +0,0 @@
---
name: spring-design
description: Spring design for force-deflection and life requirements. Use this skill whenever the user asks about coil/leaf/disc spring sizing, stiffness tuning, set relaxation, or cycle life.
---
# Spring Design
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
design springs for force window, envelope, and durability.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- stress correction factors
- solid height and buckling checks
- set and relaxation allowances
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/standards-compliance-check.md
View File

@@ -1,65 +0,0 @@
---
name: standards-compliance-check
description: Engineering standards and compliance guidance for mechanical products. Use this skill whenever the user asks about ISO/EN/ASME/ASTM/API/NACE requirements, legal/contractual compliance checks, certification readiness, or design acceptability against standards, even if standard names are only partially known.
---
# Standards And Compliance Check
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
map requirements to applicable standards and evidence packages.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- normative scope mapping
- mandatory vs optional clauses
- compliance evidence matrix
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/structural-analysis.md
View File

@@ -1,65 +0,0 @@
---
name: structural-analysis
description: Solid mechanics analysis for parts and assemblies under static loads. Use this skill whenever the user asks for stress, strain, deflection, stiffness, load paths, or structural adequacy checks for mechanical components, even if geometry is incomplete.
---
# Structural Analysis
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
evaluate stresses, strains, and stiffness under real load cases.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- equilibrium and boundary conditions
- stress concentration handling
- deflection/serviceability limits
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/technical-report.md
View File

@@ -1,65 +0,0 @@
---
name: technical-report
description: Technical report writing for mechanical engineering deliverables. Use this skill whenever the user needs a clear, professional engineering report with rationale, findings, and recommendations for stakeholders.
---
# Technical Report
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
produce concise, evidence-based engineering reports.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- executive clarity for mixed audiences
- evidence-to-claim traceability
- decision-oriented recommendations
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/test-plan-validation.md
View File

@@ -1,65 +0,0 @@
---
name: test-plan-validation
description: Test planning and validation strategy for mechanical design verification. Use this skill whenever the user asks how to verify requirements, design tests, set acceptance criteria, or plan DV/PV campaigns.
---
# Test Plan Validation
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
build requirement-linked verification plan.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- requirement-to-test traceability
- test severity and representativeness
- pass/fail criteria robustness
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/thermal-analysis.md
View File

@@ -1,65 +0,0 @@
---
name: thermal-analysis
description: Thermal behavior analysis for mechanical systems. Use this skill whenever the user asks about temperatures, heat flux, thermal gradients, cooling, insulation, or thermal sizing of components and assemblies.
---
# Thermal Analysis
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
analyze temperature fields and thermal balances.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- steady vs transient model choice
- boundary heat transfer coefficients
- thermal bottleneck identification
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/thermal-expansion-stress.md
View File

@@ -1,65 +0,0 @@
---
name: thermal-expansion-stress
description: Thermal expansion mismatch and thermal stress assessment. Use this skill whenever the user asks about differential expansion, constrained thermal growth, thermal bowing, or seal/interface thermal issues.
---
# Thermal Expansion And Thermal Stress
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
quantify expansion mismatch and resulting stress risk.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- CTE mismatch mapping
- constraint realism check
- allowance/compensation strategies
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/tolerance-gdt-fits.md
View File

@@ -1,65 +0,0 @@
---
name: tolerance-gdt-fits
description: Tolerance stack-up, GD&T, and fit selection for assemblies. Use this skill whenever the user asks about dimensional variation, datums, interchangeability, fit class, or functional tolerancing.
---
# Tolerance GD&T Fits
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
control variation to ensure assembly function and cost balance.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- datum strategy coherence
- worst-case vs statistical stackup
- measurement feasibility
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

65
mechanical-skills/upload-md/tribology-lubrication.md
View File

@@ -1,65 +0,0 @@
---
name: tribology-lubrication
description: Tribology and lubrication engineering for moving interfaces. Use this skill whenever the user asks about friction, wear, lubrication regime, lubricant choice, surface finish, or seizure/scuffing risk.
---
# Tribology And Lubrication
## Objective
Deliver senior-level mechanical engineering support for this domain with transparent assumptions, standards-aware reasoning, and decision-oriented outputs.
## Focus
optimize contact pair performance and lubricant strategy.
## Required Inputs
Collect and state these inputs before final recommendations:
- Functional objective and acceptance criteria.
- Geometry, interfaces, and boundary conditions.
- Load cases and duty cycle (magnitude, direction, duration, repetitions).
- Material state, manufacturing route, and environment (temperature, corrosion, contamination).
- Applicable standards, customer constraints, and safety expectations.
If data is missing, proceed with bounded assumptions and clearly mark uncertainty impact.
## Workflow
1. Frame the engineering question and define pass/fail metrics.
2. Build a first-principles model and choose methods suitable for the available fidelity.
3. Cross-check with standards, supplier datasheets, and recognized references.
4. Compare at least two options when tradeoffs are relevant.
5. Quantify margins, sensitivities, and residual risks.
6. Conclude with a practical recommendation and next validation step.
## Specialized Checks
Prioritize these checks in the analysis:
- lambda ratio and film regime
- surface roughness compatibility
- contamination and maintenance effects
## Sources Priority
Use and cite sources in this order:
1. Binding standards/codes and contractual requirements.
2. OEM or supplier technical documentation.
3. Peer-reviewed literature and recognized handbooks.
4. Internal lessons learned and field evidence.
When sources disagree, explain which source controls the decision and why.
## Output Format
ALWAYS use this structure:
# Engineering Response
## 1. Problem Framing
## 2. Inputs And Assumptions
## 3. Analysis And Checks
## 4. Design Options And Tradeoffs
## 5. Risks, Failure Modes, And Mitigations
## 6. Recommendation And Next Actions
## 7. Sources Consulted
## Quality Gates
Before finalizing, verify all of the following:
- SI units are consistent and conversions are explicit.
- At least one sanity check exists (order-of-magnitude or handbook benchmark).
- Utilization, margin, or safety factor is reported where applicable.
- Limitations and confidence level are stated.
- Cases requiring human expert sign-off or physical testing are clearly flagged.

332
script/package_skills.py Executable file
View File

@@ -0,0 +1,332 @@
#!/usr/bin/env python3
from __future__ import annotations
import argparse
import re
import shutil
import sys
from dataclasses import dataclass
from datetime import datetime, timezone
from pathlib import Path
from zipfile import ZIP_DEFLATED, ZipFile
EXCLUDED_DIRS = {"evals", "packages", "upload-md", "scripts"}
KEY_VALUE_RE = re.compile(r"^([A-Za-z0-9_-]+)\s*:\s*(.*)\s*$")
@dataclass
class SkillRecord:
source_dir_name: str
source_path: Path
declared_name: str
description: str
package_name: str
def parse_frontmatter(skill_md: Path) -> tuple[str | None, str | None, str | None]:
content = skill_md.read_text(encoding="utf-8")
lines = content.splitlines()
if not lines or lines[0].strip() != "---":
return None, None, "missing YAML frontmatter opening delimiter '---'"
try:
end_idx = lines.index("---", 1)
except ValueError:
return None, None, "missing YAML frontmatter closing delimiter '---'"
yaml_lines = lines[1:end_idx]
values: dict[str, str] = {}
for line in yaml_lines:
match = KEY_VALUE_RE.match(line)
if not match:
continue
key = match.group(1).strip()
value = match.group(2).strip().strip("'\"")
values[key] = value
name = values.get("name")
description = values.get("description")
if not name or not description:
return None, None, "frontmatter must include both 'name' and 'description'"
return name, description, None
def iter_skill_dirs(skills_root: Path) -> list[Path]:
return [
path
for path in sorted(skills_root.iterdir())
if path.is_dir() and path.name not in EXCLUDED_DIRS and not path.name.startswith(".")
]
def ensure_clean_output(output_dir: Path) -> tuple[Path, Path]:
per_skill_dir = output_dir / "per-skill"
bundles_dir = output_dir / "bundles"
if per_skill_dir.exists():
shutil.rmtree(per_skill_dir)
if bundles_dir.exists():
shutil.rmtree(bundles_dir)
per_skill_dir.mkdir(parents=True, exist_ok=True)
bundles_dir.mkdir(parents=True, exist_ok=True)
return per_skill_dir, bundles_dir
def add_directory_to_zip(zip_file: ZipFile, source_dir: Path, arc_prefix: str | None = None) -> None:
for file_path in sorted(source_dir.rglob("*")):
if not file_path.is_file():
continue
relative = file_path.relative_to(source_dir).as_posix()
if arc_prefix:
relative = f"{arc_prefix}/{relative}"
zip_file.write(file_path, relative)
def create_skill_archives(skill: SkillRecord, per_skill_dir: Path) -> tuple[Path, Path]:
skill_file = per_skill_dir / f"{skill.package_name}.skill"
zip_file = per_skill_dir / f"{skill.package_name}.zip"
with ZipFile(skill_file, "w", compression=ZIP_DEFLATED) as zf:
add_directory_to_zip(zf, skill.source_path)
with ZipFile(zip_file, "w", compression=ZIP_DEFLATED) as zf:
add_directory_to_zip(zf, skill.source_path)
return skill_file, zip_file
def validate_archive_contains_skill_md(archive_path: Path) -> tuple[bool, str]:
with ZipFile(archive_path, "r") as zf:
names = set(zf.namelist())
if "SKILL.md" not in names:
return False, f"{archive_path.name}: SKILL.md not found at archive root"
content = zf.read("SKILL.md").decode("utf-8", errors="replace")
if "name:" not in content or "description:" not in content:
return False, f"{archive_path.name}: SKILL.md missing 'name' or 'description'"
return True, f"{archive_path.name}: OK"
def validate_bundle_contains_skills(bundle_path: Path, source_dir_names: list[str]) -> tuple[bool, str]:
with ZipFile(bundle_path, "r") as zf:
entries = zf.namelist()
missing = []
for dir_name in source_dir_names:
prefix = f"{dir_name}/"
if not any(item.startswith(prefix) for item in entries):
missing.append(dir_name)
if missing:
return False, f"bundle missing directories: {', '.join(missing)}"
return True, "bundle contains all valid skill directories"
def build_index(
output_file: Path,
skills_root: Path,
valid_skills: list[SkillRecord],
skipped: list[str],
warnings: list[str],
validations: list[tuple[bool, str]],
bundle_path: Path,
) -> None:
ts = datetime.now(timezone.utc).strftime("%Y-%m-%d %H:%M:%S UTC")
all_ok = all(ok for ok, _ in validations)
lines = [
"# PACKAGES INDEX",
"",
f"- Generated: {ts}",
f"- Skills root: `{skills_root}`",
f"- Valid skills packaged: {len(valid_skills)}",
f"- Package formats: `.skill` + `.zip` (per skill)",
f"- Bundle: `{bundle_path.name}`",
f"- Validation status: {'PASS' if all_ok else 'FAIL'}",
"",
"## Included Skills",
"",
]
for skill in valid_skills:
lines.append(
"- `{name}` (source dir: `{src}`, declared name: `{decl}`)".format(
name=skill.package_name, src=skill.source_dir_name, decl=skill.declared_name
)
)
lines.extend(["", "## Warnings", ""])
if warnings:
lines.extend([f"- {msg}" for msg in warnings])
else:
lines.append("- None")
lines.extend(["", "## Skipped", ""])
if skipped:
lines.extend([f"- {msg}" for msg in skipped])
else:
lines.append("- None")
lines.extend(["", "## Validation", ""])
for ok, message in validations:
lines.append(f"- [{'x' if ok else ' '}] {message}")
lines.extend(["", "## Output Paths", "", "- `packages/per-skill/`", "- `packages/bundles/`"])
output_file.write_text("\n".join(lines) + "\n", encoding="utf-8")
def package_skills(skills_root: Path, output_dir: Path, bundle_name: str, spot_check_count: int) -> int:
per_skill_dir, bundles_dir = ensure_clean_output(output_dir)
skipped: list[str] = []
warnings: list[str] = []
valid_skills: list[SkillRecord] = []
used_names: dict[str, int] = {}
for skill_dir in iter_skill_dirs(skills_root):
skill_md = skill_dir / "SKILL.md"
if not skill_md.exists():
skipped.append(f"{skill_dir.name}: missing SKILL.md")
continue
declared_name, description, error = parse_frontmatter(skill_md)
if error:
skipped.append(f"{skill_dir.name}: {error}")
continue
assert declared_name is not None and description is not None
package_name = declared_name
if declared_name != skill_dir.name:
warnings.append(
f"{skill_dir.name}: declared name '{declared_name}' differs from directory name"
)
if package_name in used_names:
used_names[package_name] += 1
new_name = f"{package_name}-{used_names[package_name]}"
warnings.append(
f"name collision for '{package_name}', renamed package to '{new_name}'"
)
package_name = new_name
else:
used_names[package_name] = 1
valid_skills.append(
SkillRecord(
source_dir_name=skill_dir.name,
source_path=skill_dir,
declared_name=declared_name,
description=description,
package_name=package_name,
)
)
for skill in valid_skills:
create_skill_archives(skill, per_skill_dir)
bundle_path = bundles_dir / bundle_name
with ZipFile(bundle_path, "w", compression=ZIP_DEFLATED) as zf:
for skill in valid_skills:
add_directory_to_zip(zf, skill.source_path, arc_prefix=skill.source_dir_name)
validations: list[tuple[bool, str]] = []
expected = 2 * len(valid_skills)
produced = len(list(per_skill_dir.glob("*.skill"))) + len(list(per_skill_dir.glob("*.zip")))
validations.append(
(
expected == produced,
f"package count check: expected {expected}, found {produced}",
)
)
check_items = valid_skills[: max(0, spot_check_count)]
for skill in check_items:
skill_archive = per_skill_dir / f"{skill.package_name}.skill"
zip_archive = per_skill_dir / f"{skill.package_name}.zip"
validations.append(validate_archive_contains_skill_md(skill_archive))
validations.append(validate_archive_contains_skill_md(zip_archive))
validations.append(
validate_bundle_contains_skills(
bundle_path=bundle_path,
source_dir_names=[record.source_dir_name for record in valid_skills],
)
)
index_path = output_dir / "PACKAGES_INDEX.md"
build_index(
output_file=index_path,
skills_root=skills_root,
valid_skills=valid_skills,
skipped=skipped,
warnings=warnings,
validations=validations,
bundle_path=bundle_path,
)
print(f"Skills root: {skills_root}")
print(f"Valid skills: {len(valid_skills)}")
print(f"Skipped: {len(skipped)}")
print(f"Warnings: {len(warnings)}")
print(f"Per-skill output: {per_skill_dir}")
print(f"Bundle output: {bundle_path}")
print(f"Index: {index_path}")
all_ok = all(ok for ok, _ in validations)
print(f"Validation: {'PASS' if all_ok else 'FAIL'}")
if not all_ok:
for ok, message in validations:
if not ok:
print(f" - {message}")
return 1
return 0
def main() -> int:
repo_root = Path(__file__).resolve().parents[1]
default_skills_root = repo_root / "skill"
parser = argparse.ArgumentParser(
description="Create .skill/.zip import packages for each skill and a collection bundle."
)
parser.add_argument(
"--skills-root",
type=Path,
default=default_skills_root,
help="Path to skill collection root (default: script parent directory).",
)
parser.add_argument(
"--output-dir",
type=Path,
default=None,
help="Output directory (default: <skills-root>/packages).",
)
parser.add_argument(
"--bundle-name",
type=str,
default="mechanical-skills-collection.zip",
help="Filename for the collection bundle.",
)
parser.add_argument(
"--spot-check-count",
type=int,
default=3,
help="How many skills to spot-check for SKILL.md in both archive formats.",
)
args = parser.parse_args()
skills_root = args.skills_root.resolve()
output_dir = (args.output_dir or (skills_root.parent / "package")).resolve()
if not skills_root.exists() or not skills_root.is_dir():
print(f"skills root does not exist or is not a directory: {skills_root}")
return 2
return package_skills(
skills_root=skills_root,
output_dir=output_dir,
bundle_name=args.bundle_name,
spot_check_count=max(0, args.spot_check_count),
)
if __name__ == "__main__":
sys.exit(main())

0
mechanical-skills/SKILLS_INDEX.md → skill/SKILLS_INDEX.md
View File

0
mechanical-skills/bearings-seals-selection/SKILL.md → skill/bearings-seals-selection/SKILL.md
View File

0
mechanical-skills/calculation-report/SKILL.md → skill/calculation-report/SKILL.md
View File

0
mechanical-skills/cnc-sheet-casting-forging/SKILL.md → skill/cnc-sheet-casting-forging/SKILL.md
View File

0
mechanical-skills/design-review-fmea/SKILL.md → skill/design-review-fmea/SKILL.md
View File

0
mechanical-skills/dfm-dfa-review/SKILL.md → skill/dfm-dfa-review/SKILL.md
View File

0
mechanical-skills/dynamics-vibrations-analysis/SKILL.md → skill/dynamics-vibrations-analysis/SKILL.md
View File

0
mechanical-skills/energy-efficiency-analysis/SKILL.md → skill/energy-efficiency-analysis/SKILL.md
View File

0
mechanical-skills/evals/evals.json → skill/evals/evals.json
View File

0
mechanical-skills/failure-root-cause-analysis/SKILL.md → skill/failure-root-cause-analysis/SKILL.md
View File

0
mechanical-skills/fatigue-fracture-analysis/SKILL.md → skill/fatigue-fracture-analysis/SKILL.md
View File

0
mechanical-skills/fea-cfd-review/SKILL.md → skill/fea-cfd-review/SKILL.md
View File

0
mechanical-skills/fluid-analysis/SKILL.md → skill/fluid-analysis/SKILL.md
View File

0
mechanical-skills/gear-design/SKILL.md → skill/gear-design/SKILL.md
View File

0
mechanical-skills/heat-treatment/SKILL.md → skill/heat-treatment/SKILL.md
View File

0
mechanical-skills/joints-design/SKILL.md → skill/joints-design/SKILL.md
View File

0
mechanical-skills/machine-elements-selection/SKILL.md → skill/machine-elements-selection/SKILL.md
View File

0
mechanical-skills/material-failure-modes/SKILL.md → skill/material-failure-modes/SKILL.md
View File

0
mechanical-skills/materials-metallurgy/SKILL.md → skill/materials-metallurgy/SKILL.md
View File

0
mechanical-skills/mechanical-orchestrator/SKILL.md → skill/mechanical-orchestrator/SKILL.md
View File

0
mechanical-skills/modal-analysis/SKILL.md → skill/modal-analysis/SKILL.md
View File

0
mechanical-skills/pressure-loss-pump-piping/SKILL.md → skill/pressure-loss-pump-piping/SKILL.md
View File

0
mechanical-skills/process-selection/SKILL.md → skill/process-selection/SKILL.md
View File

0
mechanical-skills/quality-metrology-plan/SKILL.md → skill/quality-metrology-plan/SKILL.md
View File

0
mechanical-skills/reliability-analysis/SKILL.md → skill/reliability-analysis/SKILL.md
View File

0
mechanical-skills/shafts-couplings-design/SKILL.md → skill/shafts-couplings-design/SKILL.md
View File

0
mechanical-skills/should-cost-estimation/SKILL.md → skill/should-cost-estimation/SKILL.md
View File

0
mechanical-skills/spring-design/SKILL.md → skill/spring-design/SKILL.md
View File

0
mechanical-skills/standards-compliance-check/SKILL.md → skill/standards-compliance-check/SKILL.md
View File

0
mechanical-skills/structural-analysis/SKILL.md → skill/structural-analysis/SKILL.md
View File

0
mechanical-skills/technical-report/SKILL.md → skill/technical-report/SKILL.md
View File

0
mechanical-skills/test-plan-validation/SKILL.md → skill/test-plan-validation/SKILL.md
View File

0
mechanical-skills/thermal-analysis/SKILL.md → skill/thermal-analysis/SKILL.md
View File

0
mechanical-skills/thermal-expansion-stress/SKILL.md → skill/thermal-expansion-stress/SKILL.md
View File

0
mechanical-skills/tolerance-gdt-fits/SKILL.md → skill/tolerance-gdt-fits/SKILL.md
View File

0
mechanical-skills/tribology-lubrication/SKILL.md → skill/tribology-lubrication/SKILL.md
View File