Workspace-Level Skills Not Working #6882
Description
Before opening, please confirm:
Operating System
darwin
Kiro Version
0.11.107
Bug Description
Bug Report:
Environment: Kiro on macOS
Issues:
Workspace skills not shown in Agent Steering & Skills panel The panel only shows a "Global" section. Skills placed in .kiro/skills/ within the workspace do not appear. There is no "Workspace" section in the panel at all.
Workspace skills not invokable via slash command A skill at
SKILL.md
cannot be invoked with /skill-from-masters in chat. Only skills in the global ~/.kiro/skills/ directory are invokable.
Inconsistent behavior on first load A skill placed in the global directory (~/.kiro/skills/test-skill/) was initially not invokable via /test-skill, then started working without any changes made. Suggests a possible indexing/reload delay with no user feedback.
Expected behavior: Skills in .kiro/skills/ within a workspace should appear under a "Workspace" section in the Agent Steering & Skills panel and be invokable via slash command, consistent with how global skills work.
Workaround: Copy skills to ~/.kiro/skills/ for them to be recognized.
Steps to Reproduce
Steps to Reproduce:
Issue 1 & 2: Workspace skills not shown or invokable
Open a workspace in Kiro
Create a skill file at
SKILL.md
with valid frontmatter (name, description) and content
Open the Agent Steering & Skills panel in the sidebar
Observe: no "Workspace" section appears — only "Global"
In the chat input, type /my-skill
Observe: skill is not suggested or invokable
Expected: Skill appears under a "Workspace" section and is invokable via /my-skill Actual: Skill is invisible and not invokable
Issue 3: Slash command not working on first install, then works without changes
Create a skill at ~/.kiro/skills/test-skill/SKILL.md
In chat, type /test-skill
Observe: skill is not invokable
Make no changes, wait or send another message
Try /test-skill again
Observe: now works
Expected: Skill is immediately invokable after creation with no reload required Actual: Skill requires an indeterminate delay or unknown trigger before becoming invokable
Credits used: 0.22
Elapsed time: 7s
Expected Behavior
Expected Behavior:
Issue 1 & 2: Workspace skills
Skills placed in .kiro/skills/ within a workspace should be recognized by Kiro automatically
They should appear in the Agent Steering & Skills panel under a "Workspace" section, separate from global skills
They should be invokable via slash command (e.g. /my-skill) in the chat input, identical to how global skills work
Workspace skills should take precedence over global skills if a name conflict exists
Issue 3: Skill indexing delay
A skill should be available immediately after its SKILL.md file is saved — no restart, reload, or waiting required
If there is a loading state, Kiro should show visible feedback (e.g. "indexing skills...") so the user knows it's not ready yet
Once ready, the slash command should work on the first attempt
Conversation ID
No response
Additional Context
No response