conda-env-manager

Plan, create, and manage conda environments with dry-run previews and logging.

78|3|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/CUHK-AIM-Group/NeuroClaw --skill conda-env-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conda-env-manager
Source: https://github.com/CUHK-AIM-Group/NeuroClaw/tree/main/skills/conda-env-manager
Command: npx skills add https://github.com/CUHK-AIM-Group/NeuroClaw --skill conda-env-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conda environments are central to reproducible ML workflows, but managing them safely and without touching the base system is error-prone. This skill provides a guided, safe, and auditable way to plan, create, export, clone, update, remove, and activate environments, enforcing best practices and reproducibility across projects.

Core Features & Use Cases

  • Isolated lifecycle management: create, export, update, clone, remove, list, and activate environments without modifying the base.
  • Reproducibility and auditing: export environment.yml, maintain versioned metadata, and log actions for team sharing.
  • Safe execution workflow: dry-run previews, explicit user confirmation, and automated validation before applying changes.

Quick Start

Create a new isolated conda environment for your project and export its specification to environment.yml.

Frequently Asked Questions about conda-env-manager

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

FAQPage Schema
How do I create isolated conda environments without modifying the base system?

Conda environment creation isolates dependencies without touching the base system. You get dry-run previews, explicit confirmation prompts, and automated validation before applying changes.

What is the best way to export conda environment specs for team reproducibility?

Exporting conda environments generates an environment.yml file with versioned metadata. This ensures reproducibility and team sharing by logging actions and maintaining auditable specs.

Can I clone and update conda environments safely across different projects?

Cloning and updating conda environments is handled through a strict workflow with dry-run previews. Explicit user confirmation is enforced before applying any environment modifications.

How do I manage the full lifecycle of conda environments for local workflows?

Managing conda environments covers creating, exporting, updating, cloning, removing, listing, and activating. It enforces best practices and reproducibility metadata across local and team workflows.

Does conda environment management support dry-run previews before applying changes?

Dry-run previews are a core feature of conda environment management. They validate changes and require explicit user confirmation before any modification is applied to the environment.