plugins-manager

Create, validate, and improve Claude Code plugins following the JARVIS-02 policy.

1|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/Jarvis-Projects/plugin-dev --skill plugins-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugins-manager
Source: https://github.com/Jarvis-Projects/plugin-dev/tree/main/skills/plugins-manager
Command: npx skills add https://github.com/Jarvis-Projects/plugin-dev --skill plugins-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the entire lifecycle of Claude Code plugin development, from initial creation and validation to ongoing improvement and adaptation of existing plugins.

Core Features & Use Cases

  • Plugin Creation: Guides users through creating new plugins, whether shared templates or custom domain-specific ones.
  • Validation: Provides a comprehensive checklist to ensure plugins adhere to structure, naming, and component best practices.
  • Improvement & Adaptation: Offers workflows for fixing existing plugins and integrating marketplace plugins into the JARVIS ecosystem.
  • Use Case: A developer needs to create a new plugin for managing user profiles. They can use this skill to set up the correct directory structure, define the plugin.json manifest, and create initial agent and command files, ensuring it follows all JARVIS standards.

Quick Start

Use the plugins-manager skill to create a new plugin for managing user authentication.

Frequently Asked Questions about plugins-manager

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

FAQPage Schema
How do I create a Claude Code plugin that follows the JARVIS-02 policy?

To create a Claude Code plugin following the JARVIS-02 policy, use a guided workflow to establish a conventional directory layout, define the plugin.json manifest, and organize components using the ${CLAUDE_PLUGIN_ROOT} variable for strict standard compliance.

What is the best way to validate an existing plugin's manifest and directory structure?

Validating a plugin's manifest and directory structure involves running a comprehensive checklist that enforces naming conventions, component organization, and JARVIS-02 policy standards to ensure the plugin is correctly configured for the ecosystem.

Can I adapt a marketplace plugin to work within the JARVIS ecosystem?

Yes, you can adapt marketplace plugins into the JARVIS ecosystem by using an improvement workflow that restructures the plugin's directory layout and manifest configuration to meet JARVIS-02 policy requirements.

How do I fix issues with a Claude Code plugin that violates component organization standards?

Fixing Claude Code plugin component organization issues requires using a targeted workflow that corrects the directory layout and manifest configurations, ensuring the plugin adheres to JARVIS-02 policy and structural best practices.

Do I need to use the ${CLAUDE_PLUGIN_ROOT} variable for Claude Code plugin development?

Yes, using the ${CLAUDE_PLUGIN_ROOT} variable is required for Claude Code plugin development under the JARVIS-02 policy to enforce conventional directory layouts and ensure proper component organization across different environments.

What is the standard directory layout for a JARVIS plugin?

The standard directory layout for a JARVIS plugin enforces specific conventional structures for agent files, command files, and the plugin.json manifest, all organized and referenced using the ${CLAUDE_PLUGIN_ROOT} variable for consistency.