Not every prompt belongs on the public web. Some are personal drafts, some contain client details, and a few are good enough to share with everyone. Every template in our public prompt library went through the same three-step path before being published.
This post covers how to decide which level a prompt belongs to and what to strip out before it goes public. It is a follow-up to our guide on sharing prompts across a team.
Three levels of visibility
| Level | Who sees it | Typical content |
|---|---|---|
| Private | Only the author | Drafts, experiments, personal shortcuts |
| Team | Everyone in the team | Client work, internal processes, project context |
| Public | Anyone visiting the site | Tested, general-purpose templates |
The default should always be private. Moving a prompt up a level is a deliberate decision, never an accident.
When a prompt is ready for the team
- It has been used successfully at least a few times.
- The title and variables make sense to someone who didn’t write it.
- It has an owner who will maintain it.
When a prompt is ready to go public
Public prompts need a higher bar. Before publishing, check for anything that shouldn’t leave the company:
- Client names, internal product names and project codes.
- Real data in examples: emails, numbers, customer quotes.
- Internal URLs, file paths and API details.
- Persona or context text that only makes sense inside your team.
Before: Summarise the Q3 complaints from Hartwell Logistics
(account #4471) and suggest replies.
After: Summarise the {{period}} complaints from {{client_type}}
and suggest replies in {{tone}}.
Shared parts need checking too
A public prompt that includes a team-only persona or project context can leak that text when someone copies the prompt. Check every included piece, or replace it with a public version.
Publishing a prompt is like publishing code: assume someone will read every line.
Security lead
Publish less, but better
A public library with twenty well-tested prompts is more useful than one with two hundred drafts. Mark tested prompts clearly, include a sample output and keep the rest in the team.