MetaSkill Plugin Packaging FAQs

Question 1

How do I test my Claude plugin during development?

Accepted Answer

You can use the 'dogfooding' approach by running 'claude --plugin-dir ./your-plugin-path'. This loads the plugin immediately and allows for rapid iteration.

Question 2

What is the recommended naming convention for plugins and skills?

Accepted Answer

Plugins should use a neutral noun prefix (e.g., 'datakit'). Skills within that plugin should use the gerund form (e.g., 'datakit-extracting'), while agents use role nouns and commands use imperative verbs.

Question 3

What files should be placed inside the .claude-plugin directory?

Accepted Answer

Only the plugin.json manifest (and marketplace.json if applicable) should go inside the .claude-plugin directory. All other components like skills, agents, and commands must stay at the plugin root.

Question 4

How can I manage multiple plugins in a single repository?

Accepted Answer

You can create a marketplace.json file within a .claude-plugin directory at the repository root. This file maps unique plugin names to their respective subdirectories within the repo.

Question 5

Does a Claude plugin require a specific manifest file?

Accepted Answer

Yes, every plugin requires a plugin.json file located in the .claude-plugin/ directory. It must contain at least the name, version, and description of the plugin.

MetaSkill Plugin Packaging

Key Features

Use Cases

MetaSkill Plugin Packaging

Key Features

Use Cases