paper-opportunity-radar

# Paper Opportunity Radar Treat the literature as an evidence base to traverse over time, not a feed to summarize. Build a cumulative corpus, audit important papers at claim level, look for what happened after publication, and turn only defensible gaps into testable opportunities. This skill runs when invoked. It does not silently create a background scheduler. If the user wants a daily cadence, preserve resumable state and give their scheduler the recurring prompt in [Daily Operation](#daily-operation). Never say monitoring is active until a recurring job actually exists. ## Non-negotiable Standards - **Never claim exhaustive coverage without a bounded corpus.** Define the databases, query strings, dates, languages, document types, and traversal cursor. Say "all records returned by this protocol," not "all papers ever." - **Fact-check at claim level.** Every factual statement in a report needs a fetched source. Mark interpretations as `INFERENCE` and gaps as `UNKNOWN`. - **A paper verifies what its authors reported, not that the result is true.** Independent replication, convergent evidence, or real-world validation is a separate evidence layer. - **Do not infer fraud.** Use `INTEGRITY CONCERN` for observable anomalies. Use `RETRACTED`, `CORRECTED`, or `FORMAL MISCONDUCT FINDING` only when the publisher, institution, court, or regulator supports that status. - **Citation count is attention, not validity.** Peer review, venue prestige, author reputation, a...