run-experiment

Record anchored evaluation events with config snapshots and results.tsv.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/LinkDry/Link-Research --skill run-experiment-linkdry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-experiment
Source: https://github.com/LinkDry/Link-Research/tree/main/skills/run-experiment
Command: npx skills add https://github.com/LinkDry/Link-Research --skill run-experiment-linkdry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Records a real evaluation event as canonical evidence for anchored lines, ensuring traceability and preventing mutation of the locked claim.

Core Features & Use Cases

  • Anchored-experiment recording: creates an append-only artifact bundle with the actual run configuration snapshot and evidence.
  • Evidence integrity: writes results and config snapshots to a stable location for auditability.
  • Guided workflow: coordinates with project briefs, STATE.md, and experiment memory to preserve lineage.

Quick Start

Invoke the run-experiment skill to record an anchored evaluation event and generate the corresponding config snapshot and results artifact.

Frequently Asked Questions about run-experiment

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

FAQPage Schema
How do I record an evaluation event as canonical evidence for research workflows?

To record an evaluation event as canonical evidence, you identify anchored execution lines and generate an append-only artifact bundle containing the actual run configuration snapshot and results. This ensures audit-ready traceability for your research workflow.

What is an anchored execution line and when do I need to record its evaluation evidence?

An anchored execution line is a locked claim in your research workflow that requires traceability. You need to record its evaluation evidence when you must prevent mutation of the locked claim and prove audit-ready traceability for your experiment.

How do I generate a config snapshot and results.tsv that meet evidence-contract requirements?

You generate a config snapshot and results.tsv by invoking the experiment recording workflow, which coordinates with project briefs and experiment memory to produce audit-ready artifacts stored in a designated workspace without mutating locked invariants.

Can I use experiment memory and project briefs to preserve lineage during an evaluation run?

Yes, you can use experiment memory and project briefs to preserve lineage during an evaluation run. The recording workflow coordinates with these artifacts alongside STATE.md to ensure the produced config snapshot maintains full audit-ready traceability.

What happens if I need to prevent mutation of locked invariants while recording experiment evidence?

To prevent mutation of locked invariants while recording experiment evidence, the workflow writes results and config snapshots to a stable, append-only location. This ensures the locked claim remains unchanged and the evidence integrity is maintained for audits.

Does the experiment recording workflow require any external dependencies to create an audit trail?

No, the experiment recording workflow requires no external dependencies to create an audit trail. It independently identifies anchored lines and records the real evaluation event, generating the necessary config snapshot and results artifacts within your designated workspace.