mira-new-plugin

Orchestrates creation, validation, and activation of user-authored Mira agent plugins.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/mayconspirlandelli/slides-podcast-ia-home-office --skill mira-new-plugin-mayconspirlandelli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mira-new-plugin
Source: https://github.com/mayconspirlandelli/slides-podcast-ia-home-office/tree/main/.agents/skills/mira-new-plugin
Command: npx skills add https://github.com/mayconspirlandelli/slides-podcast-ia-home-office --skill mira-new-plugin-mayconspirlandelli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating a custom Mira agent plugin involves many coordinated steps: checking for the Reversa toolchain, scaffolding the plugin folder, writing specifications, implementing the SKILL.md, validating the manifest, and activating it. This Skill orchestrates that entire lifecycle so nothing is missed or done out of order. ## Core Features & Use Cases - End-to-end plugin scaffolding: Derives a valid plugin identifier, copies the plugin template into mira-plugins/<id>/, and keeps folder name, manifest id, and SKILL.md name in sync. - Reversa orchestration: Checks whether Reversa is installed (installing only with explicit user consent), runs /reversa-new once per workshop, then drives the forward cycle (requirements, clarify, plan, to-do, coding) scoped strictly to the plugin folder. - Validation and activation: Runs npx mira-animator plugin validate <id> and plugin sync, enforces constraints (self-contained folder, no executable files, single SKILL.md with optional references/assets), and supports an edit mode that bumps the version. - Use Case: A user says "quero fazer meu proprio agente" and this Skill walks them from idea to a validated, shareable .mplug plugin without touching anything outside mira-plugins/<id>/. ## Quick Start Ask the assistant to create a new Mira plugin by describing what your custom agent should do, for example by saying "/mira-new-plugin" or "criar plugin do Mira que resume reunioes".

Frequently Asked Questions about mira-new-plugin

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

FAQPage Schema
How do I create a custom Mira agent plugin?▼

Invoke /mira-new-plugin and describe what the agent should do. The Skill derives a valid identifier, scaffolds mira-plugins/<id>/ from the plugin template, runs the Reversa specification and implementation cycle, then validates and activates the plugin.

What are the rules for naming a Mira plugin identifier?▼

The identifier must use only lowercase letters, digits, and hyphens, contain at least one hyphen, and follow the <author>-<name> format. It cannot start with the reserved mira- prefix or collide with native agents or existing folders in mira-plugins/.

Can a Mira plugin contain executable scripts like Python or JavaScript?▼

No. The first version of the Mira plugin system rejects any executable files such as .js, .sh, .bat, .ps1, or .py. A plugin must be a single SKILL.md with optional references/ and assets/ folders, fully self-contained in its own directory.

Does the Skill install Reversa automatically?▼

No. If Reversa is missing, the Skill asks for explicit permission before running npx reversa install, explaining that it creates .reversa/ and modifies CLAUDE.md and .gitignore. Without an explicit yes, it stops without installing anything.

How do I share or uninstall a Mira plugin?▼

Run npx mira-animator plugin pack <id> to generate a .mplug file that others install with plugin add or by copying the folder into mira-plugins/. To uninstall, delete mira-plugins/<id>/ and Mira removes the activated copy on the next sync.

Why are the Reversa spec folders not included when sharing a plugin?▼

The _reversa_sdd/ and _reversa_forward/ folders stay local and are not part of the shared package. Recipients get a working plugin but cannot evolve it from the specs; deleting those folders leaves only the SKILL.md.