scout-review

Triages weekly literature inbox notes into keep/drop verdicts and backlog entries.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ZK-Theory/TDL --skill scout-review-zk-theory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scout-review
Source: https://github.com/ZK-Theory/TDL/tree/main/.agents/skills/scout-review
Command: npx skills add https://github.com/ZK-Theory/TDL --skill scout-review-zk-theory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Weekly literature-gathering runs produce raw inbox notes full of hits with mechanically assigned stream tags, and someone must decide which papers are worth deeper evaluation. This Skill performs that human-in-the-loop triage pass: it clusters near-duplicates, drops noise, and shortlists candidates for viability assessment without prematurely scoring them. ## Core Features & Use Cases - Inbox triage: Reads the newest untriaged vault/00-Meta/Discovery/_inbox/YYYY-Www.md note, judges every hit keep/drop, and appends a ## Triage table with one-line reasons. - Backlog promotion: Writes PROMOTE candidates into vault/00-Meta/Discovery/_backlog.md as state: triaged entries, reverse-chronological, carrying the source week and relevance note. - Guardrails: Distrusts mechanical stream tags, forbids viability scoring (reserved for /assay), and treats the ## Triage section as the completion marker even when zero hits survive. - Use Case: After Scout drops 2026-W25.md with 14 arXiv hits, run this Skill to merge duplicates, drop gate false-positives, and promote two persistence-diagram papers into the backlog for the next /assay pass. ## Quick Start Triage the latest untriaged weekly inbox note in vault/00-Meta/Discovery/_inbox and write the results into its Triage section and the discovery backlog.

Frequently Asked Questions about scout-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage a weekly literature inbox note?

Read the newest inbox note in vault/00-Meta/Discovery/_inbox that lacks a ## Triage section, judge each hit keep or drop with a one-line reason, then append the Triage table to that same note. Promote the strongest keeps into _backlog.md as state: triaged entries.

How to filter false positives from keyword-based literature alerts?

Treat mechanically assigned stream tags as hints only and judge relevance from the title and abstract yourself. Drop hits where a shared generic term caused a false positive, such as clinical graph papers matched on non-topological uses of network or segregation.

Does triage scoring happen during the inbox review pass?

No. This pass deliberately excludes viability scoring, which belongs to the later /assay step. Triage only records why a paper is worth assaying, writing triaged-state backlog entries rather than Axis-1/2/3 rubric scores.

What marks a literature inbox week as fully triaged?

The presence of a ## Triage section appended to the inbox note is the completion marker. A week can be fully triaged with zero backlog entries if every hit was dropped, so backlog presence is never the trigger.

When should a tagging problem be escalated instead of triaged around?

Escalate when the inbox stream tags are systematically wrong in a way that indicates the watchlist configuration itself needs fixing, rather than just one week's noise. Flag the broken watchlist instead of silently routing around it indefinitely.