Avoid "externally-managed-environment" with pipx and venv
Modern Kali and Debian mark system Python as externally managed (PEP 668), breaking bare `pip install` workflows. This recipe standardizes pipx for CLI tools and venv for libraries so tool installs stay isolated and the distro stays intact.
Create a skill called "PEP 668 Python Tool Installer". Inputs I will provide: - OS/distro (Kali/Debian/Ubuntu) - The tool name and whether it is a CLI application or a Python library - The exact pip error output (if any) Task: 1) Choose the correct install method: apt package, pipx, or venv. 2) Output the exact commands to install, verify, and record the installed version. 3) Provide a troubleshooting checklist for PATH issues and venv activation mistakes.
Common symptom:
`sudo apt update && sudo apt install -y pipx`
`pipx ensurepath`
`pipx install
Example:
`pipx install semgrep`
`python3 -m venv .venv`
`source .venv/bin/activate`
`python3 -m pip install -U pip`
`python3 -m pip install
`git clone
`cd
`python3 -m venv .venv && source .venv/bin/activate`
`python3 -m pip install -r requirements.txt`
Fix "no templates provided", template drift, and signing surprises
Nuclei scans fail not because the engine is broken but because templates are missing, outdated, filtered out, or failing validation. This recipe diagnoses template path and version problems, performs safe updates, validates templates, and explains a secure workflow for code-template signing.
Fix raw-socket "Operation not permitted" without --privileged
Least-privilege setup for running Nmap, MASSCAN, or ZMap inside Docker/Podman/Kubernetes. Solves "requires root privileges" and "Operation not permitted" failures without reaching for --privileged. Includes fallbacks when raw sockets are unavailable.
Keep your content off the AI slop list
Have your Claw periodically check the AI Slop Wiki and build a living filter of patterns to avoid. Every piece of content your Claw creates runs through this filter first, so you never publish anything that reads like generic AI-generated filler.
A playbook for "stops at the same frame" and "freeze mid-render" failures
Renders freeze at a consistent percentage or frame — often caused by a bad clip, a heavy effect, a Fusion comp issue, or "stop render on error" settings. This recipe classifies the failure pattern and gives you a structured triage plan instead of blind re-exports.