abaqus-job
About
This skill creates, submits, and monitors Abaqus analysis jobs, including generating input (.inp) files and running parallel executions. Use it when a model is complete and a user requests to run, submit, or check the status of an analysis. It requires a saved .cae file and uses specific Abaqus commands via a Bash tool.
Quick Install
Claude Code
Recommended/plugin add https://github.com/majiayu000/claude-skill-registrygit clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/abaqus-jobCopy and paste this command in Claude Code to install this skill
Documentation
Abaqus Job Skill
This skill creates, submits, and monitors Abaqus analysis jobs. Use it when the model is ready to run.
When to Use This Skill
Route here when user says:
- "Run the analysis", "Submit the job", "Execute the model"
- "Generate input file", "Create INP file"
- "Run in parallel", "Check job status"
Route elsewhere:
- Reading results after completion →
/abaqus-odb - Setting up the model → use other module skills
Prerequisites
Before job submission:
- Model is complete (geometry, material, mesh, BCs, loads, step)
- Model saved to .cae file
- No validation errors
Workflow: Running an Analysis
Step 1: Save the Model
Always save before creating a job. The .cae file must exist.
Step 2: Create the Job
Specify job name and model name. They can differ.
Step 3: Choose Submission Mode
| 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 |
Step 4: Wait and Monitor
For interactive submission, monitor status until COMPLETED or ABORTED.
Step 5: Check Results
If COMPLETED, results are in .odb file. If ABORTED, check .msg file.
Key Decisions
Submit vs Write Input?
| Goal | Method |
|---|---|
| Run analysis now | submit() |
| Only create INP file | writeInput() |
| Run later from CLI | writeInput, then abaqus job=Name |
Parallel Processing
| 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 |
What to Ask User
If unclear, ask:
- "Ready to run the analysis?"
- "How many CPUs for parallel?"
- "Just need the input file, or run the analysis?"
Output Files
| 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) |
Troubleshooting
| 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 |
Validation Checklist
Before submitting:
- Model saved (.cae exists)
- Job name specified
- Model name matches saved model
- CPUs set appropriately
Code Patterns
For API syntax and code examples, see:
GitHub Repository
Related Skills
algorithmic-art
MetaThis Claude Skill creates original algorithmic art using p5.js with seeded randomness and interactive parameters. It generates .md files for algorithmic philosophies, plus .html and .js files for interactive generative art implementations. Use it when developers need to create flow fields, particle systems, or other computational art while avoiding copyright issues.
subagent-driven-development
DevelopmentThis skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.
executing-plans
DesignUse the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.
cost-optimization
OtherThis Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.
