project-prospectorlisted

# Project Prospector Surface and rank a person's body of work on a machine. The output is a **tiered ranking of projects/ideas/codebases** — strongest (most original ideas, most leverage) first — built from a parallel sweep that no single linear pass would find. The name is the intent: you're prospecting a messy filesystem for the few genius ideas buried in it. ## Operating context: run this from the main conversation This skill *spawns* investigation agents, so it belongs in the main agent loop where the Agent/Task tool is available. If you find yourself running it somewhere that can't spawn sub-agents (e.g. you are yourself a sub-agent, and nested agents are disallowed), don't abort — **fall back to running the same two-pass structure inline and sequentially yourself.** Use the identical scout commands, per-cluster git-log/mtime sweep, and the five Pass-2 blind-spot checks; you only lose parallelism, not coverage. Say so in one line at the top of your output so the reader knows the run was serial. One self-reference trap to close every time: **this skill and its working files live on the machine you're scanning.** Exclude the prospector skill directory and any `*-workspace/` it created from the catalog — they're this tool's own scaffolding, not the user's projects — and never treat your own draft report as a finding. If you write the final report to disk and the Write tool is blocked for it, fall back to a Bash heredoc (`cat <<'EOF' > report.md`). **The machine is a mo