
Start here
Looking for a ready-made prompt to copy is a reasonable first move, and several vendors publish exactly that kind of page. What a reader finds behind three current links, retrieved 16 September 2026, is not the same shape of thing in each case, which matters before treating any one of them as the standard format.
What the documents say
Google's Workspace guide gives one worked template built from four labelled parts, persona, task, context, format, illustrated with a single program-manager email example that fills in an industry, a recipient and a length limit. It is short by design, meant to be filled in by hand. Anthropic's dedicated prompt-library address, previously a page of individual templates, now redirects to its consolidated prompting best practices reference, where worked examples appear as illustrations inside technique sections, an analytics-dashboard instruction, a formatting-preference comparison, rather than as a standalone list to browse and copy. OpenAI's public Cookbook is organised differently again: full worked recipes with titles such as 'Build a data analyst with the Agents API' and 'Build a Slack bot with the Agents API,' aimed at a developer assembling code around a model rather than a person typing a request by hand. All three are the vendors' own current pages, describing what each currently publishes, not an independent comparison of them.
Check this
The check is to open each page and note who it assumes is reading: a business user with no code, in the Workspace case; a person already comfortable with a detailed technique reference, in Anthropic's case; a developer writing an application, in OpenAI's case. A prompt copied from the wrong tier, a developer recipe used as a typed request, or a one-line persona template used as a coding pattern, will not transfer cleanly, and checking the assumed audience first avoids that mismatch.
What holds and what fails
A published template holds up as a starting structure, a reminder of what to specify, which is what all three pages are actually for. It fails as a finished answer to copy verbatim into an unrelated task, since every example is illustrating a technique for its own stated audience rather than solving a reader's specific problem. That a library can also simply move or disappear, as Anthropic's standalone library address did here, is a further, practical reason not to depend on any single bookmarked template surviving unchanged.
- Note which audience a prompt library assumes before adapting one of its examples.
- Treat a worked example as a structure to fill in, not as wording to keep unchanged.
- Re-check a bookmarked library page occasionally, since a vendor can consolidate or move it without notice.
A library is a snapshot of how one vendor currently organises its own advice, for one audience, and adapting from it is the intended use rather than a shortcut around it.
Sources & reading trail
Gives the single persona/task/context/format template aimed at business users.
Source published: Not established · Retrieved: 16 September 2026
Shows that Anthropic's former standalone prompt-library address now redirects here, with examples embedded in technique sections.
Source published: Not established · Retrieved: 16 September 2026
Confirms OpenAI's current public library is organised as developer recipes rather than short copyable prompts.
Source published: Not established · Retrieved: 16 September 2026
Documentation, regulator guidance and studies establish the record; the checks and the boundary are AI Use Field Guide editorial analysis. This retrospective draft does not imply the site published on the event date.