How to Create a GPT

Custom GPT Examples (Blueprints)

Six practical GPTs you can replicate. Each includes: what it does, ingredients, setup steps, golden prompts, and a copyable instruction block.

Last updated:

Contents

  1. Docs Summarizer
  2. Release Notes Writer
  3. Support Triage
  4. Onboarding Coach
  5. Data QA Assistant
  6. SEO Brief Generator

1) Docs Summarizer

What it does

Turns long product docs into short executive summaries and FAQ answers that quote sources.

Ingredients

Setup

  1. Upload docs using the templates.
  2. Use the response format: Answer → Bullets → Source quote.
  3. Test with 10 common questions; require source labels.

Golden prompts

Summarize the upgrade steps for {feature}. Quote the source heading like [file.md › Section].

Copyable Instructions

You are a Docs Summarizer. Use uploaded Knowledge as the primary source.
When answering, include a short answer, then bullets, then a quoted excerpt with [file.md › Heading]. If answer isn't present, say so briefly.

2) Release Notes Writer

What it does

Turns PR titles or a changelog into short, on-brand release notes.

Ingredients

  • Knowledge: 07-release-notes.md, 10-changelog-decisions.md
  • Actions: optional search over your repo

Setup

  1. Upload the release notes and decisions templates.
  2. Define a response format: Added / Changed / Fixed.
  3. Provide product voice/tone in Instructions.

Golden prompts

Draft release notes from these PR titles. Keep to 130–160 words.
- feat: {title}
- fix: {title}

Copyable Instructions

You are a Release Notes Writer.
Format: Hook sentence → Added → Changed → Fixed. Use the product voice from Knowledge. Avoid internal jargon.

3) Support Triage

What it does

Collects user issue details, drafts steps to reproduce, and (optionally) creates a ticket.

Ingredients

  • Actions: createTicket (see OpenAPI Recipes)
  • Knowledge: troubleshooting FAQ

Setup

  1. Implement the createTicket Action (bearer auth).
  2. Decision rule: call Action after gathering {subject, description, priority, email}.
  3. Response format: Summary → Repro steps → Next action → (ticket URL).

Golden prompts

User says: “{symptoms}”. Ask any missing questions, then create a ticket and give me the URL.

Copyable Instructions

You are a Support Triage assistant. Ask for missing details (subject, description, priority, email). Then call createTicket. Return a short summary, numbered repro steps, next action for the user, and the ticket URL.

4) Onboarding Coach

What it does

Guides new customers through a 5‑step setup, checks prerequisites, and tracks progress.

Ingredients

  • Knowledge: SOPs + Quickstart
  • Actions: optional appendRow to log progress

Setup

  1. Upload SOP template and Quickstart guide.
  2. Define the 5 steps with prerequisites and success checks.
  3. Optional: log progress via sheet append Action.

Golden prompts

I’m onboarding a {customer type}. Walk me through the 5 steps. Ask one question at a time and mark progress after each step.

Copyable Instructions

You are an Onboarding Coach. Guide the user through 5 numbered steps, one at a time. After each step, confirm success with a short check. Keep tone friendly and concise. Optionally log progress via appendRow.

5) Data QA Assistant

What it does

Validates CSVs or pasted tables: checks types, nulls, ranges, and outputs a compact report.

Ingredients

  • Tools: data/code tool enabled
  • Knowledge: data dictionary CSV

Setup

  1. Upload the data dictionary from templates.
  2. Specify checks: types, null %, valid ranges, primary key uniqueness.
  3. Define output: Issues table → Fix suggestions.

Golden prompts

I uploaded {file}. Validate it against the data dictionary. Show issues with row counts and one-line fixes.

Copyable Instructions

You are a Data QA assistant. Analyze uploaded CSVs using the data dictionary. Output: (1) issues table with counts, (2) 3 prioritized fixes, (3) a single SQL or pandas snippet to apply the top fix.

6) SEO Brief Generator

What it does

Creates article briefs with search intent, H2/H3 skeletons, SERP features to target, and must-cover entities.

Ingredients

  • Knowledge: glossary + product positioning
  • Actions: optional search endpoint for fresh SERP checks

Setup

  1. Provide a response template: Title → Search intent → Outline → Entities → Internal links.
  2. Add refusal rules (no YMYL advice beyond scope).
  3. Define a style (concise, no fluff).

Golden prompts

Make an SEO brief for the keyword: {topic}. Include: search intent, H2/H3s, entities to cover, FAQs, and 3 internal links.

Copyable Instructions

You are an SEO Brief Generator.
Output:
- Title (≤ 60 chars)
- Search intent (1–2 lines)
- Outline (H2 with 2–3 H3s each)
- Entities (bullets)
- FAQs (3–5)
- Suggested internal links (from site map)

Publishing tips

  • Add a short decision rule for Actions (if any) in each example’s Instructions.
  • Include a privacy line: “Don’t send PII in Action requests.”
  • Link to Privacy Checklist before listing the GPT.

FAQ

Can I mix and match these?

Yes. Use a single GPT with multiple roles if you define clear decision rules and response formats.

Do I need Actions for all of them?

No. Several examples are Knowledge‑only. Add Actions when you need live data or server‑side work.

How do I measure success?

Track completion rates, edits required, and time saved. Keep a /changelog/ file in Knowledge.

Where do I start?

Pick one example, ship it in a day, and iterate using golden prompts.