cc-pluginroot-directory-source-ignored

Fix Claude Code plugin loading errors by replacing pluginRoot with explicit plugin paths.

Updated Nov 18, 2025

Search Tags:#debugging #claude code #plugins #marketplace #apm #path resolution

Ready to run

npx skills add https://github.com/cajias/claude-skills --skill cc-pluginroot-directory-source-ignored

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cc-pluginroot-directory-source-ignored
Source: https://github.com/cajias/claude-skills/tree/main/plugins/cc-authoring/skills/cc-pluginroot-directory-source-ignored
Command: npx skills add https://github.com/cajias/claude-skills --skill cc-pluginroot-directory-source-ignored

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It fixes a Claude Code marketplace loading failure where plugins appear to exist on disk but are resolved to the wrong path because metadata.pluginRoot is ignored for directory-source marketplaces.

Core Features & Use Cases

Diagnose the failure mode: Identify when a local directory-source marketplace is using pluginRoot in a way Claude Code does not apply at runtime.
Apply the correct fix: Replace short plugin sources with explicit ./plugins/<name> paths and remove the unused pluginRoot setting.
Handle APM-managed setups: Update both apm.yml and the generated marketplace file so the fix survives repackaging and CI checks.
Verify resolution: Confirm the marketplace JSON parses, plugin paths use the correct prefix, and Claude Code stops reporting missing plugin directories.

Quick Start

Ask Claude to inspect your directory-source Claude Code marketplace for ignored pluginRoot paths and rewrite the plugin sources to explicit ./plugins/<name> entries.

Frequently Asked Questions about cc-pluginroot-directory-source-ignored

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

FAQPage Schema

Why does Claude Code ignore the pluginRoot setting in my directory-source marketplace?▼

Claude Code ignores pluginRoot in directory-source marketplaces because runtime path resolution requires explicit plugin source entries. When metadata.pluginRoot is set instead of direct paths, plugins resolve incorrectly and fail to load from their on-disk locations.

How do I fix Claude Code plugin loading errors caused by ignored pluginRoot paths?▼

Fix Claude Code plugin loading errors by replacing short plugin sources with explicit ./plugins/<name> paths and removing the unused pluginRoot setting from marketplace metadata. This ensures runtime path resolution matches the actual on-disk plugin layout.

How do I update APM-managed marketplace files to fix broken Claude Code plugin paths?▼

Update both apm.yml and the generated marketplace file to use explicit ./plugins/<name> paths and remove pluginRoot settings. This ensures the path resolution fix survives repackaging and CI checks in APM-managed setups.

What is the correct way to validate Claude Code marketplace JSON after fixing plugin paths?▼

Validate Claude Code marketplace JSON by confirming the file parses correctly, all plugin sources use the explicit ./plugins/<name> prefix, and Claude Code no longer reports missing plugin directories at runtime.

Does this plugin path fix work for local marketplace authoring and APM-managed packaging?▼

Yes, the fix applies to both local marketplace authoring and APM-managed packaging by requiring explicit plugin source paths and removing pluginRoot from metadata. It validates that generated marketplace files match the on-disk layout across both workflows.