Agent skill

Python Env

Create and maintain Python environments and dependencies with uv.

MITAuto-check passed

Install Python Env

skills CLI

$ npx skills add flonat/flonat-research --skill python-env -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research python-env --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/python-env .claude/skills/python-env && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "python-env" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/python-env into .claude/skills/python-env/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-env", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/flonat/flonat-research/tree/main/skills/python-env

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add flonat/flonat-research --skill python-env -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research python-env --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/python-env .agents/skills/python-env && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "python-env" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/python-env into .agents/skills/python-env/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-env", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add flonat/flonat-research --skill python-env -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research python-env --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/python-env .cursor/skills/python-env && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "python-env" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/python-env into .cursor/skills/python-env/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-env", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/flonat/flonat-research.git --path skills/python-env

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add flonat/flonat-research --skill python-env -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research python-env --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/python-env .gemini/skills/python-env && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "python-env" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/python-env into .gemini/skills/python-env/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-env", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install flonat/flonat-research python-env

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add flonat/flonat-research --skill python-env -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/python-env .github/skills/python-env && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "python-env" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/python-env into .github/skills/python-env/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-env", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add flonat/flonat-research --skill python-env -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research python-env --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/python-env .opencode/skills/python-env && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "python-env" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/python-env into .opencode/skills/python-env/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "python-env", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: python-env
GitHub stars: 145
Token cost: ~558 tokens
SKILL.md length: 228 words
Files: 1
Skills in repo: 83
Repo updated: Sep 29, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Create and maintain Python environments and dependencies with uv.

Works in 4 steps: Never use pip install — always uv pip… → Never install globally — use uv tool… → Always work in a venv — created by uv… → …
Installing packages
SKILL.md covers Golden Rule, Commands, Project Setup and Rules, plus 2 more sections
Calls uv and pip

What it does

Python Env is an agent skill from flonat/flonat-research. Create and maintain Python environments and dependencies with uv. Use when installing packages, creating a virtual environment, resolving Python dependency state, or migrating away from pip. Not for general Python coding.

Its SKILL.md is about 560 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Python. The repository describes itself as: Shareable Claude Code + Codex infrastructure for PhD researchers — skills, agents, hooks, and rules for academic workflows. The licence is MIT.

When your agent uses it

Installing packages
Creating a virtual environment
Resolving Python dependency state
Migrating away from pip

Example prompts

“/python-env”

Requirements

Python 3
Pre-approved tools (allowed-tools): Bash(uv*), Bash(uv:*), Bash(mkdir*), Bash(ls*)

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Never use pip install — always uv pip install or uv add
Never install globally — use uv tool install for CLI tools
Always work in a venv — created by uv venv or uv sync
Use uv run — to execute scripts within the project environment

What it can do on your machine

Read from SKILL.md and the folder at commit da27600. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash(uv*)
- Bash(uv:*)
- Bash(mkdir*)
- Bash(ls*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- uv
- pip
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv and pip, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Python Env loads about 558 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 228 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~58
When it runs · the whole SKILL.md, loaded when a task matches: ~558

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from flonat/flonat-research at commit da27600, republished under its MIT licence (© flonat). 228 words, ~558 tokens.

Download SKILL.mdSave it as .claude/skills/python-env/SKILL.md (or your agent's skills folder).

name: python-env
description: Create and maintain Python environments and dependencies with uv. Use when installing packages, creating a virtual environment, resolving Python dependency state, or migrating away from pip. Not for general Python coding.
allowed-tools: Bash(uv*), Bash(uv:*), Bash(mkdir*), Bash(ls*)

Python Environment Management

CRITICAL RULE: Never use pip directly. Always use uv. This applies to all Python package management.

Golden Rule

ALWAYS use uv for Python package and environment management. Never use pip directly.

Commands

Task	Command
Create venv	`uv venv`
Install package	`uv pip install <package>`
Install from requirements	`uv pip install -r requirements.txt`
Run script in project	`uv run python script.py`
Run with dependencies	`uv run --with pandas python script.py`
Install CLI tool globally	`uv tool install <tool>`
Sync project deps	`uv sync`
Add dependency	`uv add <package>`

Project Setup

For new projects:

bash

uv init
uv add <dependencies>
uv sync

For existing projects with pyproject.toml:

bash

uv sync
uv run python main.py

Rules

Never use pip install — always uv pip install or uv add
Never install globally — use uv tool install for CLI tools
Always work in a venv — created by uv venv or uv sync
Use uv run — to execute scripts within the project environment

Typical Project

For a project with a Python entry point:

bash

cd <project>
uv sync                           # Install dependencies
uv run python scripts/task.py     # Run a project script

On [HPC cluster] HPC

[HPC cluster] uses Miniconda3 + Lmod (not uv) because cluster users need to compose with module load CUDA/12.6.0 and other pre-built modules. The project-specific pattern is hpc/env-setup.sh (conda create + pip install) — see docs/guides/hpc.md and reference implementations under Projects/NLP/{example-project-a,example-project-b}/hpc/env-setup.sh. The local dev env still uses uv; HPC gets its own conda env with identical pins. Don't try to port uv to [HPC cluster] — the module system assumes conda.

Files

Just SKILL.md in skills/python-env of flonat/flonat-research.

Open the folder on GitHubat commit da27600

Compare with similar skills

Python Env next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Python Env compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Python Env this skillflonat/flonat-research	145	—	~558	Automated safety check: Pass	MIT	8 days ago
MCP Server Builderanthropics/skills	180k	62 repos	~2.3k	Automated safety check: Pass	Apache-2.0	2 days ago
PDF Processinganthropics/skills	180k	48 repos	~2k	Automated safety check: Pass	Proprietary	2 days ago
NotebookLM Research AssistantPleasePrompto/notebooklm-skill	7.8k	13 repos	~2.4k	Automated safety check: Notes	MIT	27 days ago
Manim Video Productionbrowser-use/video-use	28k	6 repos	~3k	Automated safety check: Pass	MIT	5 days ago
Code Review ChecklistshareAI-lab/learn-claude-code	78k	5 repos	~1.1k	Automated safety check: Pass	MIT	9 days ago

Similar skills

MCP Server Builder
anthropics/skills
Official
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
180k GitHub starsUsed in 62 repos~2.3k tokens
Agent WorkflowsAuto-check passed
PDF Processing
anthropics/skills
Official
Handles everyday PDF jobs in Python and on the command line: extract text and tables, merge, split, rotate, watermark, fill forms, encrypt and OCR.
180k GitHub starsUsed in 48 repos~2k tokens
Documents & OfficeAuto-check passed
NotebookLM Research Assistant
PleasePrompto/notebooklm-skill
Lets Claude Code ask questions of your Google NotebookLM notebooks through browser automation and return answers grounded in your uploaded sources.
7.8k GitHub starsUsed in 13 repos~2.4k tokens
Knowledge ManagementAuto-check: notes
Manim Video Production
browser-use/video-use
Produces math and technical explainer videos with Manim Community Edition: concept animations, equation derivations, algorithm walkthroughs and data stories.
28k GitHub starsUsed in 6 repos~3k tokens
Media & CreativeAuto-check passed
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
78k GitHub starsUsed in 5 repos~1.1k tokens
DevelopmentAuto-check passed
PPT Master
hugohe3/ppt-master
Generates editable PowerPoint decks, rebuilds slides from images, fills .pptx templates and polishes existing presentations through routed workflows.
58k GitHub starsUsed in 1 repo~2.5k tokens
Documents & OfficeAuto-check passed

More from flonat/flonat-research

All 83 skills in this repo

Latex Posters
flonat/flonat-research
Create a large-format academic poster in LaTeX using beamerposter, tikzposter, or baposter.
145 GitHub stars~1.5k tokensUpdated 8 days ago
Auto-check: notes
Skill Creator
flonat/flonat-research
Create, revise, and evaluate reusable AI workflow skills, including trigger-quality tests.
145 GitHub stars~4.4k tokensUpdated 8 days ago
Auto-check passed
DOCX
flonat/flonat-research
Create, read, edit, or convert Microsoft Word documents while preserving professional document structure.
145 GitHub stars~1.2k tokensUpdated 8 days ago
Auto-check passed
PDF
flonat/flonat-research
Read, create, combine, split, rotate, OCR, watermark, secure, or extract content from PDF files.
145 GitHub stars~488 tokensUpdated 8 days ago
Auto-check passed
Init Project Orchestration
flonat/flonat-research
Create or migrate project-level agents, repeatable project workflows, and planning state from one client-neutral contract, then render repository-scoped adapters for both Claude Code and Codex.
145 GitHub stars~1.6k tokensUpdated 8 days ago
Auto-check passed
Pre Commit Audit
flonat/flonat-research
Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers.
145 GitHub stars~2.8k tokensUpdated 8 days ago
Auto-check: notes

Works with

Python

Questions about Python Env

What does Python Env do?

Create and maintain Python environments and dependencies with uv. Python Env is an agent skill from flonat/flonat-research. Create and maintain Python environments and dependencies with uv.

When should I use Python Env?

Python Env fits situations like: installing packages; creating a virtual environment; resolving Python dependency state; migrating away from pip.

How do I install Python Env in Claude Code?

Run `npx skills add flonat/flonat-research --skill python-env -a claude-code`. Or copy the skill folder (skills/python-env in flonat/flonat-research) into .claude/skills/python-env in your project. Claude Code loads it when a task matches its description.

How do I install Python Env in Codex?

Run `npx skills add flonat/flonat-research --skill python-env -a codex`. Or copy the skill folder (skills/python-env in flonat/flonat-research) into .agents/skills/python-env in your project. Codex loads it when a task matches its description.

Can I use Python Env in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add flonat/flonat-research --skill python-env -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/python-env, .gemini/skills/python-env, .github/skills/python-env and .opencode/skills/python-env in your project.

What does Python Env need to run?

Going by SKILL.md and its folder, Python Env needs the command-line tools its instructions call (uv and pip). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Bash(uv*), Bash(uv:*), Bash(mkdir*), Bash(ls*).

Does Python Env access the network?

SKILL.md contains no URLs. Its commands use uv and pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Python Env safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Python Env use?

Python Env is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Python Env use?

About 558 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Python Env?

Skills that share tags, products or a category with Python Env: MCP Server Builder (anthropics/skills, 180k stars), PDF Processing (anthropics/skills, 180k stars), NotebookLM Research Assistant (PleasePrompto/notebooklm-skill, 7.8k stars) and Manim Video Production (browser-use/video-use, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Python Env?

flonat (a GitHub user) maintains it in flonat/flonat-research, which has 145 GitHub stars. The repository holds 83 skills in this directory. The repository was last updated on September 29, 2026.

Source: flonat/flonat-research on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Python Env

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Python Environment Management

Golden Rule

Commands

Project Setup

Rules

Typical Project

On [HPC cluster] HPC

Files

Compare with similar skills

Similar skills

More from flonat/flonat-research

Related

Questions about Python Env