ds-lite-review

Reviews experiment evidence packs for integrity, reproducibility, and claim readiness before analysis.

2|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/AlexenderSokolov/deepscientist-lite-codex-plugin --skill ds-lite-review-alexendersokolov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ds-lite-review
Source: https://github.com/AlexenderSokolov/deepscientist-lite-codex-plugin/tree/main/plugins/deepscientist-lite-core/skills/ds-lite-review
Command: npx skills add https://github.com/AlexenderSokolov/deepscientist-lite-codex-plugin --skill ds-lite-review-alexendersokolov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Research experiments often produce results that look convincing but lack verified evidence: missing logs, unverified citations, threshold misses, or mismatched methods. This Skill acts as an independent evidence gate between experiment and analysis, ensuring no claim is promoted without typed, verifiable proof. ## Core Features & Use Cases - Four-lane review rubric: Assesses reproducibility/integrity, specification and metric compliance, citation authenticity, and method-code-log alignment using only pass, fail, needs-human, or not-applicable verdicts. - Evidence Pack verification: Runs run_review.sh <run-id> against the experiment's manifest and contract, validating hashes, logs, metrics, and external long-task (tmux) attempt chains before any claim promotion. - Typed review artifacts: Produces a Markdown review plus a ds-lite.review-result.v1 JSON sidecar, links them into the project state graph, and blocks analysis nodes until a passing review is active. - Use Case: After an experiment run finishes, invoke this Skill to verify the Evidence Pack, check that cited sources are authentic, and receive a gate decision (pass/fail/needs-human) with the smallest required follow-up before writing any analysis. ## Quick Start Use ds-lite-review to check whether the latest experiment run has enough valid evidence to support an analysis.

Frequently Asked Questions about ds-lite-review

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

FAQPage Schema
How do I verify an experiment's evidence before writing analysis?▼

Run the review workflow, which executes run_review.sh <run-id> against the experiment's Evidence Pack manifest and contract. It checks hashes, logs, metrics, and thresholds, then issues a pass, fail, or needs-human gate decision before any analysis node is created.

What does the four-lane review rubric check?▼

The rubric covers reproducibility and integrity, specification and metric compliance, citation authenticity, and method-code-log alignment. Each lane receives pass, fail, needs-human, or not-applicable, and the overall decision fails if any single lane fails.

What happens if the Evidence Pack is missing?▼

If the Evidence Pack is absent, the review stops claim promotion immediately and creates no positive review. The experiment workflow is asked to package the run first, since missing typed evidence becomes blocked or not-verified rather than a prose caveat.

Can a failed experiment run still pass review?▼

Yes. A nonzero exit code is an execution failure, not evidence corruption. If the Evidence Pack remains intact with valid manifest, logs, and hashes, the review distinguishes execution failure from evidence integrity and evaluates each lane on its own merits.

How are external long-running tmux tasks reviewed?▼

The review traces the external task record, tmux capacity plan, slot authorization, launch authority, and every attempt's Evidence Pack chain. Missing links, non-terminal task states, or inconsistent records result in needs-human or fail, never a prose-only caveat.

When should a review return needs-human instead of pass?▼

Return needs-human when a qualified check cannot be completed safely, such as unavailable source verification for citations or unverifiable external task evidence. An assumed pass is never allowed when independent verification is impossible.