Free to read · no account needed

10 min · plugins

Package a plugin for teammates

Goal: One page for teammates: plain-word permissions, clickable install, how to roll back, plus one read-only acceptance check.

Best for: you got something working and others need the same path.

A package teammates can install beats a genius folder only you understand. Include a one-page README and a revoke note. Packaging for beginners means: what it does, who should use it, permissions in plain words, install clicks, a shared test prompt, rollback, and who to ping when it breaks. Store it next to your team skill library.

Why beginners skip this

Packaging for teammates without uninstall and permissions feels light—when it breaks, nobody knows how to roll back. Checklist complete before ship.

Step 1 — Write the one-pager skeleton

Fill a one-pager skeleton: purpose, audience, permissions, install, test, rollback, owner—do not share without rollback.

Fill a teammate one-pager for [plugin/connector name].
Purpose · Who · Permissions (plain words) · Install clicks · Test prompt · Rollback · Owner
Keep under one screen. No jargon without a one-line gloss.
Example

Filled prompt

One-pager for company calendar connector used by PMs.
Permissions: read events only. Rollback = disconnect in Settings → Connectors.
Owner: Sam (ops).

What good output looks like

  • Permissions in plain words
  • Install is click-by-click
  • Rollback = disconnect steps a beginner can follow
  • Welcoming tone, one connector only—no stack pitch

Step 2 — Include a shared test prompt

Everyone runs the same read-only test after install; if results diverge, stop—do not open write yet.

Create a shared post-install test prompt for [name] that is read-only and proves access works.
Success = observable in under 2 minutes.
Example

Filled prompt

Ship "meeting-notes→actions" pack to 2 PMs.
Include: purpose, Done, never-do, install, uninstall, golden example with Unclear owners.
Secrets = placeholders only.

What good output looks like

  • Eval score written before install for “hand teammates a plugin/connector setup they can i”
  • Uninstall path and scopes listed
  • No always-allow on write/send
  • Pass/fail: keep-or-remove decision dated

Step 3 — Store it where people look

Put the one-pager beside the skill-library index and link it in onboarding; oral-only dies when you go on leave.

Draft a 4-line onboarding blurb pointing new hires to the connector one-pager.
Say when they need it and who owns it.
Example

Filled prompt

Package a "status polish" prompt pack for 3 teammates.
Include: purpose, Done, never-do, install steps, uninstall path, one golden example.
Ban secrets in the pack. Ask-every-time on send.

What good output looks like

  • Uninstall path and scopes listed
  • No always-allow on write/send
  • Pass/fail: keep-or-remove decision dated
  • Eval score written before install for “hand teammates a plugin/connector setup they can i”

One-pager is the product

If install needs a screen-share every time, you shipped a secret, not a package.

Do not bookmark-only

Finish Practice now, then tick this guide on your path. Titles unread are not skills.

Close the loop

Write one line: next time I ship with no uninstall path, I refuse.

Red flag

Packaging without uninstall and permissions leaves nobody able to roll back—checklist complete before ship.

Save this card

Card: A one-pager needs install, permissions, rollback—oral-only dies when you are offline. Keep this beside the tool; read before you start.

Wear-test: show your Save card to a teammate for thirty seconds—if they cannot restate the refuse line, tighten the card tonight and date it (Asia/Shanghai).

Before you start

Open the listing and a notes doc. Score purpose/scopes/uninstall for “hand teammates a plugin/connector setup they can install wit” before Install. Prefer wait over always-allow Guide: plugins-package-for-teammates Keep the live artifact visible the whole time. If you only have a blank box, stop and fetch the real job first

How to use this week

This week write a teammate pack for a real plugin: permissions, egress, uninstall path, maintainer; no ship if any item is missing.

Close the week by quoting aloud the refuse line you actually used once. If you cannot, rerun Practice now and date the pass/fail (Asia/Shanghai).

Pitfalls

PitfallFix
Oral-only setupWrite the one-pager
Different tests per personOne shared read-only test
No ownerName a human + backup
Packaging write access on day oneShip read-only first
Example

Filled prompt

Temptation: skip the habit for plugins-package-for-teammates to save five minutes.
Job still: hand teammates a plugin/connector setup
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-package-for-teammates)
  • Still delivers checkable output for “hand teammates a plugin/connector setup”
  • Unknowns labeled; draft-only
  • Pass/fail: refuse-line dated (plugins-package-for-teammates #4)

Field note: hand the one-pager to someone who did not build the tool. If they cannot install or roll back from the page alone, the page is not done.

Practice now

Smoke install: teammate dry-install instructions in 5 lines (Asia/Shanghai).

Support hours: state who answers questions and when (Asia/Shanghai).

Revoke-doc drill: document revoke steps in README before share (Asia/Shanghai).

Package drill: write the README “who maintains + how to revoke” before sharing a plugin (Asia/Shanghai).

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

Tonight write install / permissions / uninstall three lines for a real plugin, then have a teammate trial-install once.

Today card (copy) — plugins-package-for-teammates: 1. Artifact I will produce: ___ 2. Pass/fail check: ___ 3. Refuse-line if tempted to skip verify/send: ___ (date: Asia/Shanghai) 4. One never-do from this guide: ___

Extra pass: do the card on a real file today—reading alone does not count.

Buffer line: name the artifact path you used (Asia/Shanghai).

One sentence takeaway

Teammate pack: permissions, egress, uninstall path, maintainer; no ship if any missing.

Next

Install and evaluate · Skill library · Directory hygiene

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