os-experiment-log

Automates persistent logging of OS experiment outcomes into dated files and index.md.

5|3|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/richfrem/agent-plugins-skills --skill os-experiment-log
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: os-experiment-log
Source: https://github.com/richfrem/agent-plugins-skills/tree/main/plugins/agent-agentic-os/skills/os-experiment-log
Command: npx skills add https://github.com/richfrem/agent-plugins-skills --skill os-experiment-log

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains a persistent, folder-based log of all agentic-os experiment runs, writing one dated file per run to context/experiment-log/ and updating index.md for quick queries.

Core Features & Use Cases

  • Centralized logging: creates one file per run under context/experiment-log/ with a clean, date-stamped naming convention.
  • Indexable history: updates index.md to provide a searchable overview of past experiments across verifier, tester, planner, and orchestrator sources.
  • Queryable insights: supports keyword and date-range queries to surface results, comparisons, and gap analyses.

Quick Start

Run the log writer after finishing an experiment to persist results to context/experiment-log/ and refresh index.md.

Frequently Asked Questions about os-experiment-log

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

FAQPage Schema
How do I persist and query agent OS experiment logs across multiple runs?

To persist and query agent OS experiment logs, this Skill automates writing one dated file per run to a context/experiment-log/ directory and updates an index.md. This creates a structured, searchable history of qualitative and numeric results from verifier, tester, planner, and orchestrator activities.

What is the best way to index experiment outcomes for traceability?

Indexing experiment outcomes for traceability is handled by maintaining an index.md file aggregating dated run logs. This provides a searchable overview of past experiments, allowing you to surface results, comparisons, and gap analyses using keyword and date-range queries.

Do I need Python to automate tracking of OS experiment outcomes?

Yes, you need Python to automate tracking of OS experiment outcomes. The workflow requires a Python-based script named experiment_log.py to write dated run files and maintain the index.md within the context/experiment-log/ directory.

Can I search past experiment logs by keyword and date range?

Yes, you can search past experiment logs by keyword and date range. The index.md provides a searchable overview of past experiments, enabling you to quickly surface specific qualitative and numeric results, comparisons, and gap analyses across verifier and planner runs.

How does centralized logging work for agentic-os experiment runs?

Centralized logging for agentic-os experiment runs works by creating one date-stamped file per run inside a dedicated context/experiment-log/ directory. It captures qualitative and numeric results across activities, updating an index for quick queries and traceability.