AWS Builder Center

A guide for migrating Claude Code Skills to Kiro Powers.

This is a step-by-step opinionated guide for converting Claude Skills to Kiro Custom Powers

Why this guide? The Claude Code community has created valuable Skills that package domain expertise, and this guide helps you bring that knowledge into Kiro while taking advantage of Powers' enhanced capabilities like MCP server integration.

Overview

Claude Skills are markdown-based knowledge packages for Claude Code (IDE extension), while Kiro Powers are similar packages for Kiro (standalone IDE) that can additionally bundle MCP servers and tools, making Powers more comprehensive by combining documentation, workflows + best practices, and executable capabilities in one package.
Claude Skills and Kiro Powers serve a similar purpose: packaging domain knowledge and workflows for AI assistants. The conversion is straightforward because both use markdown-based documentation with progressive disclosure patterns.

Structural Mapping

Claude Skill
Kiro Power
Purpose
 SKILL.md 
 POWER.md 
Core documentation (always loaded)
 references/*.md 
 steering/*.md 
Deep-dive content (loaded on-demand)
 .claude-plugin/marketplace.json 
POWER.md frontmatter
Metadata (name, description, keywords)
 CLAUDE.md 
 steering/contributing-guidelines.md  or  steering/development-guide.md  or  steering/maintenance-notes.md 
Contributor docs (optional)
 README.md 
Not needed
User-facing docs (handled by Powers UI)

Step-by-Step Conversion

Step 1: Create Directory Structure

mkdir -p powers/{power-name}/steering

Step 2: Convert SKILL.md → POWER.md

Add Kiro frontmatter at the top of your SKILL.md content:
---
name: "power-name"
displayName: "Human Readable Name"
description: "Clear description (max 3 sentences)"
keywords: ["keyword1", "keyword2", "keyword3"]
author: "Your Name"
---
Frontmatter rules:
  •  name : lowercase kebab-case
  •  displayName : Title Case for display
  •  description : What the power does and why it's useful
  •  keywords : 5-7 specific terms for discovery (avoid generic words like "help", "tool")
  •  author : Creator name

Step 3: Add Steering Files Section

Add this section to POWER.md listing available steering files:
## Available Steering Files

- **file-name** - Description of what this file covers
- **another-file** - Description of content

Step 4: Copy Reference Files to Steering

cp references/*.md steering/

Step 5: Update Internal Links

Replace all internal references:
Find
Replace
 references/ 
 steering/ 
 ../SKILL.md 
Main POWER.md
 [Main Skill File](../SKILL.md) 
Main POWER.md

Step 6: Extract CLAUDE.md Content (Optional)

If your skill has a CLAUDE.md with contributor guidelines, extract useful content:
Keep:
  • Content philosophy (what belongs, what doesn't)
  • Writing style guidelines
  • Quality standards checklists
  • Update criteria
Discard:
  • Claude-specific installation instructions
  • Token budget calculations (optional)
  • Claude Code marketplace references
Save as  steering/contributing-guidelines.md .

Step 7: Add Attribution

Include proper attribution in POWER.md:
## License & Attribution

**License:** [Original License]

**Power Author:** [Your Name]

**Original Work:** This power is inspired by [original-skill](https://github.com/...) by [Original Author].

**Source Version:** Based on [version/commit reference].

**Update Frequency:** This power will be updated periodically.

What to Remove

  •  .claude-plugin/  directory (metadata moves to frontmatter)
  •  README.md  (Powers UI handles discovery)
  •  CHANGELOG.md  (optional, not used by Kiro)
  • Claude-specific instructions in documentation

What to Keep

  • All technical content from SKILL.md
  • All reference documentation
  • Code examples and patterns
  • Decision matrices and flowcharts
  • ✅/❌ pattern examples

Validation Checklist

Before testing:
  • [ ] POWER.md has valid frontmatter (name, displayName, description)
  • [ ] Keywords are specific, not generic
  • [ ] All steering files are listed in "Available Steering Files" section
  • [ ] Internal links updated from  references/  to  steering/ 
  • [ ] Back-links to SKILL.md removed or updated
  • [ ] Attribution section includes original author and source version
  • [ ] No Claude-specific installation instructions remain

Testing Your Power

  1. Open Kiro Powers panel
  1. Click "Add Custom Power"
  1. Select "Local Directory"
  1. Enter full path to your power directory
  1. Click "Add"
Test queries:
  • Ask about topics covered in POWER.md
  • Request deep-dive content (should load steering files)
  • Verify keywords trigger power activation

Example Conversion

This methodology was tested by converting Anton Babenko's popular  terraform-skill  (from  terraform-best-practices.com  |  Compliance.tf ) into a Kiro Power.
Tip: Use the Kiro "Build a Power" power to help streamline this conversion process.
Before (Claude Skill):
terraform-skill/
├── .claude-plugin/
│ └── marketplace.json
├── SKILL.md
├── CLAUDE.md
├── README.md
└── references/
├── testing-frameworks.md
└── module-patterns.md
After (Kiro Power):
terraform-best-practices/
├── POWER.md
└── steering/
├── testing-frameworks.md
├── module-patterns.md
└── contributing-guidelines.md

Key Differences

Aspect
Claude Skills
Kiro Powers
Metadata location
 .claude-plugin/marketplace.json 
POWER.md frontmatter
Reference files
 references/ 
 steering/ 
MCP integration
Separate concern
Can include  mcp.json 
Distribution
Claude marketplace
Local directory, Git repo, or Kiro marketplace

Publishing Your Power

Local testing:
/full/path/to/powers/power-name
Git repository: Push to public GitHub repo, users add via repo URL.
Before sharing:
  • Sanitize any sensitive values
  • Document placeholders users need to replace
  • Include clear attribution to original work
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article