How do I install the Organize Experiments skill?

Run npx skillmds@latest add marin-community/organize-experiments in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Organize Experiments safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Organize Experiments?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Organize Experiments free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Organize Experiments?

marin-community (@marin-community) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Organize Experiments by marin-community

Name: Organize Experiments
Author: marin-community

File contents

Skill: Organize Experiment Reports

Overview

Curate docs/reports/index.md after new experiment issues are harvested: fold fresh entries into the right sections, refresh links, and leave ## Uncategorized empty.

Prerequisites

Local checkout of the marin repository with write access.
Ability to run uv commands.
Familiarity with the existing experiment categories in docs/reports/index.md.

Guidelines for Humans

Standard Workflow

Run uv run scripts/pm/itemize_experiment_issues.py to append new experiments.
Open the diff for docs/reports/index.md and identify the additions in ## Uncategorized.
For each experiment:
- Match it to an existing section (e.g., Training and Performance, Data Experiments).
- Merge any new resources (WandB links, Data Browser URLs) into the canonical entry in that section.
- Remove the placeholder entry from ## Uncategorized.
If an experiment truly does not fit, leave it under ## Uncategorized and add a note explaining why.
Proofread for duplicate bullets, broken Markdown, and consistent title casing.
Commit the curated report, open a PR, or, if an interactive agent, signal to the user to look.

Link Hygiene

Prefer direct https://wandb.ai/... links when available; keep legacy api.wandb.ai links only if the direct share link does not exist.
Use https://marin.community Data Browser URLs when the script surfaces them.
Preserve access tokens embedded in links.

Rules for Agents

NEVER delete existing sections or conclusions.
Keep badge styling consistent: [![#NNN](https://img.shields.io/...)] next to each experiment title.
When merging new content, update the canonical entry instead of duplicating it.
Leave ## Uncategorized empty whenever possible; a single placeholder sentence is fine.
Ask for guidance if an experiment does not map cleanly to known categories.

Validation

rg "^- " docs/reports/index.md to confirm bullets exist only under curated sections, not under ## Uncategorized.
Re-run uv run scripts/pm/itemize_experiment_issues.py if unsure that all experiments were captured.
Optional: markdownlint docs/reports/index.md to catch formatting drift.

---name: organize-experimentsdescription: Harvest experiment issue reports and curate docs/reports/index.md only when explicitly requested.---# Skill: Organize Experiment Reports## OverviewCurate `docs/reports/index.md` after new experiment issues are harvested: fold fresh entries into the right sections, refresh links, and leave `## Uncategorized` empty.## Prerequisites- Local checkout of the marin repository with write access.- Ability to run `uv` commands.- Familiarity with the existing experiment categories in `docs/reports/index.md`.## Guidelines for Humans### Standard Workflow1. Run `uv run scripts/pm/itemize_experiment_issues.py` to append new experiments.2. Open the diff for `docs/reports/index.md` and identify the additions in `## Uncategorized`.3. For each experiment: - Match it to an existing section (e.g., `Training and Performance`, `Data Experiments`). - Merge any new resources (WandB links, Data Browser URLs) into the canonical entry in that section. - Remove the placeholder entry from `## Uncategorized`.4. If an experiment truly does not fit, leave it under `## Uncategorized` and add a note explaining why.5. Proofread for duplicate bullets, broken Markdown, and consistent title casing.6. Commit the curated report, open a PR, or, if an interactive agent, signal to the user to look.### Link Hygiene- Prefer direct `https://wandb.ai/...` links when available; keep legacy `api.wandb.ai` links only if the direct share link does not exist.- Use `https://marin.community` Data Browser URLs when the script surfaces them.- Preserve access tokens embedded in links.## Rules for Agents- NEVER delete existing sections or conclusions.- Keep badge styling consistent: `[![#NNN](https://img.shields.io/...)]` next to each experiment title.- When merging new content, update the canonical entry instead of duplicating it.- Leave `## Uncategorized` empty whenever possible; a single placeholder sentence is fine.- Ask for guidance if an experiment does not map cleanly to known categories.## Validation- `rg "^- " docs/reports/index.md` to confirm bullets exist only under curated sections, not under `## Uncategorized`.- Re-run `uv run scripts/pm/itemize_experiment_issues.py` if unsure that all experiments were captured.- Optional: `markdownlint docs/reports/index.md` to catch formatting drift.## See Also- `scripts/pm/itemize_experiment_issues.py` for source data generation.- `.agents/skills/archive-experiments/SKILL.md` for retiring legacy experiments.

Frequently asked questions

Organize Experiments