paraview-interface-cli-execution

Sub-skill of paraview-interface: CLI Execution (+3).

5 stars

Best use case

paraview-interface-cli-execution is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Sub-skill of paraview-interface: CLI Execution (+3).

Teams using paraview-interface-cli-execution 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

$curl -o ~/.claude/skills/cli-execution/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/_archive/engineering/cfd/paraview/cli-execution/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/cli-execution/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How paraview-interface-cli-execution Compares

Feature / Agent	paraview-interface-cli-execution	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?

Sub-skill of paraview-interface: CLI Execution (+3).

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

# CLI Execution (+3)

## CLI Execution


```bash
# Run ParaView Python script (with GUI libraries, offscreen)
pvpython script.py

# Run in pure batch mode (no GUI libraries needed)
pvbatch script.py

# Parallel execution with MPI
mpirun -np 4 pvbatch script.py

# With offscreen rendering (mesa)
pvbatch --force-offscreen-rendering script.py

# Specify specific mesa/EGL
DISPLAY=:0 pvpython script.py
```


## pvpython vs pvbatch


| Feature | pvpython | pvbatch |
|---------|----------|---------|
| GUI available | Yes (can show windows) | No (headless only) |
| MPI parallel | No | Yes |
| Offscreen | Via `--force-offscreen-rendering` | Default |
| Use case | Interactive scripts, debugging | Production batch jobs |


## CLI Flags


| Flag | Purpose |
|------|---------|
| `--force-offscreen-rendering` | Force offscreen (no display needed) |
| `--mesa` | Use Mesa software rendering |
| `-dr` | Disable registry (ignore saved settings) |
| `--state=file.pvsm` | Load ParaView state file |
| `--data=file.vtk` | Load data file |


## Environment Setup


```bash
# Typical ParaView environment (installed via package manager)
export PATH=/usr/bin:$PATH  # pvpython, pvbatch in standard path

# Or from tarball installation
export PARAVIEW_HOME=/opt/ParaView-5.12
export PATH=$PARAVIEW_HOME/bin:$PATH
export LD_LIBRARY_PATH=$PARAVIEW_HOME/lib:$LD_LIBRARY_PATH
```

Related Skills

digitalmodel-worktree-test-execution-with-shared-venv

from vamseeachanta/workspace-hub

Run digitalmodel tests from isolated worktrees without uv editable-dependency failures by using the main repo's existing virtualenv and PYTHONPATH.

plan-gated-issue-execution-wave

from vamseeachanta/workspace-hub

Execute a multi-issue architecture/planning wave in a plan-gated repo, then safely transition approved issues into implementation with file-based Codex prompts, local approval markers, subprocess monitoring, and cleanup handling for sandbox/hook edge cases.

work-around-merge-conflicts-in-test-execution

from vamseeachanta/workspace-hub

Run tests when repo has unresolved merge conflicts in config files by bypassing broken configs and executing tests directly

wave-based-parallel-plan-execution

from vamseeachanta/workspace-hub

Orchestrate phase execution by discovering dependencies, grouping into waves, spawning subagents, and collecting results with optional wave filtering

plan-governance-vs-execution-boundary-for-adversarial-review

from vamseeachanta/workspace-hub

Keep stale-approval/governance remediation out of execution-path pseudocode, TDD, files-to-change, and deliverable acceptance when hardening a GitHub issue plan under adversarial review.

interactive-issue-execution-worktree-guardrails

from vamseeachanta/workspace-hub

Execute approved GitHub issues in isolated worktrees with interactive Codex/Codex runs, while containing agent drift and salvaging progress when provider/runtime problems occur.

gtm-prospect-pipeline-phased-execution

from vamseeachanta/workspace-hub

Phased execution pattern for

workspace-hub-batch-issue-execution

from vamseeachanta/workspace-hub

Deprecated alias for gh-work-execution.

gh-work-execution

from vamseeachanta/workspace-hub

Canonical GitHub issue execution route after plan approval — strengthened resource intelligence, TDD-first implementation, targeted validation, adversarial review, delegation controls for Codex agent teams, GitHub progress posting, future-issue capture, and commit/push with closeout discipline.

gh-work-execution-checklist

from vamseeachanta/workspace-hub

Compact live-execution checklist companion for approved GitHub issue work. Use during active implementation as a fast operational route; gh-work-execution remains the canonical source of truth.

aqwa-batch-execution

from vamseeachanta/workspace-hub

Run ANSYS AQWA analyses in batch/headless mode on Linux. Covers CLI execution, DAT input file structure, multi-stage analysis chaining, output file parsing, failure diagnosis, and HPC job scheduling.

blender-interface

from vamseeachanta/workspace-hub

AI interface skill for Blender 3D — headless CLI execution, Python bpy API, mesh import/export, rendering, and integration with engineering analysis workflows.