Glean skills, agents, and auto agents: When to use each - Glean Tutorial

By this point at the series, we've looked at a few ways to get stronger outputs out of Glean. As people start to look for ways to automate this work, they usually run into a slightly more nuanced question. When should I use a skill and when should I build an agent? Here's the simplest way to think about it. A skill captures expertise. It's best when you want Glean to follow a general approach, but still use its broader judgment. It can draw from all of the knowledge and tools Glean has access to, and decide what's most useful without being told exactly what to do. Skills are also reusable. The same skill applies across many situations and teams. Build it once and every workflow that needs it can use it. A good example is helping teams write client emails in a consistent style across your whole company. And importantly, a skill gives Glean guidance, not constraints. You set a general direction, Glean still has the flexibility to find the best route and choose what's most helpful. An…