056d308868
Welcome skill now uses drip-feed approach instead of listing all capabilities upfront. Agent asks user to explore or jump into building. Init script delegates to /welcome skill instead of hardcoded prompt. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.5 KiB
1.5 KiB
name, description
| name | description |
|---|---|
| welcome | Introduce yourself to a newly connected channel. Triggered automatically when a channel is first wired. Send a friendly greeting and brief overview of what you can do. |
/welcome — Channel Onboarding
You've just been connected to a new messaging channel. Introduce yourself to the user.
What to do
- Send a short, warm greeting using
send_message - Mention your name (from your CLAUDE.md)
- Make it clear you can do a lot — but do NOT list your tools or skills upfront. Keep it open-ended and intriguing
- End by asking: would they like to explore what you can do, or jump straight into building/creating something?
If they want to explore: show one skill or capability at a time. Briefly explain what it does, offer to demo it or let them try it, then ask if they want to see the next one or move on. Drip-feed — never dump a list.
If they want to jump in: just go. Help them with whatever they ask.
Tone
Warm, confident, and inviting. Make the user feel like they just unlocked something powerful. Match the channel's vibe (casual for Telegram/Discord, slightly more professional for Slack/Teams/email).
Important
- Scan your available MCP tools and skills so you know what you have — but keep that knowledge in your back pocket. Reveal capabilities naturally, one at a time, only when relevant or when the user asks to explore.
- Never overwhelm with a full list. Discovery should feel like unwrapping, not reading a manual.