ds-lite-experiment

Define, run, and package reproducible research experiments with evidence manifests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Research experiments often lose their commands, metrics, and logs between sessions, making results impossible to rerun, verify, or hand off. This Skill enforces a contract-first experiment protocol so every run leaves behind reproducible commands, budgets, metrics, and a verifiable evidence pack. ## Core Features & Use Cases - Experiment Contracts: Declares hypothesis, baseline, metric direction, early/final budgets, success thresholds, and failure interpretations before execution in a JSON contract file. - Evidence Pack Lifecycle: Initializes, finalizes, and strictly verifies evidence packs via the ds_lite_evidence.py CLI, capturing stdout, stderr, metrics.json, and sanitized environment descriptions. - Long-Task and tmux Governance: Plans user-provisioned tmux capacity, verifies server fingerprints, and reconciles external task attempts so long-running GPU or cluster jobs survive session handoffs. - Use Case: A researcher comparing two model variants defines the contract, runs the baseline and candidate under a budget cap, finalizes the evidence pack, and hands the verified manifest to the review skill so the next session can audit exactly what ran. ## Quick Start Use ds-lite-experiment to define the contract for my baseline comparison, run it under a fixed budget, and package the metrics and logs as a verified evidence pack.

Frequently Asked Questions about ds-lite-experiment

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

FAQPage Schema
How do I make a research experiment reproducible across sessions?▼

Define an experiment contract with hypothesis, baseline, command, metric direction, and budgets, then initialize an evidence pack with ds_lite_evidence.py. The pack captures stdout, stderr, metrics.json, and environment data so another session can rerun or diagnose the experiment from files.

How do I run long experiments that outlive my current session?▼

Read the external long-task protocol and create an external task record before launch. For tmux runtimes, write a capacity plan, have the user bootstrap the server, verify the fingerprint, and launch only in the assigned pane with a recorded slot claim.

What is an evidence pack in experiment tracking?▼

An evidence pack is a validated bundle of a run's contract, logs, metrics, environment description, and outputs. It is initialized before execution, finalized after completion or failure, and checked with verify --strict so even failed runs count as intact evidence.

Can failed experiments still be recorded as valid results?▼

Yes. A failed process is valid evidence when its pack is intact. The protocol requires recording failed runs as first-class evidence, marking blocked experiments honestly, and never polishing missing evidence into success prose.

What happens when an experiment invalidates a previous idea?▼

Add a rollback or supersedes edge in the experiment graph instead of erasing the old route. Record the old interpretation, the correction, affected claims, and the supersede reason so the audit trail stays intact.