Corey Knowles

There's like very deep configuration that you can push to your team.

Skills just being a small part of that.

And then you can like automate things so that they're like whatever you want, like whatever value you want is just provided.

We'll probably refine this because we haven't actually published our thinking on it.

There's just some PRs in the open source repo.

But my thinking is that connectors are basically ways to use other tools or gather context.

Great.

A skill, the way that I think about it, is actually more of a set of instructions that create a capability.

That capability might include a connector.

So an example would be, we might have a connector to, say, Sentry.

And so you could use the Sentry to identify crashes that you want to fix.

But the truth is, if I navigate to the Sentry website right now, I will have to do a ton of work to click around to get to my team's crashes.

And then I'll have to click around some more to get to which things I care about.

Right, so there's actually a bunch beyond the connector that I might want to prompt.

And so you could have a Sentry connector, you could have a Sentry skill like vaguely, but what I might really want on my team is I might want a skill that is like,

identify century crashes related to the most recent release specifically pertaining to the code that I wrote.

And then like plan, investigate changes and plan the fix.

And like, for me, all of that thing that I just said is like one skill.

So you're sending it to look specifically for your stuff.

Yeah.