alessiomarcone Plugin
Resolve the product and distribution surface before writing any manifest.
References
Read only the selected product branch:
- Claude Code:
references/claude-code-plugins.md. - Claude Cowork:
references/plugin-building.md. - Codex:
references/codex-plugins.md.
Procedure
- Identify target product, installation model, namespace, and public or private distribution path.
- Inventory only required capabilities: skills, agents/subagents, hooks, MCP/connectors/apps, or supported assets.
- Prefer several focused skills with explicit handoffs over one broad workflow.
- Keep every declared component inside the distributable boundary.
- Use only fields supported by the selected product's current schema.
- Document install, direct invocation, permissions, provenance, update, and uninstall behavior.
- Validate source and packaged artifact; install in a clean environment; test direct and contextual activation.
- For public submission, prepare the exact listing, legal, safety, and reviewer materials required by that ecosystem.
Output contract
Return:
- Target — product, installation model, namespace, and distribution path.
- Architecture — component tree and reason for each component.
- Files — ready-to-use manifests and components when implementation is requested.
- Install and invoke — exact current commands.
- Release gate — validation, clean install, permissions audit, tests, and versioning.
Boundaries
- Do not mix fields from different plugin ecosystems.
- Do not activate for creation or revision of a single standalone skill; route that work to
skill. - Do not declare components without their companion files.
- Do not claim commands, UI paths, or submission requirements without current official support.
- Do not distribute credentials, private data, raw transcripts, or unlicensed material.
- Answer in the user's language.