Locating Plugin Source Code

Locate installed Claude Code plugin source via installed_plugins.json installPath.

2|1|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/bbrowning/bbrowning-claude-marketplace --skill locating-plugin-source-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Locating Plugin Source Code
Source: https://github.com/bbrowning/bbrowning-claude-marketplace/tree/main/bbrowning-claude/skills/plugin-source-locator
Command: npx skills add https://github.com/bbrowning/bbrowning-claude-marketplace --skill locating-plugin-source-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps users locate the source code for installed Claude plugins, navigate plugin structure, read reference materials in plugins, or debug plugin issues by reading installed plugins metadata and following installPath.

Core Features & Use Cases

  • Discovery: Locate plugin directories via installed_plugins.json
  • Navigation: Find SKILL.md and reference docs within a plugin
  • Debugging: Read plugin components to understand implementation

Quick Start

Read ~/.claude/plugins/installed_plugins.json, locate the requested plugin's installPath, then cd into that path and inspect skills/<skill>/SKILL.md or reference/ docs.

Frequently Asked Questions about Locating Plugin Source Code

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

FAQPage Schema
How do I locate the source code for an installed Claude Code plugin?

Plugin source code locations are stored in ~/.claude/plugins/installed_plugins.json. Read this file to find each plugin's installPath, then navigate to that directory to access the plugin's SKILL.md and source files.

Where can I find SKILL.md and reference documentation within a plugin directory?

After locating a plugin's installPath, reference materials are organized in skills/<skill>/SKILL.md and reference/ subdirectories. Navigate into the plugin directory and inspect these locations using standard filesystem commands.

How do I debug plugin issues by reading the plugin source?

Access installed_plugins.json to identify the plugin's installPath, then explore the plugin's directory structure and component files to understand its implementation and identify the source of issues.

Can I modify a local plugin after locating its source code?

Yes. Once you've located the plugin's installPath through installed_plugins.json and navigated to the directory, you can read and edit the plugin files directly for local modifications.

What's the fastest way to discover where a specific skill or command file is stored?

Start with ~/.claude/plugins/installed_plugins.json to extract the target plugin's installPath, then navigate directly to that path and search the skills/ subdirectories for the specific skill or command implementation.