generic-setup-claude-plugin-locally

Automate global setup of a local Claude Code plugin via symbolic link.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Puzzle9900/puzzle9900-claude-plugin --skill generic-setup-claude-plugin-locally
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generic-setup-claude-plugin-locally
Source: https://github.com/Puzzle9900/puzzle9900-claude-plugin/tree/main/skills/generic-setup-claude-plugin-locally
Command: npx skills add https://github.com/Puzzle9900/puzzle9900-claude-plugin --skill generic-setup-claude-plugin-locally

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of setting up a local Claude Code plugin so it's available globally, ensuring all your development changes are picked up automatically on restart.

Core Features & Use Cases

  • Global Plugin Access: Makes your local plugin accessible in any Claude Code session.
  • Live Development: Automatically picks up changes (new skills, edits) without version bumps or reinstallation.
  • Use Case: You're building a new Claude Code plugin. Use this Skill to link your local development directory to Claude Code's global plugin system, so you can test new features instantly as you code.

Quick Start

Use the generic-setup-claude-plugin-locally skill to set up the plugin located at /Users/you/projects/my-claude-plugin.

Frequently Asked Questions about generic-setup-claude-plugin-locally

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

FAQPage Schema
How do I set up a local Claude Code plugin globally for live development?

To set up a local Claude Code plugin globally, you validate the plugin manifest and execute a setup script that registers it in user settings and cache directories using a symbolic link. This ensures live development changes are picked up automatically upon session restart.

Why are my local Claude Code plugin changes not reflected without reinstallation?

Local Claude Code plugin changes require a symbolic link to the global plugin system to enable live reload. Without linking your development directory, new skills and edits will not be picked up automatically on session restart without version bumps or manual reinstallation.

What's the best way to test a Claude Code plugin continuously during development?

The best way to test a Claude Code plugin continuously is to link your local development directory to the global plugin system via a symbolic link. This live reload setup automatically reflects all development changes upon session restart for continuous integration workflows.

Do I need to validate a plugin manifest before linking it to Claude Code globally?

Yes, validating the plugin manifest is required before linking a local plugin to Claude Code globally. Manifest validation ensures the setup script can successfully register the plugin in user settings and cache directories for live development.

Can I use a symlink to make my local Claude Code plugin available in any session?

Yes, you can use a symlink to make your local Claude Code plugin available globally in any session. The setup script creates a symbolic link from your development directory to the global plugin system, ensuring changes are accessible across all Claude Code sessions.