chronicle-status

Inspects Chronicle experiment lifecycle state, run statuses, and retracted lineage ancestors.

1|1|Updated May 9, 2026
One-click install
npx skills add https://github.com/methodic-research/skills --skill chronicle-status-methodic-research
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chronicle-status
Source: https://github.com/methodic-research/skills/tree/main/plugins/chronicle/skills/status
Command: npx skills add https://github.com/methodic-research/skills --skill chronicle-status-methodic-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you need a quick read on what is happening with a Chronicle experiment — whether runs are failing, what state an experiment is in, or whether retracted ancestors invalidate its lineage — this Skill returns a structured snapshot without opening the web UI. ## Core Features & Use Cases - Single-experiment snapshot: Calls the bundled MCP tool chronicle.get_experiment to report lifecycle state, variations, run counts, and latest run statuses. - Lineage validity check: Uses chronicle.get_lineage to flag retracted parents or grandparents that invalidate an experiment's premises, surfaced in a prominent warning block. - Fleet overview: When no experiment is specified, lists the caller's experiments via chronicle.list_experiments with a compact per-experiment summary. - Use Case: Ask "what's running on experiment X" or "any failures recently" and get a read-only status report highlighting failures, retractions, and non-ready git repo states. ## Quick Start Ask the agent to show the status of your Chronicle experiment, for example by saying "what's going on with v2's run on experiment X".

Frequently Asked Questions about chronicle-status

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

FAQPage Schema
How do I check the status of a Chronicle experiment?▼

Ask for the status of a specific experiment ID and the skill calls chronicle.get_experiment via the bundled MCP tools. It returns the experiment's lifecycle state, each variation's run count, and the latest run status in a compact snapshot.

How do I see all my running experiments at once?▼

Omit the experiment ID and the skill calls chronicle.list_experiments to print roughly the first 20 of your experiments with their hypothesis summaries and states. It does not page through the full list.

Does checking experiment status require installing the methodic SDK?▼

No, this is a read-only skill that uses the bundled MCP tools directly with credentials resolved from ~/.methodic. The methodic SDK is optional and only needed if you prefer its Python equivalents.

Can this skill detect retracted experiments that affect my results?▼

Yes, by default it calls chronicle.get_lineage and flags any ancestor with a non-null retracted_at timestamp. These retractions invalidate the experiment's premises and are shown in a prominent warning block.

Will the status check modify my experiments or runs?▼

No, the skill is strictly read-only and never mutates anything. It only calls get and list MCP tools, with no git operations or writes.