Estructura de Plugin

Defines plugin directory structure, manifest configuration, and component auto-discovery conventions.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/juanjo-zurich/juarvis-v4 --skill estructura-de-plugin-juanjo-zurich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Estructura de Plugin
Source: https://github.com/juanjo-zurich/juarvis-v4/tree/main/plugins/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/juanjo-zurich/juarvis-v4 --skill estructura-de-plugin-juanjo-zurich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When building plugins for AI agent ecosystems, developers often struggle with where to place the manifest, how to organize commands, agents, skills, and hooks, and why components fail to load. This Skill provides the standardized directory layout and manifest rules so plugins are discovered and loaded correctly. ## Core Features & Use Cases - Standardized Directory Layout: Defines the canonical structure with .plugin/plugin.json, commands/, agents/, skills/, hooks/, and .mcp.json. - Manifest Configuration: Documents required fields (kebab-case name), recommended metadata, and custom component path overrides. - Auto-Discovery & Troubleshooting: Explains how components are scanned automatically and how to fix loading, path resolution, and naming issues using ${PLUGIN_ROOT}. - Use Case: You are creating a new plugin with slash commands and a custom skill. Use this Skill to scaffold the correct directory tree, write a valid plugin.json, and verify every component is auto-discovered. ## Quick Start Ask the agent to create a new plugin called "mi-plugin" with one command and one skill following the standard plugin structure.

Frequently Asked Questions about Estructura de Plugin

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

FAQPage Schema
How do I structure a plugin directory for agent plugins?▼

Place the manifest at .plugin/plugin.json and put component directories (commands/, agents/, skills/, hooks/) at the plugin root. Each skill needs its own subdirectory containing a SKILL.md file.

What fields are required in a plugin.json manifest?▼

Only the name field is strictly required, in kebab-case format and unique among installed plugins. Version, description, author, license, and keywords are recommended metadata, and custom component paths can be declared optionally.

Why is my plugin component not loading or auto-discovered?▼

Check that the component sits in the correct root-level directory with the right extension, that YAML frontmatter syntax is valid, and that skills contain a SKILL.md file. Also confirm the plugin is enabled and naming follows kebab-case conventions.

How do I make plugin paths portable across systems?▼

Replace all hardcoded absolute paths with ${PLUGIN_ROOT} references and use relative paths inside the manifest. Test the plugin on multiple systems and document any external dependencies.

Can I customize where plugin components are located?▼

Yes, the manifest supports custom path overrides for commands, agents, hooks, and MCP server definitions, including arrays of multiple directories. Default convention-based directories are used when no overrides are declared.