You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You are generating a concise weekly opportunities digest for a single student.
5
+
6
+
You are given a JSON array called "events". Each event may look like:
7
+
{
8
+
"listserv": "ACSU", // listserv or source that advertised the event
9
+
"host": "Cornell AppDev", // primary hosting org or company (may differ from listserv)
10
+
"title": "AppDev x Ramp - HACK→HIRED",
11
+
"description": "One‑day hackathon with prizes and recruiting",
12
+
"date": "2026-03-14",
13
+
"location": "eHub",
14
+
"tags": ["hackathon", "career", "recruiting"]
15
+
}
16
+
17
+
Important:
18
+
- \`listserv\` = who sent/advertised the opportunity (ACSU, WICC, etc.).
19
+
- \`host\` = who is actually running the event (AppDev, Ramp, a company, a conference, etc.).
20
+
Many events are cross‑posted; do not assume the listserv owns the event.
21
+
22
+
### Your task
23
+
- Write a **compact markdown digest** for this week, **no intro or outro sentences**.
24
+
- **Group events by listserv** using markdown headings based on the \`listserv\` field:
25
+
- Use a level-3 heading for each listserv that appears, like:
26
+
- \`### ACSU\`
27
+
- \`### WICC\`
28
+
- \`### Cornell\`
29
+
- \`### Opportunities\`
30
+
- Under each heading, list at most **3 high‑value events** that were advertised on that listserv, chosen for impact (recruiting, hackathons, major talks, strong mentorship/community events).
31
+
- For each event, use **one clean bullet point** in this exact format:
32
+
- \`- **Title (Mar 14)** – 1‑sentence description that clearly names the **host** or event type, the key value prop, and location if available.\`
33
+
- Keep each description **under 25 words**.
34
+
- Prefer **hackathons, recruiting, mentorship, and flagship events** over minor or redundant ones.
35
+
- If a listserv has more than 3 events, summarize only the top 3 and ignore the rest.
36
+
37
+
### Style constraints
38
+
- Output **markdown only** (no code fences).
39
+
- Use only \`###\` headings and \`- \` bullets, nothing else.
40
+
- **No emojis, no unsubscribe text, no calendar links, no greetings or sign‑offs.**
41
+
- **Total digest <= 220 words** across all sections.
0 commit comments