python-env-setup
Python environment setup — conda/miniconda installation, environment creation, mirror configuration, and activation patterns.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Python environment setup — conda/miniconda installation, environment creation, mirror configuration, and activation patterns.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Integration testing for AI Agent CLI systems — PTY-driven conversation simulation, tool chain verification, OpenSpec-driven test design, and real-API validation.
Extract web article content from WeChat MP, blogs, and other platforms, converting text, images, formatting, and tables to clean Markdown.
Configure, extend, or contribute to Hermes Agent.
Generate images, video, and audio with ComfyUI — install, launch, manage nodes/models, run workflows with parameter injection. Uses the official comfy-cli for lifecycle and direct REST/WebSocket API for execution.
Decomposition playbook + anti-temptation rules for an orchestrator profile routing work through Kanban. The "don't do the work yourself" rule and the basic lifecycle are auto-injected into every kanban worker's system prompt; this skill is the deeper playbook when you're specifically playing the orchestrator role.
Pitfalls, examples, and edge cases for Hermes Kanban workers. The lifecycle itself is auto-injected into every worker's system prompt as KANBAN_GUIDANCE (from agent/prompt_builder.py); this skill is what you load when you want deeper detail on specific scenarios.
| name | python-env-setup |
| description | Python environment setup — conda/miniconda installation, environment creation, mirror configuration, and activation patterns. |
| tags | ["setup","python","conda","miniconda","environment","mirrors"] |
Conda-based Python environment provisioning: install Miniconda, create environments, configure mirrors, and handle activation in scripted contexts.
conda or python commands fail with "command not found"# Download installer
cd /tmp && curl -fsSL -o miniconda.sh https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh
# Silent install to ~/miniconda3
bash /tmp/miniconda.sh -b -p $HOME/miniconda3
# Initialize for bash
~/miniconda3/bin/conda init bash
# Accept Terms of Service (conda 26.x+) — REQUIRED before creating environments
conda tos accept --override-channels --channel https://repo.anaconda.com/pkgs/main
conda tos accept --override-channels --channel https://repo.anaconda.com/pkgs/r
# Activate conda in the current shell (non-login / scripted context)
eval "$($HOME/miniconda3/bin/conda shell.bash hook)"
# Create environment
conda create -y -n <env_name> python=<version>
# Verify
conda activate <env_name> && python --version && which python
conda activate does NOT work in non-login shells even after conda init bash. Always use:
eval "$($HOME/miniconda3/bin/conda shell.bash hook)" && conda activate <env_name>
This is the pattern for all scripted terminal commands — source ~/.bashrc is unreliable in non-interactive contexts.
conda config --set show_channel_urls yes
conda config --add channels https://mirrors.tuna.tsinghua.edu.cn/anaconda/pkgs/main/
conda config --add channels https://mirrors.tuna.tsinghua.edu.cn/anaconda/pkgs/free/
conda config --add channels https://mirrors.tuna.tsinghua.edu.cn/anaconda/cloud/conda-forge/
mkdir -p ~/.config/pip
cat > ~/.config/pip/pip.conf << 'EOF'
[global]
index-url = https://pypi.tuna.tsinghua.edu.cn/simple
trusted-host = pypi.tuna.tsinghua.edu.cn
EOF
Conda 26+ requires explicit Terms of Service acceptance before conda create works. Without it, the command prints a TOS message and exits — the environment is NOT created, but the exit code may still be 0. Always run conda tos accept for both pkgs/main and pkgs/r channels first.
conda init bash modifies ~/.bashrc, but that file is only sourced in interactive login shells. In non-interactive contexts (background processes, subshells, CI), use the eval "$(conda shell.bash hook)" pattern. source ~/.bashrc in a script is unreliable because many .bashrc files have early return/exit guards for non-interactive shells.
Conda uses channels in reverse order of addition (last added = highest priority). Add conda-forge last if you want it to take priority over pkgs/main. For most users, the default priority order (main → free → conda-forge) is fine.