Promptprocessor
Write your prompt in your group's Google Doc, then submit the link here. The answer comes back into the same document.
New here? Start with the demo document
Open the demo & examples doc to see the convention, three worked examples, and what a good prompt looks like. Make a copy of it as your group's starting point.
How it works
- Write your prompt in your group's Google Doc under a heading called Prompt (a Heading 2 titled
Prompt, or simply a line reading ## Prompt — both work).
- Submit the document link above with your name and group.
- The processor reads that document, runs your prompt, and appends a Response section in the same document.
It normally completes within a few minutes. If nothing appears, check that the document is shared with simonwanghkteacher@gmail.com — the processor can only read documents that account can open.
Writing a good prompt — examples
Clear and specific:
“Explain the difference between active voice and passive voice in 3 sentences, and give one example of each.”
Feedback on your own writing:
“Here is my thesis statement: ‘…’. Give me feedback on how specific and arguable it is, and suggest two stronger versions.”
Too broad:
“Tell me about globalization.” → you will get a generic summary you already know.
The same idea, sharpened:
“In 150 words, explain one way globalization has affected Hong Kong's higher education, with a concrete example.”
Tips and things that go wrong
- Be specific about length — “in 3 sentences”, “about 150 words”.
- Ask for a format when you need one — “as a table”, “as bullet points”.
- One focused prompt per section beats five unrelated questions.
- An existing Response section means the doc counts as answered, so remove it first if you want a second run.
- Private documents the account cannot open will fail — share the doc before submitting.
For teaching staff — what is happening behind the scenes
Submissions land in a queue, each becomes a tracked record, and the answer is written back into the student's document under ## Response. Reads and writes go through Composio as simonwanghkteacher@gmail.com; the model is the HKBU GenAI gateway (BYOK). Re-running a document that already has a Response is skipped deliberately, so the queue is idempotent.
One page, several courses: UE2, GCAP 3056 and (planned) GCAP 3226 all share it, so nothing here is tied to a single workshop.