modernize-scientific-stack

Converts Python 2 scientific code to Python 3 using modern libraries.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Lilwenz/Geometry-Informed-Dual-Adaptive --skill modernize-scientific-stack-lilwenz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: modernize-scientific-stack
Source: https://github.com/Lilwenz/Geometry-Informed-Dual-Adaptive/tree/main/.agents/skills/modernize-scientific-stack
Command: npx skills add https://github.com/Lilwenz/Geometry-Informed-Dual-Adaptive --skill modernize-scientific-stack-lilwenz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps convert legacy Python 2 scientific computing code to Python 3 using modern libraries, reducing compatibility risk and enabling continued maintenance.

Core Features & Use Cases

  • Complete code discovery and dependency mapping for scientific scripts.
  • Phase-driven migration plan that updates file handling to UTF-8 and uses pathlib, replacing older patterns.
  • Implementation strategy focusing on reproducibility, verification, and documentation.

Quick Start

Provide a migration plan for a given Python 2 scientific script to Python 3, detailing encoding, path handling with pathlib, and data processing with pandas.

Frequently Asked Questions about modernize-scientific-stack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate legacy Python 2 scientific computing scripts to Python 3?▼

Migrate Python 2 scientific computing scripts to Python 3 by mapping dependencies, updating file handling to UTF-8 encoding, replacing legacy paths with pathlib, and modernizing pandas and numpy usage through a phase-driven plan.

What is the best way to modernize pandas and numpy code during a Python 3 migration?▼

Modernize pandas and numpy code by applying a phase-driven migration plan that replaces deprecated patterns, enforces UTF-8 encoding, and validates data processing changes through a reproducible verification protocol.

Does this Python 3 migration approach enforce UTF-8 encoding and pathlib for file handling?▼

Yes, this Python 3 migration approach enforces UTF-8 encoding for file handling and replaces legacy path patterns with pathlib to ensure reproducible data processing and numerical analysis scripts.

Can I use this migration plan for data processing and numerical analysis scripts?▼

Yes, you can use this migration plan for data processing and numerical analysis scripts, as it includes complete code discovery, dependency mapping, and a verification protocol tailored for scientific computing.

What are the limitations when converting legacy scientific code to Python 3?▼

Converting legacy scientific code to Python 3 requires careful dependency mapping and validation, as limitations arise from deprecated library patterns in pandas and numpy that must be verified through a reproducible testing protocol.

Why does my legacy Python 2 scientific code need pathlib and UTF-8 updates?▼

Legacy Python 2 scientific code needs pathlib and UTF-8 updates to reduce compatibility risk and enable continued maintenance, replacing older file handling patterns with modern Python 3 standards for reproducible scientific computing.