plugin-creator

Create Claude Code plugins with templates for commands, agents, hooks, and scripts.

13|1|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/d-oit/gemini-search-plugin --skill plugin-creator-d-oit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/d-oit/gemini-search-plugin/tree/main/.claude/skills/plugin-creator
Command: npx skills add https://github.com/d-oit/gemini-search-plugin --skill plugin-creator-d-oit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the complex process of creating Claude Code plugins by providing a structured approach, best practices, and ready-to-use templates. It eliminates guesswork and ensures plugins are well-architected, compliant with official guidelines, and marketplace-ready.

Core Features & Use Cases

  • Structured Plugin Architecture: Guides through setting up core configuration (plugin.json, marketplace.json), commands, agents, and hooks.
  • Best Practices & Patterns: Implements context isolation for token savings, robust error handling, caching strategies, and semantic versioning.
  • Ready-to-Use Templates: Provides templates for README.md, commands, agents, hooks, and scripts to jumpstart development.
  • Use Case: A developer wants to create a new Claude Code plugin but is unsure about the official structure, configuration, or best practices. This skill walks them through every step, from initialization to marketplace publishing.

Quick Start

Initialize plugin structure

mkdir -p my-plugin/.claude-plugin mkdir -p my-plugin/commands mkdir -p my-plugin/agents mkdir -p my-plugin/hooks mkdir -p my-plugin/scripts mkdir -p my-plugin/tests

Frequently Asked Questions about plugin-creator

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

FAQPage Schema
How do I create a Claude Code plugin from scratch?

Creating a Claude Code plugin requires setting up a structured directory with plugin.json for core metadata, marketplace.json for publishing details, and subdirectories for commands, agents, hooks, and scripts. This Skill provides templates and step-by-step scaffolding to initialize the full plugin structure and ensure compliance with official guidelines.

What goes in plugin.json and marketplace.json files?

plugin.json defines your plugin's core configuration including name, version, and entry points for commands and agents. marketplace.json contains publishing metadata like description, pricing, and visibility settings. This Skill guides you through configuring both files correctly and validates them against official specifications.

What are best practices for Claude Code plugin architecture?

Best practices include context isolation to reduce token usage, robust error handling, caching strategies, semantic versioning, and modular command and agent design. This Skill implements these patterns across templates and provides guidance for structuring commands, agents, hooks, and scripts to follow official recommendations.

How do I prepare a Claude Code plugin for marketplace publishing?

Publishing requires a complete plugin structure with validated configuration files, comprehensive README.md documentation, tested commands and agents, and marketplace.json metadata. This Skill walks through the full development, testing, and deployment pipeline to ensure your plugin meets marketplace requirements.

Can I use this to add commands and agents to an existing plugin?

Yes, this Skill covers adding new commands, agents, hooks, and scripts to an existing plugin structure. It provides templates and validation patterns to ensure new components integrate properly with your plugin's architecture and follow best-practice patterns.