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.
Best use case
abaqus-job is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create and manage Abaqus jobs. Use when user asks to run the analysis, submit the job, execute the model, or generate input file.
Teams using abaqus-job should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/abaqus-job/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How abaqus-job Compares
| Feature / Agent | abaqus-job | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create and manage Abaqus jobs. Use when user asks to run the analysis, submit the job, execute the model, or generate input file.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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: 1. Model is complete (geometry, material, mesh, BCs, loads, step) 2. Model saved to .cae file 3. 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: - [API Quick Reference](references/api-quick-ref.md) - [Common Patterns](references/common-patterns.md) - [Troubleshooting Guide](references/troubleshooting.md)
Related Skills
abaqus-topology-optimization
Complete workflow for topology optimization using Tosca. Use to minimize weight while maintaining stiffness. Requires full Abaqus license (not Learning Edition).
abaqus-thermal-analysis
Complete workflow for heat transfer analysis - steady-state and transient thermal. Use when user asks about temperature distribution, conduction, convection, or heat flow.
abaqus-optimization
Configure Tosca optimization. Use when user mentions design response, objective function, optimization constraint, or SIMP penalty. Base module for topology/shape optimization.
abaqus-geometry
Create and manipulate Abaqus geometry - parts, sketches, extrusions, CAD import. Use for any geometry creation task including box, cylinder, or STEP/IGES import.
abaqus-material
Define material properties for FEA models. Use when user mentions steel, aluminum, Young's modulus, elastic, plastic, density, or asks about material properties.
abaqus-bc
Define boundary conditions - fixed supports, displacements, symmetry. Use when user mentions fixed, pinned, clamped, supported, or constrained. Does NOT handle loads or forces.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
cc-routine-and-class-design
Evaluate routine and class design quality using Code Complete checklists (43 items). Use when designing routines or classes, reviewing class interfaces, choosing between inheritance and containment, or evaluating routine cohesion. Also trigger when tempted to use inheritance as a quick fix under deadline pressure, or when rationalizing 'but it works' for code with deep inheritance or many parameters. Produce severity-tagged reviews (VIOLATION/WARNING/PASS) in CHECKER mode or design decisions in APPLIER mode. Symptoms: vague routine names, >7 parameters, deep inheritance, mixed abstraction levels.
cc-get-session-id
Get the current Claude Code session ID. Use when you need to reference or display the session ID.
canvas
Spawn interactive terminal TUI components (calendars, documents, flight bookings) with real-time IPC communication. Display rich content and collect user selections in tmux split panes.
canvas-design
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create ...
canva-branded-presentation
Create on-brand Canva presentations from an outline or brief. Use when the user asks to create a branded presentation, make an on-brand deck, turn an outline into slides, or generate a presentation from a brief. Input can be text directly in the message, a reference to a Canva doc by name, or a Canva design link (e.g., https://www.canva.com/design/...).