Skip to content
Back to skills

Experiment Retrospective

ASecurity

Turn experiment reports and notes into summaries and new/updated result skills.

  • 666 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added February 8, 2026
research

Security analysis

A100/100

Scanned February 10, 2026

npx -y skills add majiayu000/claude-skill-registry --skill experiment-retrospective --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Experiment Retrospective?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Experiment Retrospective
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-experiment-retrospective/badge)](https://www.skillsdirectory.com/skills/majiayu000-experiment-retrospective)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: experiment-retrospective
description: >
  Turn experiment reports and notes into summaries and new/updated result skills.
metadata:
  short-description: "Summarize experiments and distill them into skills"
---

# Skill: experiment-retrospective

## When to use

Use this when:
- The user starts with `<retrospective>`, or
- Requests a summary/lessons-learned across one or more experiments.

## Behavior

1. **Select inputs**
   - Use the user's description to identify relevant:
     - `training_reports/*.md`
     - Sections of `references/experiment-log.md`
   - If ambiguous, list candidate reports and ask the user to choose.

2. **Summarize experiments**
   - For each report:
     - Extract: setup, hyperparameters, metrics, successes, failures.
   - Write a markdown summary with:
     - "What we tried"
     - "Key findings"
     - "What failed"
     - "Open questions"

3. **Update troubleshooting (if needed)**
   - If the experiments reveal new error patterns and their fixes:
     - Propose new rows for `references/troubleshooting.md`.
     - Ask the user for confirmation before editing the file.

4. **Propose or update skills**
   - Decide what **result skills** should reflect these findings.
   - For each skill:
     - If new: start from `templates/skills/result-skill-template.md`.
     - If existing: identify which sections to update.
   - Draft SKILL.md content that includes:
     - General description, context, results summary, recommended practice,
       failure modes, and explicit guidance for future Codex usage.
   - Use the user's description to fill in names, summaries, and assumptions,
     then remove any template sections that do not apply.

5. **Ask before writing**
   - Present the proposed skill changes.
   - Only create or modify files under `.codex/skills/` with user approval.

6. **Optional**
   - Append a summarized retrospective entry to `references/experiment-log.md`
     (e.g. "2025-12-26 – Retrospective on IMDb+Amazon mixture experiments").
   - Include a short "General description" line when logging.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.