fix-plugin-paths

Standardize plugin path references for portability across skill installations.

5|3|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/richfrem/agent-plugins-skills --skill fix-plugin-paths
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-plugin-paths
Source: https://github.com/richfrem/agent-plugins-skills/tree/main/plugins/agent-scaffolders/skills/fix-plugin-paths
Command: npx skills add https://github.com/richfrem/agent-plugins-skills --skill fix-plugin-paths

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixes broken path references in plugin skill and agent files to ensure portability across installed environments. It helps when you see "plugins/" paths in SKILL.md or agent files, standardize path references after installation, audit and fix cross-plugin path dependencies, run a portability audit on a repository, neutralize hardcoded machine paths like /Users/, and reach into plugins/<name>/ at runtime via Python scripts or when preparing plugin files for distribution via uvx or bootstrap.py. It also supports evolving a skill in-session while tracking quality scores with the eval runner to continuously improve skill routing accuracy.

Core Features & Use Cases

  • Audit and fix plugin path portability across skills and agents.
  • Normalize references from plugins/<plugin>/skills/<skill>/ to installed locations (.agents/skills/<skill>/...).
  • Neutralize absolute machine paths (e.g., /Users/...) and ensure runtime scripts avoid hardcoded roots.
  • Prepare plugin files for distribution via uvx/bootstrap.py and support in-session evolution with eval-runner tracking.

Quick Start

Run a portability audit across your repository and apply fixes to standardize all plugin path references.

Frequently Asked Questions about fix-plugin-paths

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix broken plugin path references in SKILL.md and agent files?

You can standardize plugin path references by normalizing plugins/<plugin>/skills/<skill>/ paths to installed locations and neutralizing absolute machine paths like /Users/. This enforces portability across skill installations while aligning with SKILL.md frontmatter rules.

What is a plugin portability audit and when do I need to run one?

A plugin portability audit identifies and standardizes all path references across plugins and agents to ensure they function across installed environments. Run this audit when preparing plugin files for distribution via uvx or bootstrap.py to prevent hardcoded path failures.

How do I remove hardcoded absolute machine paths like /Users/ from runtime scripts?

You can remove hardcoded absolute machine paths like /Users/ from runtime scripts by neutralizing path roots and ensuring scripts reach into plugins/<name>/ dynamically. This prevents environment-specific failures during cross-skill execution and distribution.

Does this portability fix process support in-session skill evolution and quality tracking?

Yes, the portability fix process supports evolving a skill in-session while tracking quality scores with the eval runner. This allows you to continuously improve skill routing accuracy alongside applying repository-wide path standardization fixes.

What is the best way to normalize cross-plugin path dependencies for distribution?

The best way to normalize cross-plugin path dependencies is running a repository-wide audit and applying fixes that map plugins/ paths to .agents/skills/<skill>/ locations. This aligns references with SKILL.md frontmatter rules for safe distribution via uvx.

Why do my cross-skill references break after installing plugins in a new environment?

Cross-skill references break due to hardcoded absolute machine paths and un-normalized plugins/ directory structures. Fixing these references to point to installed locations (.agents/skills/...) resolves cross-plugin portability issues across different environments.