ワンクリックで
abaqus-job
Create and manage Abaqus jobs. Use when user asks to run the analysis, submit the job, execute the model, or generate input file.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Create and manage Abaqus jobs. Use when user asks to run the analysis, submit the job, execute the model, or generate input file.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Define time-varying amplitudes. Use when user mentions ramp, time-varying, cyclic, pulse, or gradually increasing loads. Does NOT handle static constant loads.
Analyze multi-body contact. Use when user mentions parts touching, friction between surfaces, bolt-plate contact, press fit, or assembly with contact.
Complete workflow for coupled thermomechanical analysis. Use when user mentions thermal stress, thermal expansion, or temperature causing deformation.
Download and manage abqpy API documentation. Use when user asks about API documentation, API reference, or downloading Abaqus docs.
Complete workflow for dynamic analysis. Use when user mentions impact, crash, drop test, transient, or time-varying response. Handles explicit and implicit dynamics.
Workflow for fatigue and durability analysis - cycle counting, damage accumulation, and fatigue life prediction.
| name | abaqus-job |
| description | Create and manage Abaqus jobs. Use when user asks to run the analysis, submit the job, execute the model, or generate input file. |
| allowed-tools | ["Read","Write","Edit","Glob","Grep","Bash(abaqus:*)"] |
This skill creates, submits, and monitors Abaqus analysis jobs. Use it when the model is ready to run.
Route here when user says:
Route elsewhere:
/abaqus-odbBefore job submission:
Always save before creating a job. The .cae file must exist.
Specify job name and model name. They can differ.
| User Wants | Action |
|---|---|
| Run analysis and wait | Submit with waitForCompletion |
| Generate INP only (no run) | writeInput |
| Run in background | Submit without waiting |
| Run from command line | abaqus job=Name interactive |
For interactive submission, monitor status until COMPLETED or ABORTED.
If COMPLETED, results are in .odb file. If ABORTED, check .msg file.
| Goal | Method |
|---|---|
| Run analysis now | submit() |
| Only create INP file | writeInput() |
| Run later from CLI | writeInput, then abaqus job=Name |
| Scenario | Setting |
|---|---|
| Small model / Learning Edition | numCpus=1 |
| Large model, multi-core | numCpus=N, numDomains=N |
| Single machine | mp_mode=THREADS |
| Cluster | mp_mode=MPI |
If unclear, ask:
| Extension | Content |
|---|---|
| .odb | Results database (use /abaqus-odb to read) |
| .dat | Printed output (nodal values, summaries) |
| .msg | Solver messages - check this if job fails |
| .sta | Status file (increment progress) |
| .inp | Input file (model definition) |
| .lck | Lock file (exists while job runs) |
| Status/Error | Meaning | Solution |
|---|---|---|
| COMPLETED | Success | Proceed to /abaqus-odb |
| ABORTED | Failed | Check .msg file for error |
| License not available | No tokens | Wait or check license server |
| Memory error | Model too large | Increase memory or coarsen mesh |
| .lck file exists | Stale lock | Delete if job is not running |
Before submitting:
For API syntax and code examples, see: