Build a team prompt library, saved assistants and safe automations

0:00 Your team prompt library

Here's a question for anyone who's taken this course. Where are your prompts right now? If the answer is scattered across dozens of chats, a notes app and your memory, you're not alone. And it means the quality of your team's AI work depends on who happens to remember what. In this final lecture, you'll turn everything you've built, templates, context packs, voice guides, reviews and sales prompts, into a system: a shared prompt library, saved assistants your whole team can use, and a few safe automations. You'll see an agency's library in action and watch me build version one.

0:43 Why a system

Why build a system? Three reasons. First, quality that doesn't depend on memory. When the best prompts live in one place, everyone uses the best version, not whatever they remember. Second, faster onboarding. A new hire or freelancer can produce on brand work in their first week, because the expertise is in the library, not in someone's head. And third, prompts that improve over time. When prompts are shared and versioned, every fix one person makes helps everyone. Here's the key idea. Individual prompting is a skill. A prompt library is an asset.

1:23 The restaurant kitchen analogy

Think of a well run restaurant kitchen. There's a recipe binder, so every cook makes the dish the same way. Each station has an owner who keeps its recipes current. And a new version of a dish doesn't go on the menu until the head chef has tasted it. Your prompt library works the same way. Entries are the recipes. Owners keep them current, especially anything that touches prices and claims. And a new version gets tested on real tasks before it replaces the old one. Kitchens that work this way are consistent. Kitchens that don't depend on who's on shift.

2:07 Library entries

Each library entry has a few fields. A clear name, like post call follow up. When to use it. An owner. A version and date. The inputs needed, like anonymized call notes and the context pack. The prompt itself with placeholders. The guardrails, like the confirm list at the end. One approved example output. And known issues, like overuses circle back, banned in version three. That last field becomes surprisingly valuable, because it's where the team records what goes wrong, and it's the fastest route to better prompts. Organize by job: research, briefs, content, long form, sales and review. Twenty excellent prompts beat two hundred mediocre ones.

2:54 Saved assistants

Your most used prompts deserve to become saved assistants. In ChatGPT, custom GPTs package a template, instructions and files into something you can share. In Gemini, Gems do the same. In Claude, shared projects carry instructions and knowledge, and Skills let you package repeatable procedures. In Microsoft 365, Copilot Notebooks group reference files and prompts, and agents handle repeatable tasks where your admin allows. And in Notion, library pages work with Notion AI, and Custom Agents can run on a schedule or trigger. Sharing options depend on your plan and admin settings. A good starter set: a hook generator, a brief builder, a long form chain, a proposal drafter and a reviewer.

3:43 Versioning and review

Prompts need maintenance, like any asset. Change one thing at a time, and note what changed: version four, added the banned phrase list. Test before you promote a new version: run it on three real tasks alongside the current version and compare with the CLEAR rubric. Review monthly: retire prompts nobody uses, fold recurring edits into the templates, and have owners check anything tied to offers, prices or approved claims, because those go stale fastest. A saved assistant with last quarter's offer sheet is worse than no assistant at all.

4:22 Safe automations

Now automation. The rule for this course: automate the admin around prompts, not the judgment. Scheduled prompts, like a weekly run that turns last week's customer questions into content ideas inside your project. Trigger based drafts: in a no code tool like Zapier, Make, Power Automate or n8n, a new discovery call note triggers an AI step with template nine, which creates an email draft, not a sent email, plus a task with the confirm list. And review routing: any draft mentioning a price or offer goes to the reviewer project or a named approver. Nothing customer facing is sent without a human clicking send.

5:08 Example 1: a solo creator's library

A simple example. A solo fitness creator in Toronto doesn't need a big system. She keeps ten prompts in one document: hooks, captions, a script template, a repurposing chain, a brand deal follow up, a rate card email, a voice check, a CLEAR reviewer, a disclosure check and a monthly analytics summary. Each has a version date and a known issues line. Her hook prompt is the one she uses daily, so she turns it into a Gem. And on the first Sunday of each month, she spends twenty minutes updating the document. That's a prompt library, and it's enough.

5:51 Example 2: the Abu Dhabi agency

Now a team example, with illustrative details. A twelve person agency in Abu Dhabi had prompts scattered across personal chats. They built a library of twenty four prompts in Notion, each with an owner and version. They turned the five most used into custom GPTs: hook generator, brief builder, long form chain, proposal drafter and reviewer. And they added one automation: after each discovery call note, a follow up draft appears in the rep's inbox for review. Three months later, new hires produce on brand drafts in their first week. And the known issues field has become the team's favorite way to improve prompts, because everyone can see what went wrong and what fixed it.

6:41 Watch me do it

Let me build version one. First, a library entry for the post call follow up: name, use when, owner, version one, inputs, the full template, guardrails, one approved example, and known issues, empty for now. Next, I turn it into a saved assistant. I paste the template into the instructions, attach the offer sheet and approved proof, and tell it to ask for the call notes first. Then the automation. In a no code tool: trigger, a new note tagged discovery call in our notes database. Step one, the AI step with the template. Step two, create an email draft addressed to the rep. Step three, create a task with the confirm list. And there's no send step at all. That's by design.

7:34 Recap and where to go next

Let's recap the final lesson. Turn your prompts into a shared library, with names, owners, versions, inputs, guardrails, examples and known issues. Package your most used prompts as saved assistants: custom GPTs, Gems, Claude projects or Skills, Copilot Notebooks or Notion agents. Version carefully, test with CLEAR, and review monthly. Automate the admin around prompts, and never let customer facing messages send without a human. Here's your try this now. Spend sixty minutes on version one: ten entries, one saved assistant and one draft only automation. Where next? Prompt Engineering Foundations for a broader pattern library. Advanced Prompt Engineering if you're building prompts into products. Mastering ChatGPT and Mastering Claude for each assistant in depth. And AI powered performance marketing for ads and measurement. Congratulations on finishing the course.