Support configurable skill/steering path (kiro.additionalSkillPath)

[SengarPrashant]

Kiro Product

IDE

Feature Description

By default, Kiro looks for the .kiro folder to access skills, steering files, and other configurations. As a result, developers need to copy the same skills into every workspace they work on.

The kiro.additionalSkillPath setting allows developers to configure a custom or centralized location for skills. Kiro can then reference skills directly from this shared path, eliminating duplicate copies across multiple workspaces.

Use Case

I have created an Marketplace extension for my organization which connects to internal skill/steering repos and enables developers to browse skills / profiles(combination of skills steering, hooks etc) and install it.

By default, Kiro looks for the .kiro folder to access skills, steering files, and other configurations. As a result, developers need to copy the same skills into every workspace they work on.

The kiro.additionalSkillPath setting allows developers to configure a custom or centralized location for skills. Kiro can then reference skills directly from this shared path, eliminating duplicate copies across multiple workspaces.

Additional Context

No response

[github-actions]

Thanks for opening this issue! 🎉 The idea of supporting a configurable path for skills and steering files so they can be shared across workspaces instead of duplicated is a really compelling one — especially for teams managing centralized skill repositories. A maintainer will take a look at this soon. Great suggestion, and we appreciate you thinking about how to make the Kiro experience better for organizations!