log-experiment

Create and merge gated GitHub pull requests for experiment logs.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/antondelafuente/automated-researcher --skill log-experiment-antondelafuente
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log-experiment
Source: https://github.com/antondelafuente/automated-researcher/tree/main/plugins/experiment-lifecycle/skills/log-experiment
Command: npx skills add https://github.com/antondelafuente/automated-researcher --skill log-experiment-antondelafuente

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of logging finished experiments, design-stage pre-registrations, or plain notes to a research repository as a gated pull request on GitHub, reducing manual steps and ensuring consistent record-keeping.

Core Features & Use Cases

  • Automated PR Creation: Automatically creates and merges a pull request for an experiment or note on GitHub.
  • Audit & Gate Checks: Ensures that the experiment has a closed audit and meets criteria for merging based on the registry convention.
  • Secret Scan: Performs a deterministic secret scan to prevent sensitive information from being committed.
  • Use Case: After running an experiment, the skill can be used to log the results as a pull request on GitHub, including an audit record for review.

Quick Start

Run the 'log-experiment' command with the directory of the experiment or note as an argument:

log-experiment.sh <registry-dir>

Frequently Asked Questions about log-experiment

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

FAQPage Schema
How do I log experiments as pull requests on GitHub?

To log experiments as pull requests on GitHub, you can automate the process of creating and merging gated PRs that include design and results files, ensuring consistent record-keeping for your research repository.

How does secret scanning prevent sensitive information in GitHub pull requests?

Secret scanning prevents sensitive information in GitHub pull requests by performing a deterministic scan before commit, blocking the creation of a gated PR if sensitive data is detected in the experiment files.

Do I need git and GitHub CLI to create gated pull requests for research logs?

Yes, you need git and the GitHub CLI (gh) installed, as the logging process relies on local git configurations and the GitHub API to automate pull request creation and merging.

What is the best way to automate design stage pre-registrations on GitHub?

The best way to automate design stage pre-registrations on GitHub is using a script that classifies files based on registry conventions, automatically creating a gated pull request for the DESIGN.md file.

How are experiment files classified when logging to a research repository?

Experiment files are classified based on registry convention: DESIGN.md and RESULTS.md are categorized as experiments, DESIGN.md alone as a design stage, and other files as plain notes for the pull request.