Agent skill · Design & Presentation

obsidian-experiment-log

Use this skill when the user discusses experiment design, ablations, training runs, evaluation, baselines, metrics, failures, or result interpretation that should be logged into Obsidian experiment and result notes.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill obsidian-experiment-log --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 2 KB
Bundled scripts: none
Path: skills/ai-ml/obsidian-experiment-log/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Obsidian Experiment Log Use this skill whenever project work changes the experimental state. ## Role in the workflow This is a **supporting skill** under `obsidian-project-memory`. It should help maintain canonical experiment and result notes, not create note sprawl. ## Default outputs - the relevant canonical note in `Experiments/` - the relevant canonical note in `Results/`, if a durable finding exists - links from today's `Daily/` note - relevant hub or plan references only when project state materially changes ## Main rules - Prefer updating an existing experiment note over creating a sibling note for the same experiment line. - Prefer updating an existing result note over creating a parallel result page for the same durable finding. - Raw logs, metric dumps, and temporary analysis fragments should usually stay in `Daily/` until they are interpreted. - A result note should exist only when the outcome is stable enough to reference later. ## Minimum experiment sections - Goal / hypothesis - Code or config entrypoint - Dataset / split - Metrics - Status (`planned`, `running`, `done`, `failed`) - Findings / notes - Next step ## Minimum result sections - Linked experiment - Main o

What's inside
Steps it walks through
  1. Role in the workflow
  2. Default outputs
  3. Main rules
  4. Minimum experiment sections
  5. Minimum result sections
  6. Linking rule
  7. Research path handoff
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the obsidian-experiment-log skill do?

Use this skill when the user discusses experiment design, ablations, training runs, evaluation, baselines, metrics, failures, or result interpretation that should be logged into Obsidian experiment and result notes.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill obsidian-experiment-log --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going