---
id: con-custom-assistants
schema: concept/1
layer: garden
status: established
name: Custom assistants
aka: ["Custom GPTs", "GPTs", "Gems", "bots", "custom agents", "assistants"]
summary: >
  A version of an AI tool set up for one purpose, with its own instructions, files and sometimes
  tools, that you or others can open and use without setting it up again.
first_seen: "2023-11"
relations:
  builds_on: [con-custom-instructions, con-projects-and-knowledge]
  evolved_from: []
  related: []
  parallels:
    - idea: "a role with a job description"
      field: "human resources"
      note: "Defining a role once (purpose, responsibilities, reference material) lets different people step into it."
implementations:
  - { provider: openai, name: "Custom GPTs" }
  - { provider: google, name: "Gemini Gems" }
  - { provider: anthropic, name: "Claude Projects (shared)" }
  - { provider: microsoft, name: "Copilot agents" }
competencies: [cmp-make-it-repeatable, cmp-describe-the-task]
origin:
  kind: ai-proposed
  by: "seed agent 2026-10-16"
  rationale: "Learners say 'I made a GPT' or 'I made a Gem'; the coach needs to map both to one idea."
---

A custom assistant is an AI you have pre-configured for a single job. You give it a name, a set of instructions, some reference files and maybe access to tools, and then anyone with access can use it for that job straight away. OpenAI calls these GPTs, Google calls them Gems, and a shared Claude Project plays a similar role.

They are handy for repeated tasks with a clear shape: an onboarding helper loaded with the staff handbook, a feedback assistant that knows your grading rubric, a style checker for your brand voice. They also let one person's setup help a whole team.

The weak points are the usual ones for any shared tool. Instructions drift out of date, files go stale, and people may trust its answers more because it looks official. Someone should own it and check it now and then.

## Example

A school administrator builds a Gem loaded with the parent handbook and the instruction "answer only from the handbook; say when it doesn't cover something." Front-office staff use it to answer routine parent emails faster.

## How it connects

- Builds on **custom instructions** and the file-holding idea behind **projects**.
- Parallels **skills**: both package a way of working, at different sizes.
- Shared assistants need **evals** or spot checks to stay trustworthy.

## Try it

Write the one-paragraph job description your assistant would have: purpose, audience, what it must never do. Paste it into a new chat as a first test, before you build anything.