Permission prompt for Skill tool should show which skill is being invoked

Summary

When Claude invokes the Skill tool, the permission prompt displays:

Allow Claude to use Skill ?

This gives the user no context about which skill is about to run. Compare this to the Bash tool, which shows the actual command:

Allow Claude to run lsof -ti:3000 ?

Expected behavior

The prompt should include the skill name, e.g.:

Allow Claude to use Skill(editor-start) ?

This is consistent with how Bash already surfaces its argument, and gives users the context they need to make an informed allow/deny decision — especially when skills are invoked automatically (e.g. via a CLAUDE.md instruction at session start).

Why it matters

Skills can be invoked automatically without any user action (e.g. a global ~/.claude/CLAUDE.md that says "run /editor-start at the start of every conversation"). When that happens, the user sees a generic "Skill ?" prompt with no indication of what's about to run. The only safe response is to allow everything or investigate manually — neither is great UX.

Suggested fix

Include the skill/command name in the permission prompt display string, the same way Bash includes its command argument. The tool already receives the skill name as a parameter, so this should be a small display-layer change.