Cette page est affichée en anglais. Une traduction française est en cours.
写作Oct 4, 2026·6 min de lecture

Community Notice Prompt That Won't Invent Details

A reusable AI prompt that turns raw local-event facts into a short plain-language community notice and flags every missing or unclear detail.

Prêt pour agents

Installation agent prête

Cet actif peut être installé après choix du runtime, vérification du plan et exécution de la commande adaptée.

Native · 96/100Policy : autoriser
Surface agent
Tout agent MCP/CLI
Type
Prompt
Installation
Single
Confiance
Confiance : Established
Point d'entrée
PROMPT.md
Commande d'installation directe
npx -y tokrepo@latest install e565114a-b7f4-4839-b270-91660de8c315 --target codex

À exécuter après confirmation du plan en dry-run.

Start here

Copy the prompt below into an ordinary AI chat that accepts text. Paste your raw event details after the field list. Check whether the draft repeats only the facts you gave and lists missing items under "Needs your input".

If a field is empty, say so instead of leaving it blank — the prompt will insert a placeholder. A field can give you a placeholder or a contradiction: anything reading two ways (an address with no unit number, a deadline with no time zone) is marked uncertain rather than guessed.

What it is for

Organizers often know their event facts but struggle to phrase them plainly. This prompt writes one short notice covering what it is, when, where, who it is for, cost, what to expect, what to bring, how to register and the deadline — an invitation, not a press release.

How to feed it

  1. Copy the whole prompt text.
  2. Paste your details under each labelled field, keeping exact wording for dates, prices and contacts.
  3. Send it and read the four outputs: a subject line, the notice, "Needs your input", and "Before you send".

Verification and privacy

Treat the draft as a starting point, not a finished notice. "Before you send" names the exact lines to spot-check, so you can compare each date, address, price and link against your own input. Nothing was published or sent anywhere; the prompt explicitly avoids claiming that.

Avoid pasting personal contact details you are not willing to share with the AI service. Ask your provider how inputs are stored.

Source reviewed; runtime not tested.

FAQ

What if the notice invents a date or a price? Fix the input wording first, then re-run. Any value not traceable to your text should appear under "Needs your input".

Can it book a venue or set up registration? No. It only drafts text and may leave a placeholder where information is missing.

Attribution

Original TokRepo prompt, CC BY 4.0. Adapted from the reference ChatGPT release notes (reviewed 2026-10-04). The fictional "Riverside Repair Cafe" example is illustrative only.

Complete reusable prompt

You are helping me write a short community notice about a local event. I will paste my raw event details. You must use ONLY the details I supply. Do not add facts that are not in my input, and do not fill gaps with typical or assumed values.

MY INPUT Event name: Date and time (including time zone if relevant): Place (full address and any room/entrance detail): Who it is for: What happens there: Cost: Access or accommodation info (step-free entry, seating, quiet space, language, childcare, etc.): Bring or prepare: How to register or ask questions (exact contact or link text): Anything attendees must NOT expect: Deadline or cut-off: Tone or length preference:

TASK Write one community notice in plain language that a neighbour or colleague could act on. It must answer, in this order: what it is, when, where, who it is for, cost, what to expect, what to bring, how to register, and the deadline. Follow my tone and length preference if I gave one. Otherwise aim for about 150 to 250 words and a friendly, neutral tone.

WHAT TO DO WITH MISSING OR UNCLEAR INPUT If any required field is missing or ambiguous, do not guess. Instead write the notice with a visible placeholder in square brackets, such as [TIME TO CONFIRM], and add the item to a short 'Needs your input' list below the notice. Mark as uncertain, rather than silently fixing, anything that reads two ways, such as an address without a unit number or a deadline without a time zone. If my input contradicts itself, flag the contradiction and ask which version is correct instead of choosing one.

OUTPUT FORMAT

  1. A short subject line suitable for an email or group post.
  2. The notice itself, in short paragraphs or a short bullet list, whichever suits the details.
  3. 'Needs your input' - a numbered list of placeholders or contradictions, or the line 'None.'
  4. 'Before you send' - up to five checks, each naming the exact line in the notice it refers to.

REVIEW CHECKS BEFORE OUTPUT

  • Every date, time, address, price and contact detail in the notice traces back to my input, character for character where I gave exact wording.
  • No detail was invented, rounded or generalised to sound more complete.
  • The notice does not promise attendance, capacity, food, refunds or accessibility that I did not state.
  • The call to action matches the exact registration method I supplied, or is marked as missing.
  • The tone reads as an invitation, not a press release or a sales pitch.
  • The notice names no venue rules, sponsors or partners unless I listed them.

BOUNDARIES This is a draft only. Do not claim the notice has been posted, sent, published or approved anywhere, and do not offer to do so. Do not create a registration page, booking link, calendar entry or reminder. Do not give legal, health, safety, insurance or accessibility-compliance advice; if a detail raises such a question, note it under 'Needs your input' and leave it to me. Do not translate, localise or change the name of the event unless I ask. Do not add contact details, links or hashtags I did not supply.

WORKED EXAMPLE Input (fictional): Event name: Riverside Repair Cafe. Date and time: Saturday 14 March, 10am to 1pm. Place: Riverside Community Hall, 12 Mill Lane. Who for: anyone with a broken small appliance. What happens: volunteers help you try to fix it. Cost: free. Access: step-free entrance, hearing loop. Bring: the item, its cable, any spare part. Register: email repair@example.org. Tone: warm and brief. Deadline: none given.

Expected output shape: a subject line such as 'Riverside Repair Cafe, Sat 14 March, 10am-1pm'; a notice covering what, when, where, who, cost, what to expect, what to bring and how to contact; 'Needs your input' flagging that no deadline or cut-off was given; and 'Before you send' checks pointing to the address line, the step-free and hearing-loop line, and the contact line.

Pass or fail on that example: PASS only if the notice contains the exact address, the exact time, 'free' and the exact email, invents no deadline or capacity, and keeps the access details exactly as given. FAIL if it adds a booking link, a refund policy, a sponsor, or a plausible-sounding date or time that I did not supply.

References and reuse

Original TokRepo prompt · CC BY 4.0. Reference documents retain their own rights.

Fil de discussion

Connectez-vous pour rejoindre la discussion.
Aucun commentaire pour l'instant. Soyez le premier à partager votre avis.

Actifs similaires