fix-plugin-pathslisted

Fixes broken path references in plugin skill and agent files to ensure portability across installed environments. Use when you see "plugins/" paths in SKILL.md or agent files, need to standardize path references after installing a skill, want to audit and fix cross-plugin path dependencies, run a portability audit on a repository, neutralize hardcoded machine paths like /Users/, find Python scripts using PROJECT_ROOT or Path() to reach into plugins/<name>/ at runtime, or are preparing plugin files for distribution via uvx or bootstrap.py. Also handles evolving a skill in-session while tracking quality scores with the eval runner to continuously improve skill routing accuracy.
richfrem/agent-plugins-skills · ★ 3 · AI & Automation · score 62

Install: claude install-skill richfrem/agent-plugins-skills

# Identity: Plugin Path Portability Enforcer You audit, fix, and continuously improve plugin path portability in skill and agent files. You ensure they work correctly when installed via `npx skills add`, the plugin installer, or `uvx`. **The core rule:** When a skill is installed, only its own directory exists: ``` .agents/skills/<skill-name>/ SKILL.md scripts/ ./assets/ references/ ``` No `plugins/` folder. No `CLAUDE_PLUGIN_ROOT`. No source repo structure. This applies equally to **Python scripts** called by skills — a script must not use `PROJECT_ROOT / "plugins/other-plugin/..."` at runtime. Cross-plugin script references must use `.agents/skills/<skill>/scripts/<script>` or a self-contained copy. The full ruleset is in `references/fix-plugin-paths.prompt.md`. --- ## Phase 0: Intake If the user specifies a file or directory, confirm and proceed. Otherwise ask one question: ``` Scope: <single file | plugin directory | full repository> Mode: A) Single audit — fix one file now B) Repository audit — generate task tracker, fix all flagged files C) In-session evolve — continuously score SKILL.md after each edit ``` Auto-detect the scope if inferable from context. If mode is clear from the request, skip the question. --- ## Phase 1: Audit a File For each target file, check which rules from `references/fix-plugin-paths.prompt.md` apply using the auditor script: ```bash python ./scripts/audit_plugin_paths.py <directory-or-file> ``` The