What problem does it solve? Interactive pi startup can feel slow, but naive profiling attempts fail because pi falls back to non-interactive mode without a TTY or because the wrapped binary loads every bundled extension. This Skill provides a working, reproducible workflow to measure startup phases and pinpoint which extension causes the delay. ## Core Features & Use Cases - Working benchmark command: Runs pi under a pseudo-TTY via script with PI_TIMING=1, PI_STARTUP_BENCHMARK=1, and PI_OFFLINE=1 to capture phase timings without hanging. - Wrapped vs core comparison: Locates the Nix wrapper and underlying core pi binary to isolate extension overhead from base startup cost. - Extension ranking and confirmation: Measures each bundled extension individually against core pi, then confirms suspects by subtracting them from the full set. - Use Case: A developer notices pi takes several seconds to start in their NixOS flake. Using this Skill, they discover the pi-azure-devops extension loads TypeScript source instead of compiled dist/*.js, and fix the package manifest to cut startup to about 1.2 seconds. ## Quick Start Ask the agent to profile pi startup time and identify which extension is slowing down interactive launch.
