From 0ac49b0e3ba8fa02cadb9b78946b63dbc939fc1f Mon Sep 17 00:00:00 2001 From: Steve Nims Date: Wed, 10 Dec 2025 07:29:33 -0500 Subject: [PATCH] docs: add ${CLAUDE_PLUGIN_ROOT} explanation to marketplace-structure skill MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add explanatory note before the Complete Plugin Entry Example in schema-reference.md to explain that ${CLAUDE_PLUGIN_ROOT} resolves to the plugin's installation directory and should be used for portable paths. Fixes #95 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .../skills/marketplace-structure/references/schema-reference.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/plugins/plugin-dev/skills/marketplace-structure/references/schema-reference.md b/plugins/plugin-dev/skills/marketplace-structure/references/schema-reference.md index 68e608f..807ceaa 100644 --- a/plugins/plugin-dev/skills/marketplace-structure/references/schema-reference.md +++ b/plugins/plugin-dev/skills/marketplace-structure/references/schema-reference.md @@ -150,6 +150,8 @@ For GitLab, Bitbucket, or self-hosted git repositories: ## Complete Plugin Entry Example +**Note:** The `${CLAUDE_PLUGIN_ROOT}` variable in the example below resolves to the plugin's absolute installation path. Use this variable for portable paths in hooks and MCP server configurations, ensuring paths work regardless of where the plugin is installed. + Advanced plugin entry with all optional fields: ```json