metaskill-packaging_skill

This skill guides packaging and structuring Claude Code plugins, enabling clean plugin.json placement and organized components for distribution.

Shell

1

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 gigaverse-app/skillet --skill metaskill-packaging

SKILL.md8.3 KB

Overview

This skill packages skills, agents, commands, and hooks into Claude Code plugins so they can be installed, distributed, and dogfooded. It enforces correct plugin layout and manifest requirements, and provides workflows for rapid iteration, marketplace testing, and repo placement. Use it to create consistent, distributable plugins that follow naming and structure conventions.

How this skill works

The skill validates and organizes plugin files so only plugin.json lives in .claude-plugin/ while all components (skills, agents, commands, hooks) remain at the plugin root. It guides construction of plugin.json with required and recommended metadata and enforces naming patterns for plugin names, skills (-ing), agents (role nouns), and commands (imperative verbs). It also documents dogfooding commands and marketplace manifest formats to test installation flows.

When to use it

Creating a new Claude Code plugin for distribution
Packaging skills, agents, commands, or hooks into a plugin
Setting up or validating plugin structure and plugin.json
Dogfooding changes locally during development (--plugin-dir)
Preparing a plugin for marketplace testing or release

Best practices

Keep only plugin.json inside .claude-plugin/; place all components at the plugin root
Use a neutral noun for the plugin name and consistent prefixes across atoms
Name skills with -ing (gerund), agents as role nouns, and commands as imperative verbs
Include recommended metadata in plugin.json (author, license, repository, keywords)
Use marketplace.json for repos containing multiple plugins and to test install/uninstall flows

Example use cases

Rapid development: load a plugin locally with claude --plugin-dir ./my-plugin for fast iteration
Marketplace pre-release: add repo with /plugin marketplace add and test install/uninstall to verify UX
Monorepo placement: include internal plugins under plugins/ and load with --plugin-dir for dogfooding
Multiple-plugin repo: create .claude-plugin/marketplace.json to expose several plugins from one repository
Distribution repo: keep the repo root as the plugin with .claude-plugin/plugin.json and top-level skills/agents/commands

FAQ

Only plugin.json belongs in .claude-plugin/. All components (skills, agents, commands, hooks) must be placed at the plugin root.

What fields are required in plugin.json?

At minimum include name, version, and description. Recommended fields include author, license, keywords, repository, and homepage.

How do I test changes locally?

For quick iteration load the folder with claude --plugin-dir ./path/to/plugin. Restart Claude Code to pick up file changes; for full-install testing use the marketplace add/install flow.