[FEATURE] Skills/Bash tool: provide a mechanism for interactive stdin input (e.g. setup wizards)

Summary

When a skill runs a setup script that uses read for interactive prompts, the Bash tool has no stdin and the script fails. There's currently no way for a skill to programmatically trigger user input mid-execution.

Request

Add a way for skills (or Bash commands) to request input from the user — either via:

• A modal in the Claude Code UI triggered from within a Bash execution
• A dedicated tool (similar to AskUserQuestion) that is accessible from within a running Bash script (e.g. via a helper CLI like claude-ask "Your vault name:")
• A stdin pipe mechanism that routes terminal input to the Bash tool

Use case

The atlassian skill has a setup.sh that walks users through configuring their password manager. It works great when run manually in a terminal, but cannot be invoked by Claude because read receives no stdin and the script exits immediately with invalid input.

The current workaround is to have Claude collect answers in chat and write the config file itself — which works but bypasses the script entirely, meaning the script only works for humans running it manually and can't be used as part of an automated skill flow.

Expected behavior

A skill should be able to define a setup wizard as a shell script and have Claude run it, with user input flowing through in a way that works in both the Claude Code Bash tool context and a regular terminal.