Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

skills-development

Estrellas140

Forks15

Actualizado21 de mayo de 2026 a las 06:49

Use when authoring or revising plugin SKILL.md files in this repo. Captures the principles for keeping skills as compact shortcuts to MCP tool groups.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

miroapp

miroapp/miro-ai

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	skills-development
description	Use when authoring or revising plugin SKILL.md files in this repo. Captures the principles for keeping skills as compact shortcuts to MCP tool groups.

Skills Development

Principles for writing SKILL.md files in this repo:

Do not duplicate parameter definitions or tool descriptions. Duplication drifts, contradicts the live tools, and steers the agent away from features that work.
The agent must fetch parameter definitions and tool descriptions from the MCP server directly at call time.
Do not name specific tools, prefixes, or suffixes. The agent finds them in the MCP tool list.
Do not name specific parameters either. Describe values in prose ("the board item ID", "the image resource ID") rather than introducing code-shaped names (item_id, board_id). Parameter names drift the same way tool names do, and the agent should read the live MCP schema.

Más de este repositorio

mismo repositorio

miro-code-explain-on-board

miroapp/miro-ai

Use when the user wants to explain or visualize a codebase on a Miro board — produces a minimal, notation-correct set of architecture / structure / behavior diagrams (flowchart, UML class, UML sequence, ERD) plus a short companion document, grounded in real repo artifacts.

2026-06-17140

miro-code-review

miroapp/miro-ai

Use when the user wants to create a visual code review on a Miro board from a pull/merge request (GitHub, GitLab, or any forge), local uncommitted changes, or a branch comparison — produces a file-changes table, summary/architecture/security docs, and architecture diagrams, then links them back from the PR/MR.

2026-06-03140

miro-browse

miroapp/miro-ai

Use when the user wants to explore, list, summarize, or inspect items on a Miro board.

2026-05-21140

miro-code-spec

miroapp/miro-ai

Use when the user wants to extract a Miro board's specs (documents, diagrams, prototypes, tables, frames, images) to local `.miro/specs/` files for AI-assisted planning and implementation — accepts a board URL or single-item URL.

2026-05-21140

miro-diagram

miroapp/miro-ai

Use when the user wants to create or update a diagram on a Miro board.

2026-05-21140

miro-doc

miroapp/miro-ai

Use when the user wants to create or edit a Google-Docs-style markdown document on a Miro board.

2026-05-21140

name	skills-development
description	Use when authoring or revising plugin SKILL.md files in this repo. Captures the principles for keeping skills as compact shortcuts to MCP tool groups.

Skills Development

Principles for writing SKILL.md files in this repo:

Do not duplicate parameter definitions or tool descriptions. Duplication drifts, contradicts the live tools, and steers the agent away from features that work.
The agent must fetch parameter definitions and tool descriptions from the MCP server directly at call time.
Do not name specific tools, prefixes, or suffixes. The agent finds them in the MCP tool list.
Do not name specific parameters either. Describe values in prose ("the board item ID", "the image resource ID") rather than introducing code-shaped names (item_id, board_id). Parameter names drift the same way tool names do, and the agent should read the live MCP schema.