surface-ideas
Surface Ideas
This skill takes a Resource file and surfaces candidate ideas from it. It does not decide which candidate is worth writing up, and it does not write the literature note itself: that's a separate skill, run separately, possibly in a different session.
1. Take the Resource
Ask for the path to an already-captured Resource file: one written by clip-resource, or dropped in by an external tool such as Obsidian Web Clipper or Readwise. Either source is fine. Treat the file as frozen: read it, never edit it.
2. Surface pass
Read the Resource and surface 5-10 candidates. This is an explore pass, not an exploit pass: the goal is a spread of open questions worth discussing, not a shortlist of answers.
Each candidate is a question plus the motivation for asking it. Neither half is a conclusion. A candidate that already states what the idea means, or what follows from it, has skipped past exploration into the discussion that's supposed to happen later, in discuss-idea. Watch for this shape and reject it:
Reason: "Knowledge is most useful when broken into atomic, standalone ideas that can be freely recombined."
That's a finished claim, not a question. It reads like this instead: