Support custom icons, skills listing, and private/enterprise power registries

[kadusalles]

Kiro Product

IDE

Feature Description

Summary

Three related enhancements that would significantly improve the power ecosystem for enterprise teams and community authors:

1. Custom icon support in POWER.md frontmatter
2. Skills installation and registration for community/local powers
3. Private power registry / catalog configuration

---

1. Custom Icon for Powers

Problem

Currently, power icons are served exclusively from prod.download.desktop.kiro.dev/powers/icons/{name}.png. Only curated/partner powers get icons — community and local powers display a generic placeholder. There is no way for power authors to provide a custom icon.

Proposal

Add an icon field to the POWER.md frontmatter that accepts either a relative path to a local image file or an HTTPS URL:

---
name: "my-power"
displayName: "My Power"
icon: "./assets/icon.png"       # relative to power root
# or
icon: "https://example.com/icon.png"  # remote URL
---

The resolution order could be:

1. CDN icon (for curated powers, backward compatible)
2. Frontmatter icon field (local file or URL)
3. Default placeholder

---

2. Skills Support for Community/Local Powers

Problem

Powers can include skills (defined in skills/*/SKILL.md), but when installing a community or local power, Kiro does not install or register the skills bundled with it. The skills directory is simply ignored during installation. Only curated/partner powers seem to have their skills recognized.

This means power authors cannot distribute skills as part of their powers — the skills/ directory structure documented in the power ecosystem is effectively non-functional for non-curated powers.

Proposal

When installing a power (from GitHub URL or local path), Kiro should:

1. Detect the skills/*/SKILL.md files in the power directory
2. Register them so they appear in the agent's available skills list
3. Display them in the power details panel (name, description, activation trigger)
4. Uninstall them when the power is removed

This would make skills a first-class distributable component of any power, not just curated ones.

---

3. Private Power Registry / Catalog

Problem

Enterprise teams building internal powers have no way to set up a private catalog or registry. The only options are:

• Install from a public GitHub URL
• Install from a local path

Neither scales well for organizations with dozens of powers across multiple teams. There is no centralized discovery, versioning, or governance mechanism for private powers.

Proposal

Support configurable power registries, similar to how npm supports private registries or how container registries work. For example, a workspace or user-level configuration:

// .kiro/settings/powers.json or similar
{
  "registries": [
    {
      "name": "company-internal",
      "url": "https://git.internal.company.com/kiro-powers",
      "type": "github-enterprise"
    },
    {
      "name": "team-powers",
      "url": "https://artifactory.company.com/kiro-powers",
      "type": "generic"
    }
  ]
}

This would enable:

• Centralized discovery: browse internal powers from the IDE panel alongside curated ones
• Version management: track and update internal powers across the organization
• Access control: leverage existing Git/artifact repository permissions
• Governance: teams can curate and approve powers before making them available

The registry could be as simple as a Git repository with an index file listing available powers and their repository URLs, or a more structured API.

Use Case

We are building internal powers for our engineering organization that package company-specific MCP servers, steering files, skills, and workflows. Today we have to distribute them manually via local paths or internal Git URLs shared in documentation. A proper registry + better metadata (icons, skills) would make the power ecosystem viable for enterprise adoption.

Additional Context

Environment:

• Kiro IDE 0.7+
• Linux / macOS / Windows

[github-actions]

Thanks for opening this issue and putting together such a thoughtful, well-structured proposal! The ideas around custom icon support, skills registration for community powers, and private registry configuration would be great enhancements for both enterprise teams and community power authors. A maintainer will review this shortly and follow up. We really appreciate you taking the time to detail these improvements — this kind of feedback helps shape the power ecosystem for everyone! 🚀

[AndrewFarley]

1000% need this so we can as an individual or team author powers and keep them internal on self/internally hosted SCM servers

[AnilMaktala]

We're doing a periodic backlog review and noticed this issue has been inactive for several months. Kiro has shipped a lot of changes since this was filed — we're now on IDE 1.0.309 and CLI 2.18.1 — and without any community uptake, we can't confidently prioritize it.

Closing to keep the backlog focused, but not as a dismissal. If you're still seeing this or others share the same experience, a new issue with your current version and any updated details would help us pick it back up. Issues with 👍 reactions from the community rise to the top fastest.