Create a new Kiro Power using the Agent Plugins v1.0.0 specification. Use when building a new power from scratch with plugin.json, skills, and optional MCP server configuration.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Create a new Kiro Power using the Agent Plugins v1.0.0 specification. Use when building a new power from scratch with plugin.json, skills, and optional MCP server configuration.
license
MIT
metadata
{"author":"Kiro Team","version":"1.0.0"}
Create a New Agent Plugin
Interactive workflow for creating a Kiro Power that conforms to the Agent Plugins specification v1.0.0.
Overview
This skill guides you through creating a portable plugin with:
A plugin.json manifest
One or more skills (each with SKILL.md)
Optional mcp.json for MCP server integration
Optional helper scripts, references, and assets
Workflow Overview
1. Understand the user's use case
2. Determine plugin components (skills, MCP, or both)
3. Create plugin directory and plugin.json
4. Create skills (SKILL.md + supporting files)
5. Create mcp.json (if MCP server involved)
6. Test and install locally
Step-by-Step Guide
1. Understand the Use Case
Have a natural conversation to understand:
What problem does this plugin solve?
Does it involve an MCP server? (needs mcp.json)
What distinct tasks/workflows does it enable? (each becomes a skill)
Is it pure documentation/guidance? (skills only, no mcp.json)
Who is the audience?
Through this conversation, determine:
The plugin name (lowercase, hyphens, 1-64 chars, no --)
Whether it needs mcp.json (MCP server integration)
How many skills it needs (one per distinct workflow/concern)
$schema is exactly https://agent-plugins.org/schemas/1.0.0/mcp.schema.json
Each server has a type field (stdio, streamable-http, or sse)
stdio: command is a single token (not a shell string)
stdio: command is either a bare name or starts with ./
env does not contain PLUGIN_ROOT or PLUGIN_DATA keys
If cwd present: starts with ./, ${PLUGIN_ROOT}, or ${PLUGIN_DATA}
Remote URLs are HTTPS (HTTP only for localhost)
No secrets in env or headers
No fields beyond those defined per transport type
5.3: Sanitize for Sharing
If the mcp.json contains user-specific values, replace with placeholders and document them in the relevant skill's SKILL.md under a "Configuration" section.
6. Final Structure Validation
Verify the complete plugin:
{plugin-name}/
โโโ plugin.json # Required
โโโ skills/ # At least one skill recommended
โ โโโ {skill-1}/
โ โ โโโ SKILL.md # Required per skill
โ โ โโโ scripts/ # Optional
โ โ โโโ references/ # Optional
โ โ โโโ assets/ # Optional
โ โโโ {skill-2}/
โ โโโ SKILL.md
โโโ mcp.json # Only if MCP server involved
Final checklist:
plugin.json exists at root with valid $schema and name
All skills have SKILL.md with valid frontmatter
Skill name in frontmatter matches directory name
mcp.json (if present) has valid $schema and mcpServers
No files reference paths outside the plugin root
No secrets in any configuration files
7. Test and Install
Install Locally
Open Kiro Powers UI (call action="configure")
Click "Add Custom Power" at the top
Select "Local Directory"
Provide the absolute path: {workspace}/powers/{plugin-name}
Click "Add"
Test
Use the "Try Power" button on the power's detail page
Also test in a fresh agent chat session
Make natural language requests that should trigger the power's skills
Verify MCP tools work if applicable
Iterate
If issues found:
Edit files in {workspace}/powers/{plugin-name}/
In Powers UI, navigate to the installed power
Click "Check for Updates" then "Update Power"
Re-test
Sharing
GitHub Repository
Push to a public GitHub repository. Users add the repo URL in Kiro Powers UI.
Before sharing:
Sanitize mcp.json (replace secrets with placeholders)
Document all placeholders in relevant SKILL.md files
