reviewing-ml-prior-art-survey

Reviews ML prior-art survey artifacts against numbered quality conditions and emits an approve or revise verdict.

1|1|Updated May 24, 2026
One-click install
npx skills add https://github.com/bm629/agent-skills --skill reviewing-ml-prior-art-survey-bm629
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-ml-prior-art-survey
Source: https://github.com/bm629/agent-skills/tree/main/skills/reviewing-ml-prior-art-survey
Command: npx skills add https://github.com/bm629/agent-skills --skill reviewing-ml-prior-art-survey-bm629

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? An agent that authors an ML prior-art survey will approve its own work, so a separate reviewer is needed to judge vocabulary maps, search outputs, extract records, and option registers against a fixed bar before the survey can be built on. ## Core Features & Use Cases - Condition-based judgment: Evaluates artifacts against 32 numbered conditions in references/conditions.md covering canonical terms, verbatim query recording, recorded zeros, cause evidence, evaluation frames, and authority ranking. - Outcome-aware review: Reads the artifact's outcome field (ran, not_run, vacated) first so coverage conditions are only applied where they are owed. - Grounded findings with a single verdict: Emits findings that each name their condition, labels upstream remedies with the exact file and field to change, and terminates with exactly one VERDICT: approve or revise line. - Use Case: After running ml-prior-art-survey to produce one angle's search output, hand the artifact plus the wave-0 vocabulary map to this reviewer to confirm every owed cell, query record, and candidate classification before adopting the survey. ## Quick Start Review this ml-prior-art-survey search output against the wave-0 vocabulary map and tell me whether to approve or revise it.

Frequently Asked Questions about reviewing-ml-prior-art-survey

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

FAQPage Schema
How do I review an ML prior-art survey artifact?

Hand the artifact to the reviewer along with the wave-0 vocabulary map, and it judges the work against the numbered conditions in references/conditions.md. It emits findings that each cite a condition, then exactly one VERDICT: approve or revise line.

What does the reviewer check in a prior-art search output?

It checks verbatim query recording, count frames, recorded zeros with causes, unreached-cell evidence, status classification, date handling, evaluation frames, and honest authority ranking. Shape and arithmetic checks are already handled by the deterministic validator, so the reviewer never repeats them.

Does this reviewer fetch sources from the web to verify claims?

No, it deliberately reads no external sources. Its inputs are the artifact, the wave-0 vocabulary map, and the producer package's schemas, source registry, and angle references, because a reviewer that fetches the corpus becomes a second unreviewed producer.

What happens when a finding's fix is outside the artifact being reviewed?

The finding is labeled UPSTREAM: with the exact file and field that must change, since the artifact's author cannot perform that remedy. A file whose every finding is upstream receives an approve verdict.

Will a thin survey result fail the review?

No, a thin-but-honest result is not revised. The reviewer only issues revise on a named gap against a numbered condition, never because an artifact could have been longer.