claude-plugins_skill

This skill helps you create and publish Claude Code plugins, guiding initialization, validation, and distribution across marketplaces.

TypeScript

25

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill outfitter-dev/agents --skill claude-plugins

SKILL.md11.1 KB

Overview

This skill guides the complete lifecycle for creating, validating, and distributing Claude Code plugins. It covers manifest formats for standalone plugins and marketplaces, component patterns (commands, agents, hooks, skills, MCP servers), caching implications, validation checklists, and release practices. Use it as a reference when scaffolding, testing, or publishing plugins.

How this skill works

The skill inspects project layout and manifest files (.claude-plugin/plugin.json or marketplace.json) and enforces required fields, naming conventions, and component schemas. It outlines component locations (commands/, agents/, hooks/, skills/), hook formats and types, MCP server config, and local testing commands. It also provides validation steps, packaging and semantic versioning guidance, and marketplace integration instructions.

When to use it

Scaffolding a new plugin or marketplace package
Adding commands, custom agents, event hooks, or MCP servers
Preparing a plugin for distribution or publishing to a marketplace
Validating plugin structure, metadata, and executables before release
Troubleshooting plugin installation, command visibility, or hook execution

Best practices

Use kebab-case for plugin, command, and agent names
Keep all resources inside the plugin directory to avoid cache/path issues
Do not hardcode secrets; reference environment variables instead
Include README.md, LICENSE, and CHANGELOG.md before distribution
Follow semantic versioning and tag releases (MAJOR.MINOR.PATCH)
Validate manifests and component schemas before publishing

Example use cases

Scaffold a standalone plugin with .claude-plugin/plugin.json and commands/
Create a consolidated local marketplace using .claude-plugin/marketplace.json with strict: false
Add a security-reviewer agent and load claude-agents patterns for consistent behavior
Define PreToolUse hooks that run validation scripts and ensure hooks are executable
Package an MCP server with command, args, and env entries for runtime integration

FAQ

Yes. Standalone plugins must include .claude-plugin/plugin.json with name, version, and description.

Can marketplace repositories omit plugin manifests?

Yes. Use marketplace.json with strict: false to consolidate metadata and avoid per-plugin manifests.

Why do my hooks fail after install?

Installed plugins are cached; ensure hook scripts are inside the plugin, executable (chmod +x), and regex matchers are valid.