Description
When a skill specifies model: haiku in its frontmatter (e.g. queue-status), invoking it via the Skill tool returns only "Launching skill: <name>" — the sub-agent output never flows back to the caller's context.
Skills without a model field load their content inline correctly and work as expected.
Steps to reproduce
- Invoke
ops-suite:queue-status via the Skill tool
- Observe the tool result:
"Launching skill: ops-suite:queue-status" (nothing else)
- No subsequent output from the sub-agent arrives in the conversation
Expected behavior
The sub-agent (Haiku) should execute the skill steps and return results to the calling conversation, or the skill content should be loaded inline so the caller can follow it.
Actual behavior
Tool returns only the launch confirmation. No queue data, no errors — silent failure.
Environment
- Plugin:
ops-suite v0.3.0
- Affected skill:
queue-status (and likely any skill with model: haiku)
- Claude Code version: current
- Skill frontmatter that triggers the issue:
model: haiku
allowed-tools:
- Bash
- AskUserQuestion
Workaround
Read SKILL.md manually and follow the steps inline with the current model.
Description
When a skill specifies
model: haikuin its frontmatter (e.g.queue-status), invoking it via theSkilltool returns only"Launching skill: <name>"— the sub-agent output never flows back to the caller's context.Skills without a
modelfield load their content inline correctly and work as expected.Steps to reproduce
ops-suite:queue-statusvia theSkilltool"Launching skill: ops-suite:queue-status"(nothing else)Expected behavior
The sub-agent (Haiku) should execute the skill steps and return results to the calling conversation, or the skill content should be loaded inline so the caller can follow it.
Actual behavior
Tool returns only the launch confirmation. No queue data, no errors — silent failure.
Environment
ops-suitev0.3.0queue-status(and likely any skill withmodel: haiku)Workaround
Read
SKILL.mdmanually and follow the steps inline with the current model.