Context
Amazon Kiro IDE has a "Powers" system that is conceptually very similar to Claude Code Skills. Both use a Markdown file with YAML frontmatter as the definition format. Since our Risk Radar skills (/risk-assess, /risk-mitigate) are already structured as SKILL.md files, adding Kiro Power equivalents would be straightforward.
Kiro Powers Format
power-name/
├── POWER.md # Metadata + instructions (like SKILL.md)
├── mcp.json # Optional MCP server config
└── steering/ # Optional workflow-specific files
POWER.md frontmatter:
---
name: "risk-assess"
displayName: "Vibe-Coding Risk Assessment"
description: "Analyze repository to assess vibe-coding risk per module"
keywords: ["risk", "security", "vibe-coding", "assessment", "tier"]
---
Key difference: Kiro Powers activate automatically via keywords (e.g. mentioning "risk assessment" loads the power), while Claude Code Skills are invoked explicitly.
Tasks
References
Context
Amazon Kiro IDE has a "Powers" system that is conceptually very similar to Claude Code Skills. Both use a Markdown file with YAML frontmatter as the definition format. Since our Risk Radar skills (
/risk-assess,/risk-mitigate) are already structured asSKILL.mdfiles, adding Kiro Power equivalents would be straightforward.Kiro Powers Format
POWER.md frontmatter:
Key difference: Kiro Powers activate automatically via keywords (e.g. mentioning "risk assessment" loads the power), while Claude Code Skills are invoked explicitly.
Tasks
POWER.mdfor risk-assess (adapt from existingSKILL.md)POWER.mdfor risk-mitigate (adapt from existingSKILL.md)keywordsfield for automatic activationsteering/files for the multi-step workflowsinstall-skills.shor create separateinstall-powers.shReferences