What problem does it solve? Powerpacks installs can end up running from the wrong path (such as a legacy .codex/powerpacks checkout), leaving local state split across duplicate .powerpacks roots, broken msgvault/WhatsApp/LinkedIn links, and stale run-id artifact directories. This Skill diagnoses those path and state problems and applies safe, non-destructive repairs. ## Core Features & Use Cases - Canonical repo enforcement: Resolves the non-.codex Powerpacks repo and refuses to run product commands from legacy installs. - State adoption and repair: Copies newer or missing managed files (.env, contacts CSVs, wacli stores, network-import manifests) into the canonical .powerpacks root without overwriting newer data. - Health reporting: Reports discovery/import manifest status per source (Gmail, LinkedIn, Messages), wacli authentication state, and stale run-id/temp directories for later cleanup. - Use Case: After Codex accidentally used .codex/powerpacks and setup became brittle, run the fixer to adopt the newer state into the canonical repo, scrub a bad unauthenticated wacli placeholder, and get a manifest health report. ## Quick Start Ask the agent to run $fix-powerpacks to diagnose my Powerpacks install paths and repair the local state directories.
