Esta página se muestra en inglés. Una traducción al español está en curso.
写作Oct 6, 2026·6 min de lectura

Plain-Language Workshop Participant Agreement Prompt

A reusable prompt that turns rough workshop ground rules into a short, readable participant agreement with space for questions and host decisions.

Listo para agents

Instalación lista para agent

Este activo puede instalarse después de elegir el runtime, revisar el plan y ejecutar el comando correspondiente.

Native · 96/100Política: permitir
Superficie agent
Cualquier agent MCP/CLI
Tipo
Prompt
Instalación
Single
Confianza
Confianza: Established
Entrada
PROMPT.md
Comando de instalación directa
npx -y tokrepo@latest install da2e58c2-bfe5-48e3-b19f-941dc6688aec --target codex

Ejecutar después de confirmar el plan con dry-run.

Start here

What to paste: three things after the instruction block — your current ground rules, the context (who attends, topic, length, in person or online, anything the host must personally approve), and any terms you must keep word for word.

Where to paste: the full prompt (with those three parts) into any ordinary AI chat that accepts text. No terminal, account setup or plugin is needed.

How to check the output: confirm every original rule appears somewhere, that kept terms survive word for word, that missing examples are labelled "needs an example", that [TO CONFIRM: your question] markers are listed in Checks, and that no invented penalties, dates or contacts were added.

What this prompt does

It restates an existing rule list in plain language under short headings, adds a blank "Questions and exceptions" area, a "Needs host decision" list drawn only from your context, and a note on what the agreement leaves vague. It never invents rules and never claims anyone was contacted or enrolled.

Inputs and permissions

  • You supply the three required parts; if any is missing or thin, the prompt stops and asks for it.
  • Host must approve decisions such as refunds, recordings, accessibility needs, guests or leaving early.
  • The draft is for you to review and share yourself; it carries no legal, compliance or safeguarding advice.
  • The prompt is a plain-text instruction, not an executable skill and not a one-click install.

Inputs you must have ready

Part What to include
Ground rules Your current list, however rough
Context Participants, topic, length, setting, host-only decisions
Terms to keep Wording, obligations or limits that cannot be softened

FAQ

Can it finalise the agreement for me? No. It produces a draft; you fill every [TO CONFIRM: ...] marker and decide what to send.

What if my rule list is messy? The prompt restates it under short headings such as Respect, Participation, Time and Sharing, and uses one heading if no grouping fits, saying so.

Privacy and limits

Paste only rule lists and context you are comfortable putting into a chat service. Do not include participant names, medical details or other personal data the agreement does not need. The prompt does not contact anyone and does not present the draft as approved or binding; you remain responsible for reviewing it and filling every marker.

Source reviewed; runtime not tested.

Source: original TokRepo prompt, CC BY 4.0. Reference context: ChatGPT release notes.

Complete reusable prompt

You are helping me turn my existing workshop ground rules into a plain-language participant agreement that a first-time attendee can read in about a minute.

WHAT I WILL PASTE I will paste three things after this instruction block:

  1. GROUND RULES — my current list, however rough, formal or legalistic it is.
  2. CONTEXT — who the participants are, the workshop topic, its length, the setting (in person or online), and any decision the host must approve personally (for example refunds, recordings, accessibility needs, guests, leaving early).
  3. TERMS I MUST KEEP — any wording, obligations or limits that cannot be softened, such as a code of conduct clause or a safety rule.

If any of these three is missing or too thin to work with, stop and tell me exactly what to supply. Do not invent rules, penalties, deadlines or promises that are not in my material. Never state or imply that I have contacted, enrolled, scheduled or messaged anyone — this is only a draft for me to review and share myself.

WHAT TO PRODUCE A participant agreement in this order:

  • A one-sentence summary of what agreeing to this means.
  • The rules restated in plain language, grouped under short headings such as Respect, Participation, Time, and Sharing. If my list has no natural grouping, use one heading and say so.
  • For each rule, one plain sentence on what it looks like in practice, drawn only from my material. If my material does not support a practical example, write "needs an example" instead of inventing one.
  • A clearly labelled "Questions and exceptions" section with blank space for the participant to write, plus a short neutral line explaining how to raise an exception with the host.
  • A clearly labelled "Needs host decision" list of anything in my rules that a participant cannot resolve alone, based only on the CONTEXT I supplied.
  • A short "What this agreement does not cover" note listing anything I left vague.

STYLE RULES Short sentences. Everyday words. Address the participant as "you". No legalese, no threats, no guilt, no exclamation marks. Keep every date, obligation and limit that appears in TERMS I MUST KEEP, even if the wording is less friendly. Do not add rules, consequences or encouragement that are not in my material.

OUTPUT FORMAT Markdown with the headings above, followed by a "Checks" section listing: every rule from my original list and where it appears in the draft; every term I asked you to keep and its exact surviving wording; and every item you marked "needs an example" or left out.

UNCERTAINTY HANDLING Where my input is ambiguous, insert [TO CONFIRM: your question] instead of guessing, and list all such markers in Checks.

BOUNDARIES Do not give legal, accessibility-compliance or safeguarding advice, and do not present this draft as approved or binding. I remain responsible for reviewing it, filling every marker, and deciding what to send.

WORKED EXAMPLE Fictional input: GROUND RULES — attendees must arrive on time, phones silent, no recording without consent, one person speaks at a time. CONTEXT — 90-minute in-person neighbourhood gardening workshop, twelve adults, host approves recordings and accessibility requests. TERMS I MUST KEEP — "no recording without consent". Illustrative output shape: summary sentence; headings Respect, Participation, Time, Sharing; under Sharing, a plain sentence that recording needs everyone's agreement, plus [TO CONFIRM: who a participant asks about recording], since the host-approval detail can sit in Needs host decision; a blank Questions and exceptions area; and Checks flagging the "needs an example" placement for punctuality if my list gave no reason.

SELF-CHECK BEFORE FINALIZING Pass or fail each: (1) Does every rule in my list appear somewhere, or is its absence named in Checks? (2) Does "no recording without consent" survive word for word? (3) Is every marker listed in Checks? (4) Is the draft free of invented penalties, dates or contacts?

Now wait for my paste. Do not produce the agreement until I have supplied all three parts.

References and reuse

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

Discusión

Inicia sesión para unirte a la discusión.
Aún no hay comentarios. Sé el primero en compartir tus ideas.

Activos relacionados