Your assistant comes with a bunch of built-in capabilities. But the real magic? Teaching it new ones.
Skills are how your assistant learns to do things. Think of them as plugins, but less boring.
A skill is a bundle of instructions and tools that gives your assistant a new capability. Some examples:
Skills can be simple (a single tool) or complex (multiple tools, configuration, and custom logic). Your assistant loads them on demand, so they don't slow anything down when they're not being used.
Your assistant came pre-loaded with a catalog of skills. Here's what's available right now:
| Skill | What it does |
|---|---|
| Email (AgentMail) | Send, read, search, and manage email from your assistant's own address |
| Google Calendar | View, create, and manage calendar events |
| Weather | Current conditions and multi-day forecasts |
| Image Studio | Generate and edit images using AI models |
| Messaging | Read and send messages across Slack, Gmail, Telegram |
| Browser | Navigate web pages, click things, extract content |
| DoorDash | Order food, groceries, and convenience items |
| Start the Day | Personalized daily briefing with weather, news, and tasks |
| App Builder | Create interactive HTML/CSS/JS apps on the fly |
| Claude Code | Delegate coding tasks to an AI coding agent |
You don't need to “activate” these. Just ask your assistant to do something and it'll load the right skill automatically. Ask for the weather? Weather skill loads. Ask it to check your email? Email skill loads. No setup menus. No toggle switches.
Let's start simple. Type this:
"What's the weather like in New York this week?"
Your assistant will:
You didn't configure an API key. You didn't enable a plugin. You just asked a question and got an answer. That's how skills are supposed to work.
This one requires a tiny bit of setup (your assistant needs its own email address), but it's worth it.
"Set up your email."
Your assistant will walk you through connecting to its email service. Once that's done:
"Check my email."
"Draft an email to john@example.com about the meeting tomorrow."
"Summarize the last 5 emails I got."
Your assistant reads and sends email from its own address, not yours. When someone receives an email from your assistant, they know it's from your assistant. Clear boundaries.
Beyond the built-in catalog, you can install additional skills:
"Show me available skills."
Your assistant will show you what's in the skill catalog. To install one:
"Install the [skill name] skill."
Skills are modular. Install what you need, ignore what you don't.
If you're technically inclined, you can build custom skills from scratch. Your assistant can even help you write them.
"I want to build a custom skill that checks Hacker News for the top stories every morning."
It'll write the code, test it in a sandbox, and (with your permission) save it as a proper skill you can use anytime.
This is a deeper topic. If you're curious, check out Building Custom Skills in the Guides section.
You used a skill without configuring it, saw your assistant load tools on demand, and maybe even set up email. That's the pattern:
No menus. No dashboards full of toggles. No “please configure your integration before proceeding.” Just ask and watch it work. That's the inviting principle: things show up when they're relevant, not before.
Next up: Key Concepts — how it all fits together under the hood. Or just keep talking to your assistant. It doesn't mind.