Prompt for highly personalized news retrieval from /r/TOPIC.json

README.md

You will receive a JSON dataset next. Analyze it and produce a concise, personalized briefing for me.

Context & goal

• Persona: infer from what you already know about me (your memory + this chat history). Use that to prioritize what I’ll care about.
• Input: A generic JSON array/object of items (e.g., posts, articles, records) with fields like title, summary/selftext, url, permalink, created_at/created_utc, tags, score, and source/domain. If names differ, map sensibly.

What to deliver (strict) 0) Begin with one short paragraph titled “Why these three” that states your exact opinion on why the selected three topics are the most relevant to me right now (tie to my known interests/tools/goals).

1. Then a single Markdown table with columns: Topic | Why it’s interesting for me | Jump

   • “Topic”: short, human-readable label.
   • “Why it’s interesting for me”: one tailored line.
   • “Jump”: a working intra-document link to the matching section below using (#slug) anchors.
   • Create stable, kebab-case slugs (e.g., supply-chain-incident, malicious-extension, roadmap-ama).

2. After the table, write exactly three sections—one per chosen topic—in this structure and order:

   • What happened (short): ≤ 2 sentences.
   • Impact for me: 1–2 bullets tying directly to my stack/role/priorities (use your memory).
   • Do now: 2–4 concrete steps (commands, checks, settings, next reads).
   • Source: Provide a working absolute link:
     • If item.url is absolute (starts with http/https), use it.
     • Else, if permalink + domain exist, build: https://<domain><permalink>.
     • If you cannot construct a valid link, write (link unavailable) instead of a broken URL.

Selection rules

• Pick the three most interesting/impactful items for me (merge in your memory of my preferences).
• De-duplicate near-identical items (collapse crossposts/repeats).
• Prefer recent, credible, and actionable items (clear implications or steps).

Link rules (must always work)

• For Jump links: use (#slug) and include a matching, explicit HTML anchor in each section header: ### Title <a id="slug"></a>.
• For Source: only use absolute http(s) links. If unable to build one, use (link unavailable)—never include a broken link.
• Validate that each (#slug) exactly matches the corresponding <a id="slug"></a>.

Style & constraints

• Personalization: Always merge your memory of me; don’t ask clarifying questions—make your best call.
• Dates: Use absolute dates in timezone Europe/Berlin.
• Brevity: Each summary section ≤ ~120 words; neutral, professional tone.
• Safety: Defang obviously malicious strings (e.g., example[.]com) and avoid reproducing sensitive payloads verbatim.
• Robustness: If fields are missing, infer sensibly. If nothing qualifies, still present the best three with a brief note.