Agent skill · Data & Analytics

post-processing

Extract, analyze, and visualize simulation output data. Use for field extraction, time series analysis, line profiles, statistical summaries, derived quantity computation, result comparison to references, and automated report generation from simulation results.

FreedomIntelligencegithub.com/FreedomIntelligenceGitHub ↗
claude-codecan modify filesships scripts
Install
npx skills add FreedomIntelligence/OpenClaw-Medical-Skills --skill post-processing --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 12
SKILL.md size: 9 KB
Bundled scripts: yes
Allowed tools: ReadBashWriteGrepGlob
Path: skills/post-processing/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,909
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Post-Processing Skill Analyze and extract meaningful information from simulation output data. ## Goal Transform raw simulation output into actionable insights through field extraction, statistical analysis, derived quantities, visualizations, and comparison with reference data. ## Inputs to Gather Before running post-processing scripts, collect: 1. **Output Data Location** - Path to simulation output files (JSON, CSV, HDF5, VTK) - Time step/snapshot indices of interest - Field names to extract 2. **Analysis Type** - Field extraction (spatial data at specific times) - Time series (temporal evolution of quantities) - Line profiles (1D cuts through domain) - Statistical summary (mean, std, distributions) - Derived quantities (gradients, integrals, fluxes) - Comparison to reference data 3. **Output Requirements** - Output format (JSON, CSV, tabular) - Visualization needs - Report format ## Scripts | Script | Purpose | Key Inputs | |--------|---------|------------| | `field_extractor.py` | Extract field data from output files | --input, --field, --timestep | | `time_series_analyzer.py` | Analyze temporal evolution | --input, --quantity, --window | | `profile_extractor.py` | Extract li

What's inside
Steps it walks through
  1. Goal
  2. Inputs to Gather
  3. Scripts
  4. Workflow
  5. 1. Data Inventory
  6. 2. Field Extraction
  7. 3. Time Series Analysis
  8. 4. Line Profile Extraction
  9. 5. Statistical Analysis
  10. 6. Derived Quantities
  11. 7. Comparison with Reference
  12. 8. Report Generation
  13. Typical Post-Processing Pipeline
  14. Interpretation Guidelines
Ships with 11 files
  • references/comparison_metrics.md
  • references/data_formats.md
  • references/derived_quantities_guide.md
  • references/statistical_methods.md
  • scripts/comparison_tool.py
  • scripts/derived_quantities.py
  • scripts/field_extractor.py
  • scripts/profile_extractor.py
  • scripts/report_generator.py
  • scripts/statistical_analyzer.py
  • scripts/time_series_analyzer.py
Commands it runs
List available fields and timesteps
python scripts/field_extractor.py --input results/ --list --json
Extract concentration field at timestep 100
python scripts/field_extractor.py \
Extract multiple fields
Extract total energy vs time
python scripts/time_series_analyzer.py \
Compute moving average with window
Detect steady state
Extract profile along x-axis at y=0.5
More from OpenClaw-Medical-Skills
All skills →
About this skill
What does the post-processing skill do?

Extract, analyze, and visualize simulation output data. Use for field extraction, time series analysis, line profiles, statistical summaries, derived quantity computation, result comparison to references, and automated report generation from simulation results.

How do I install it?

Run `npx skills add FreedomIntelligence/OpenClaw-Medical-Skills --skill post-processing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From FreedomIntelligence/OpenClaw-Medical-Skills, a repository with 2,909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going