Free to read · no account needed

9 min · plugins

Skills, MCP, and plugins — the stack in plain words

Goal: One beginner table for plugins, skills, and MCP connectors—what each does, one example, main risk—then propose the thinnest stack.

Best for: Beginners who saw Skills / MCP / Plugins in release notes.

Add one layer at a time. Inventory what you installed.

Plugins, skills, and MCP are layers—not synonyms. Pick the thinnest layer that does the job; stack only when a weekly workflow needs all three.

Why beginners skip this

Turning on plugins, skills, and MCP together feels complete—debugging cannot tell who moved. Run one channel first.

Step 1 — Three layers

  • Skill = the playbook (how to do the job).
  • MCP = a way for the AI to use outside tools/data (mail, docs, calendars) through a standard door.
  • Plugin = an installable bundle that can include skills and/or MCP connections — like an app pack.

Step 2 — Cooking metaphor

Keep the kitchen metaphor: do not mix “seasoning” with stove permissions.

LayerKitchen metaphor
SkillRecipe card
MCP toolsStove, fridge, delivery app — real appliances
PluginMeal kit box with recipe + coupons to appliances

You can use a recipe alone (skill in a Project). You only open appliances (MCP) when the job needs live data or actions — and you keep Ask-before-act on.

Step 3 — Beginner order

  • 1) Write a clear prompt pattern (Goal / Format / Boundaries).
  • 2) Save it as Project instructions or a skill draft.
  • 3) Only then connect one safe, read-mostly MCP tool.
  • 4) Install a plugin when you want a maintained bundle — still review permissions.
Example

Filled prompt

I have: 1 Custom GPT, 2 skills, 1 MCP Drive read.
Draw a one-page stack map: which job uses which layer. Flag overlap. Recommend one thing to uninstall this week.

What good output looks like

  • One-page map: Custom GPT / skills / MCP Drive each tied to a named job
  • Flags overlap where two layers claim the same weekly task
  • Recommends one concrete uninstall or disconnect for this week
  • Keeps MCP on read-mostly—no silent Gmail send added
  • Beginner can act from the map without a protocol essay
Example

Filled prompt

Inventory GPT+2 skills+Drive MCP.
One-page map jobs→layer. Uninstall one overlap this week.
Context: real workstream this week (Asia/Shanghai). Name actual files/people.
Constraints: no invented metrics/owners/prices; label Unknowns; stop before send/delete/pay.
Done check: I can mark pass/fail in one minute on the output.

What good output looks like

  • Proposes skill/Project instructions only for notes → bullets
  • Calendar stays draft-in-chat; no auto-create events yet
  • Explicit “do not connect Gmail send / Drive write this month”
  • Stack fits on one sticky note—no three-year architecture diagram
  • Ask-before-act called out if any connector is added later

Save this card

Card: Skills = playbooks · Plugins = install surface · MCP = channel. Name which layer owns send/delete before you stack.

Before you start

Open the listing and a notes doc. Score purpose/scopes/uninstall for “See how the three layers fit so new product” before Install. Prefer wait over Always allow. Guide: plugins-skills-mcp-stack. Keep the real job visible the whole time; a blank box means stop and fetch the artifact first.

How to use this week

This week pick one channel (plugin / skill / MCP) and finish one real job; then note why you did not pick the other two.

Thinnest layer wins

Prefer the smallest layer that does the weekly job. Stack only when needed.

One job, one layer

If you need “and” to describe why you installed something, you are stacking early. A skill that shapes notes is enough for many weeks; MCP calendar write is a later promotion with Ask-before-act still on.

Example

Filled prompt

Map: Custom GPT (FAQ) · skill (status) · MCP Drive read.
Find one overlap to uninstall this week. One-page stack map.
Context: real workstream this week (Asia/Shanghai). Name actual files/people.
Constraints: no invented metrics/owners/prices; label Unknowns; stop before send/delete/pay.
Done check: I can mark pass/fail in one minute on the output.

What good output looks like

  • Eval score written before install for “See how the three layers fit so new product names ”
  • Uninstall path and scopes listed
  • No always-allow on write/send
  • Pass/fail: keep-or-remove decision dated

Red flag

Unclear which layer owns send/delete; stacking all three with no job—draw the layers first.

Pitfalls

PitfallFix
Installing everything at onceOne layer at a time
MCP write tools before skills hygieneSkills/docs first; MCP least privilege
No inventory of what you installedKeep a one-page stack map
Example

Filled prompt

Temptation: skip the habit for plugins-skills-mcp-stack to save five minutes.
Job still: See how the three layers fit so new product
Smallest correct pass: Done visible · checkable artifact · Unknowns [?].
Boundaries: draft only; no silent send; no invented metrics.
Return: artifact + refuse-line said aloud.

What good output looks like

  • Names the shortcut refused (specific to plugins-skills-mcp-stack)
  • Still delivers checkable output for “See how the three layers fit so new product”
  • Unknowns labeled; draft-only
  • Pass/fail: refuse-line dated (plugins-skills-mcp-stack #4)

Practice now

Retirement line: name what you will uninstall if unused 30 days (Asia/Shanghai).

Cost-of-layer: estimate minutes each layer adds tonight (Asia/Shanghai).

Delete-one: remove one unused layer from the diagram (Asia/Shanghai).

Layer-order drill: decide plugin→skill→MCP order for one job; write why (Asia/Shanghai).

One-layer drill: solve the job with one layer only first (Asia/Shanghai).

Stack drill: draw plugin vs skill vs MCP for one job in three bullets (Asia/Shanghai).

Thin-spot drill: rewrite the Save card with real nouns from your work (repo, doc, inbox). Generic placeholders fail the drill.

Tonight enable only one layer (plugin or skill or MCP), run one real job through, then add the next layer.

Close the loop

Write one line: next time I turn on all three channels at once, I refuse to run.

One sentence takeaway

One channel first; then note why not the other two.

Next

MCP · Skill

← Back to home · Learn · Tools · Compare · Start