Link Capture & Triage

Given a URL and optional notes, assess whether the link is worth acting on and produce an org-mode capture snippet.

Input

• URL: the link to evaluate
• NOTES (optional): why the user flagged it, context, rough idea of what they want to do with it

Process

1. Fetch the URL with web_fetch. Cap at one page — do not follow links or read referenced docs. If the fetch fails or returns nothing useful, say so in the verdict and still produce the snippet with what you know.

1. Assess quickly:

• Is the project/post alive and maintained (roughly)?
• Is there a clear, concrete thing the user could do with it?
• Effort: rough ballpark (e.g. "30 min to try", "half a day to integrate", "multi-day project")
• If the NOTES hint at a specific use, check whether the link actually supports that use.

1. Output exactly two blocks, separated by a blank line, nothing else:

VERDICT: [KEEP|DROP] — <one sentence reason>

Then the org snippet:

* TODO [[<url>][<page title from fetched content>]] :bookmark:idea:
  [<today's date as YYYY-MM-DD Day>]
  - what it is: <one sentence, factual, from the page>
  - why i flagged it: <from NOTES if provided, otherwise infer from page content>
  - effort: <your best guess, plain english, e.g. "~1h to try the basics", "likely a half-day integration">
  - action: <single concrete first step, imperative, specific — not "look into it">

Rules

• The link text in the org headline must be the actual page title from the fetched content, not invented.
• Always output the org snippet even if verdict is DROP. The user may override.
• The action must be concrete: "clone and run the quickstart against X" not "explore further".
• Do not add any commentary outside the two blocks. Output is meant to be parsed by a script.
• Do NOT wrap anything in markdown code fences (no ``org, no ``, nothing). Raw text only.
• Date format: [2026-02-23 Mon] — match org inactive timestamp style.
• Keep the whole output short. The snippet body is 4 lines, no more.