Slash commands: tool studio wiring for tools, MCP, skills, providers, and previews

[Hmbown]

Scope

Make tool-facing slash commands feel like a coherent tool studio instead of separate subprocess/config paths.

Command families in scope:

• Tool and extension surfaces: /mcp, /skills, /skill, /review, /attach, /share
• Provider/model/config surfaces that affect tools: /provider, /model, /models, /config, /settings, /profile
• Tool telemetry and preview affordances: /cache, future /dryrun, command palette previews where useful

Acceptance

• Tool commands expose previews, dependency probes, approval shape, and resulting state where relevant.
• MCP/skills/provider commands share consistent validate, reload, enable/disable, and error display patterns.
• Config-affecting commands report persistence target and live-engine synchronization status.
• Command palette entries are accurate enough to act as the front door for tool discovery.

Related: #1004, #1409, #1847, #1802, #1822, #1794, #1172, #1092, #453.

[Hmbown]

Implementation notes for the next agent:

Primary files to inspect:

• crates/tui/src/commands/mcp.rs, skills.rs, review.rs, attachment.rs, provider.rs, config.rs, share.rs.
• Tool registry and schemas under crates/tui/src/tools/, especially strict schema work.
• crates/tui/src/tui/command_palette.rs, provider/model picker code, MCP manager UI, and approval UI.

Suggested tool-studio shape:

enum ToolStudioSurface { Mcp, Skill, Review, Attachment, Share, Provider, Model, Config, Cache, DryRun }

struct ToolStudioCommandState {
    command: String,
    surface: ToolStudioSurface,
    preview: Option<ToolPreview>,
    dependency_status: Vec<DependencyProbe>,
    approval_shape: Option<ApprovalShape>,
    live_engine_sync: Option<SyncStatus>,
    persistence_target: Option<PathBuf>,
}

fn classify_tool_studio_command(name: &str) -> Option<ToolStudioSurface> {
    match name {
        "mcp" => Some(ToolStudioSurface::Mcp),
        "skills" | "skill" => Some(ToolStudioSurface::Skill),
        "review" => Some(ToolStudioSurface::Review),
        "attach" => Some(ToolStudioSurface::Attachment),
        "share" => Some(ToolStudioSurface::Share),
        "provider" => Some(ToolStudioSurface::Provider),
        "model" | "models" => Some(ToolStudioSurface::Model),
        "config" | "settings" | "profile" => Some(ToolStudioSurface::Config),
        "cache" => Some(ToolStudioSurface::Cache),
        "dryrun" => Some(ToolStudioSurface::DryRun),
        _ => None,
    }
}

Design notes:

• Prefer one shared validate/preview/apply language across MCP, skills, providers, and config.
• If a command writes settings, show the file path and whether the running engine accepted the live update.
• If a command depends on an external executable or network capability, surface the probe result before the action where possible.
• Command palette entries should be strong enough to act as the discovery UI for tool capabilities.