Nufar Gaspar

verify the source, read it very carefully and treat it like installing any software package on your machine.

And especially if it's a work machine, be very careful and pay attention so you will not bring any malicious software back into your organization.

All right, so this is the basic.

Let's talk about when to build skills.

So the question is, when should you build skills?

And I wanted to start with three obvious signals.

Either when you do something more than three times, that to me is a good indication that now is a good time to build a skill.

Or you keep basically pasting the same instructions and getting very frustrated with your tool.

And that's another good one.

And also when you need a consistent output.

But the two additional things that you want to consider, first of all, this is a great opportunity to standardize things across either the way you do the work or others do the work with you.

It's a great opportunity for you to think of all the things that you ever wanted to be more consistent of or get more consistent behavior by others and just build a skill to get others to behave the same way.

And lastly, and that's something that often also NLW talks about,

Skills are not just a way for you to be more productive.

It's also a way for you to unlock opportunities of things that you always wanted to do and just didn't have the bandwidth or the ability to do so.

So think outside the box of what are some of the research tasks that you never had the opportunity to do or what are some of the work and business challenges that you could never, ever solve because you didn't have the know-how and the bandwidth.

Okay.

I want to talk about two other things.

One is that skills cannot be 10 different things.

So one skill per task, if you find yourself getting to a point where it's completely separate jobs, separate them to different skills.