Plugins: Packaging Up and Borrowing

In short

A plugin is a box: it gathers skills, helpers, connections and automations.
It's there to let you install in one move what you'd otherwise build piece by piece.
For you, just starting out, the value is taking, not sharing.
The same caution as connections applies: a plugin brings in stuff that acts.

The problem of scattered work

Let's stop and look at what you've built over the course: an instructions file, a few skills, maybe a custom helper, a couple of connections. All of it scattered across different folders.

Now try answering three questions: how do you carry it to a new laptop? How do you give it to a colleague? And if you update it tomorrow, how do you get the update to them?

A plugin is the answer: a box that holds all those pieces together and makes them installable in one move.

What's inside

Nothing new, which is why this lesson comes at the end and not the start: a plugin contains things you already know how to use.

Skills, meaning procedures.
Custom helpers.
Connections to external tools.
And the automations from the next chapter, which we haven't covered yet.

A plugin isn't a new kind of thing: it's a container.

For you, at the start, it's about taking

The obvious reading is "great, now I can share my work." True, but it comes later — once you have something to share. At the start the value runs the other way: taking.

There are marketplaces, including official ones, full of plugins already built and already tested. In the desktop app you browse them from the + button next to the text box.

The reflex worth building is this: before building yourself a procedure from scratch, check whether someone's already done it. Worst case, you find an idea better than yours.

The same caution as connections

Installing a plugin isn't like reading an article: you're putting stuff that acts into your tool. Procedures that will be followed, helpers that will run, connections that will pull content in.

So: recognizable sources, and the same question as with permissions — what can this thing do, if I install it? Official marketplaces are the sensible starting point; a plugin found at random online deserves the same wariness as a random program found online.

And now

With this the fourth bucket is closed, and with it the map we drew back in chapter 2. In the next lesson an example, and then all that's left is level 2 of the first bucket: automations that trigger on their own at precise points in the loop.

Did you get it?

Two minutes, no grade. Trying to answer — even getting it wrong — cements the concepts far more than rereading. Not in the mood? Skip it: the lesson still counts as complete.

What can a plugin contain?

What's the most immediate benefit of plugins for you, just starting out?

1
1. 1
2. 2
3. 3
2
1. 4
2. 5
3. 6
4. 7
3
1. 8
2. 9
3. 10
4. 11
5. 12
4
1. 13
2. 14
3. 15
4. 16
5. 17
6. 18
5
1. 19
2. 20
3. 21
4. 22
5. 23
6. 24
6
1. 25
2. 26
3. 27
4. 28
5. 29
6. 30
7
1. 31
2. 32
3. 33
4. 34
8
1. 35
2. 36
3. 37
4. 38
9
1. 39
2. 40
3. 41
10
1. 42
2. 43
3. 44
11
1. 45
2. 46