/design is user-only (disable-model-invocation), but the agent isn't told it exists or that the Design canvas is reachable another way

Status Open
Reported on v2.1.293
Maintainer reply None cached
Activity 0 comments · opened Oct 11, 2026

Where: Claude desktop app, Code tab (engine 2.1.293, macOS).

What happens. The user asks the agent to «run /design». The agent's Skill tool refuses: Skill design cannot be used with Skill tool due to disable-model-invocation. Ask the user to run /design themselves. Before that, the agent had told the user the command didn't exist, because /design never appears in the agent's skill listing. Yet the Design canvas that /design opens is an Artifact type the agent can reach directly through the Artifact tool (action: "quickstart", intent: "design"). When the user ran /design, it routed to exactly that.

So the user gets a detour, and a wrong «it doesn't exist», for something the agent could have done itself.

Asks

  1. When a skill is user-only, have the refusal name what the agent can use instead (here: the Design Artifact type via quickstart).
  2. List user-only commands to the agent, marked as user-only, so it never says a command doesn't exist.
  3. Consider allowing model invocation of /design, since its effect is already reachable by the agent.

Related, from the other side: #92769 (user-only plugin skills hidden from the user's own list).

View original on GitHub ↗