Create powers

Developers can use our curated powers from the powers registry, including Datadog, Figma, Neon, Netlify, Postman, Supabase, and Stripe, or build and share their own powers for any tool or framework. Community members have also created powers for building SaaS applications, managing AWS CDK infrastructure, and building agents with Pydantic AI.

Powers follow the Agent Plugins specification — an open, vendor-neutral format for packaging reusable components that extend AI agents. When you mention relevant keywords, Kiro loads the power's context and tools automatically.

View our curated powers at kiro.dev/powers

What you need

Every power needs a plugin.json manifest. Optionally, you can add:

skills/ — Agent Skills with task-specific instructions
mcp.json — MCP server configuration for tool integrations

Creating plugin.json

Your plugin.json manifest identifies the power and tells Kiro when to activate it. At minimum, it requires:

json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "supabase",
  "version": "1.0.0",
  "description": "Build fullstack applications with Supabase's Postgres database, authentication, storage, and real-time subscriptions",
  "author": {
    "name": "Supabase"
  },
  "keywords": ["database", "postgres", "auth", "storage", "realtime", "backend", "supabase", "rls"]
}

Required fields

Field	Description
`$schema`	Schema URL: `https://agent-plugins.org/schemas/1.0.0/plugin.schema.json`
`name`	Plugin identifier (kebab-case, no spaces). Used internally by Kiro to identify the power.
`version`	Semantic version of the power (e.g., `1.0.0`).
`description`	Short description of what the power does.
`author`	Object with at minimum a `name` field. Can also include `email` and `url`.
`keywords`	Array of strings that trigger activation. Use terms that match how developers talk about your tool.

When someone says "Let's set up the database," Kiro sees "database" in the keywords and activates the Supabase power. The power's MCP tools and skills load into context automatically.

Optional fields

You can also include these fields in your manifest:

json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "supabase",
  "version": "1.0.0",
  "description": "Build fullstack applications with Supabase",
  "author": {
    "name": "Supabase",
    "url": "https://supabase.com"
  },
  "keywords": ["database", "postgres", "supabase"],
  "homepage": "https://supabase.com/docs",
  "repository": "https://github.com/supabase/kiro-power",
  "license": "Apache-2.0"
}

Adding skills

Skills are instructions that guide the agent through specific tasks. Each skill lives in its own directory under skills/ and requires a SKILL.md file.

skills/
└── setup/
    ├── SKILL.md
    ├── scripts/
    │   └── validate-setup.sh
    └── references/
        └── schema-patterns.md

SKILL.md

The SKILL.md file contains the instructions the agent follows when the skill is invoked. Structure it with clear steps:

markdown

---
name: setup
description: Set up a new Supabase project with local development
---

# Set up Supabase

## Step 1: Validate dependencies

Before using Supabase, ensure the following are installed:
- **Docker Desktop**: Required for the local development stack
  - Verify with: `docker --version`
- **Supabase CLI**: Install via npm or Homebrew
  - Verify with: `supabase --version`

## Step 2: Initialize the project

Run `supabase init` to create the project configuration.

## Step 3: Start local services

Run `supabase start` to spin up the local Supabase stack.

Scripts

The scripts/ directory holds executable files the agent can run during skill execution. Use scripts for validation, setup automation, or code generation tasks.

References

The references/ directory contains supplementary material like documentation, examples, or schema definitions that the agent can consult while executing the skill.

Adding MCP servers

If your power provides MCP tools, create an mcp.json file at the power root:

json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/mcp.schema.json",
  "mcpServers": {
    "supabase-local": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@supabase/mcp-server-supabase"],
      "env": {
        "SUPABASE_URL": "${SUPABASE_URL}",
        "SUPABASE_ANON_KEY": "${SUPABASE_ANON_KEY}"
      }
    }
  }
}

Use environment variables for API keys and secrets. During installation, Kiro automatically namespaces server names to avoid conflicts (e.g., supabase-local becomes power-supabase-supabase-local).

Directory structure

Here's what a complete power looks like:

power-supabase/
├── plugin.json                           # Required manifest
├── mcp.json                              # MCP server configuration
└── skills/                               # Agent Skills
    ├── setup/
    │   ├── SKILL.md
    │   └── scripts/
    │       └── validate-deps.sh
    └── migrations/
        ├── SKILL.md
        └── references/
            └── migration-patterns.md

Testing locally

Create your power directory with the files above
Open Kiro → Powers panel → Add Custom Power
Select Import power from a folder
Select your power directory
Test activation by using keywords from your power in a conversation

Push your power to a public GitHub repository:

bash

git init
git add plugin.json mcp.json skills/ dev.kiro/
git commit -m "Initial release"
git push origin main

Others can install it via Add Custom Power → Import power from GitHub using your repository URL.

Examples

Minimal power (manifest only):

power-simple-tool/
├── plugin.json           # Keywords and description
└── mcp.json              # MCP server configuration

Skills-only power (no MCP):

power-react-patterns/
├── plugin.json
└── skills/
    ├── component-patterns/
    │   └── SKILL.md
    └── hooks-patterns/
        └── SKILL.md

Full power with all components:

power-full-stack/
├── plugin.json
├── mcp.json
└── skills/
    ├── setup/
    │   ├── SKILL.md
    │   └── scripts/
    └── deployment/
        ├── SKILL.md
        └── references/

Agent Plugins specification - The open standard powers are built on
Powers overview - What powers are and how they work
Install powers - Install from the marketplace or GitHub
Skills - Standalone portable instruction packages
MCP configuration - MCP server configuration reference

Page updated: August 4, 2026

Install powers

Cloud sessions

View our curated powers at kiro.dev/powers

What you need

Every power needs a plugin.json manifest. Optionally, you can add:

skills/ — Agent Skills with task-specific instructions
mcp.json — MCP server configuration for tool integrations

Creating plugin.json

Your plugin.json manifest identifies the power and tells Kiro when to activate it. At minimum, it requires:

json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "supabase",
  "version": "1.0.0",
  "description": "Build fullstack applications with Supabase's Postgres database, authentication, storage, and real-time subscriptions",
  "author": {
    "name": "Supabase"
  },
  "keywords": ["database", "postgres", "auth", "storage", "realtime", "backend", "supabase", "rls"]
}

Required fields

Field	Description
`$schema`	Schema URL: `https://agent-plugins.org/schemas/1.0.0/plugin.schema.json`
`name`	Plugin identifier (kebab-case, no spaces). Used internally by Kiro to identify the power.
`version`	Semantic version of the power (e.g., `1.0.0`).
`description`	Short description of what the power does.
`author`	Object with at minimum a `name` field. Can also include `email` and `url`.
`keywords`	Array of strings that trigger activation. Use terms that match how developers talk about your tool.

When someone says "Let's set up the database," Kiro sees "database" in the keywords and activates the Supabase power. The power's MCP tools and skills load into context automatically.

Optional fields

You can also include these fields in your manifest:

json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "supabase",
  "version": "1.0.0",
  "description": "Build fullstack applications with Supabase",
  "author": {
    "name": "Supabase",
    "url": "https://supabase.com"
  },
  "keywords": ["database", "postgres", "supabase"],
  "homepage": "https://supabase.com/docs",
  "repository": "https://github.com/supabase/kiro-power",
  "license": "Apache-2.0"
}

Adding skills

Skills are instructions that guide the agent through specific tasks. Each skill lives in its own directory under skills/ and requires a SKILL.md file.

skills/
└── setup/
    ├── SKILL.md
    ├── scripts/
    │   └── validate-setup.sh
    └── references/
        └── schema-patterns.md

SKILL.md

The SKILL.md file contains the instructions the agent follows when the skill is invoked. Structure it with clear steps:

markdown

---
name: setup
description: Set up a new Supabase project with local development
---

# Set up Supabase

## Step 1: Validate dependencies

Before using Supabase, ensure the following are installed:
- **Docker Desktop**: Required for the local development stack
  - Verify with: `docker --version`
- **Supabase CLI**: Install via npm or Homebrew
  - Verify with: `supabase --version`

## Step 2: Initialize the project

Run `supabase init` to create the project configuration.

## Step 3: Start local services

Run `supabase start` to spin up the local Supabase stack.

Scripts

The scripts/ directory holds executable files the agent can run during skill execution. Use scripts for validation, setup automation, or code generation tasks.

References

The references/ directory contains supplementary material like documentation, examples, or schema definitions that the agent can consult while executing the skill.

Adding MCP servers

If your power provides MCP tools, create an mcp.json file at the power root:

json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/mcp.schema.json",
  "mcpServers": {
    "supabase-local": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@supabase/mcp-server-supabase"],
      "env": {
        "SUPABASE_URL": "${SUPABASE_URL}",
        "SUPABASE_ANON_KEY": "${SUPABASE_ANON_KEY}"
      }
    }
  }
}

Directory structure

Here's what a complete power looks like:

power-supabase/
├── plugin.json                           # Required manifest
├── mcp.json                              # MCP server configuration
└── skills/                               # Agent Skills
    ├── setup/
    │   ├── SKILL.md
    │   └── scripts/
    │       └── validate-deps.sh
    └── migrations/
        ├── SKILL.md
        └── references/
            └── migration-patterns.md

Testing locally

Create your power directory with the files above
Open Kiro → Powers panel → Add Custom Power
Select Import power from a folder
Select your power directory
Test activation by using keywords from your power in a conversation

Push your power to a public GitHub repository:

bash

git init
git add plugin.json mcp.json skills/ dev.kiro/
git commit -m "Initial release"
git push origin main

Others can install it via Add Custom Power → Import power from GitHub using your repository URL.

Examples

Minimal power (manifest only):

power-simple-tool/
├── plugin.json           # Keywords and description
└── mcp.json              # MCP server configuration

Skills-only power (no MCP):

power-react-patterns/
├── plugin.json
└── skills/
    ├── component-patterns/
    │   └── SKILL.md
    └── hooks-patterns/
        └── SKILL.md

Full power with all components:

power-full-stack/
├── plugin.json
├── mcp.json
└── skills/
    ├── setup/
    │   ├── SKILL.md
    │   └── scripts/
    └── deployment/
        ├── SKILL.md
        └── references/

Agent Plugins specification - The open standard powers are built on
Powers overview - What powers are and how they work
Install powers - Install from the marketplace or GitHub
Skills - Standalone portable instruction packages
MCP configuration - MCP server configuration reference

Page updated: August 4, 2026

Install powers

Cloud sessions

Create powers

Create powers

What you need

Creating plugin.json

Required fields

Optional fields

Adding skills

SKILL.md

Scripts

References

Adding MCP servers

Directory structure

Testing locally

Sharing your power

Examples

Related documentation

What you need

Creating plugin.json

Required fields

Optional fields

Adding skills

SKILL.md

Scripts

References

Adding MCP servers

Directory structure

Testing locally

Sharing your power

Examples

Related documentation