manage-pyapp-venv
Skill203 starsChanged 51 days agoMITView on GitHub
Manage local pyapp venv (status, editable install, reset)
- Installs packages
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- pyapp-build/AGENTS.mdAGENTS.md
- add-storySkill
- build-pyapp-exeSkill
- build-pypiSkill
- bumpSkill
- check-depsSkill
- releaseSkill
- test-from-wslSkill
- triage-prSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Read pyapp-build/build-config.json to get dist_path for the exe location
- Distinctive: line 18
Check if editable: Location field shows source path if editable, site-packages if normal install
- Distinctive: line 25
If worktree-path given in [ACTION]: use it
- Very specific: line 34
Delete the venv: powershell.exe -Command 'Remove-Item -Path "$env:LOCALAPPDATA\pyapp\data\whisper-key-local" -Recurse -Force'
- Very specific: line 35
Verify deleted: powershell.exe -Command 'Test-Path "$env:LOCALAPPDATA\pyapp\data\whisper-key-local"' should return False
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
[ACTION]=$ARGUMENTS
Pyapp venv lives at: %LOCALAPPDATA%\pyapp\data\whisper-key-local\<hash>\<version>\
The exe path comes from pyapp-build/build-config.json → dist_path field (append \whisper-key.exe).
Convert Windows path to WSL: C:\Users\... → /mnt/c/Users/.../
Actions
status (default if no action given)
- Read
pyapp-build/build-config.jsonto get dist_path for the exe location - Find venv:
powershell.exe -Command "Get-ChildItem -Path \"$env:LOCALAPPDATA\pyapp\data\whisper-key-local\" -Recurse -Directory | Where-Object { Test-Path (Join-Path $_.FullName 'Scripts\python.exe') } | Select-Object -ExpandProperty FullName" - Show installed package info: run
"<exe-wsl-path>" self pip show whisper-key-local - Check if editable: Location field shows source path if editable, site-packages if normal install
- Report: venv path, installed version, editable or not, which source path if editable
install [worktree-path]
Installs current worktree (or specified path) as editable into the pyapp venv.
- Read
pyapp-build/build-config.jsonto get dist_path for the exe location - Determine source path:
- If worktree-path given in [ACTION]: use it
- Otherwise: use current working directory
- Convert to Windows path if needed (WSL
/home/...→\\wsl.localhost\Ubuntu\home\...) - Run:
"<exe-wsl-path>" self pip install -e <windows-source-path> - Verify with
"<exe-wsl-path>" self pip show whisper-key-local
reset
Nukes the pyapp venv so next launch re-creates it from PyPI.
- Confirm with user before proceeding
- Delete the venv:
powershell.exe -Command 'Remove-Item -Path "$env:LOCALAPPDATA\pyapp\data\whisper-key-local" -Recurse -Force' - Verify deleted:
powershell.exe -Command 'Test-Path "$env:LOCALAPPDATA\pyapp\data\whisper-key-local"'should return False - Report completion — next exe launch will bootstrap fresh
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

