chronicle-move-experiment

Transfers a personal Chronicle experiment into an organization with optional team and visibility settings.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Experiments often start in a researcher's personal space and later need to belong to a shared organization so admins can manage them and teammates can read them. This Skill performs that personal-to-organization transfer through the Chronicle platform without manual API calls. ## Core Features & Use Cases - Organization Resolution: Resolves the target organization by matching the user's named org against the scopes returned by the chronicle.list_scopes MCP tool, asking for clarification when ambiguous. - One-Call Transfer: Moves the experiment via chronicle.move_experiment, optionally assigning a team as owner and setting visibility (private, organization, or public) in the same call. - Failure Handling: Diagnoses common errors such as 409 conflicts for already-org-owned experiments or slug collisions, 403 membership errors, and 404 authorization misses. - Use Case: A researcher who prototyped an experiment personally says "move this experiment to the Acme organization" and the Skill resolves the org, transfers ownership, and reports the resulting visibility. ## Quick Start Ask the agent to move your experiment into your organization, for example: "Move this experiment to my org and make it visible to the whole team."

Frequently Asked Questions about chronicle-move-experiment

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

FAQPage Schema
How do I move a Chronicle experiment to an organization?▼

Provide the experiment ID and the target organization name or ID. The skill resolves the org via chronicle.list_scopes, then calls chronicle.move_experiment with the experiment_id and organization_id, optionally setting a team and visibility.

Can I transfer an experiment from one organization to another?▼

No. The move is personal-to-organization only. An experiment already owned by an organization cannot be re-homed, and the server returns a 409 error if you attempt an org-to-org transfer.

Do I need to install the Python SDK to move an experiment?▼

No. The skill uses the bundled Chronicle MCP tools directly, so no pip install is required. SDK equivalents like chronicle.experiments.move exist but are optional.

What visibility options exist when moving an experiment to an org?▼

You can set private (creator plus org admins), organization (org or team members get read and discuss access, the default), or public (anyone can read). Omitting visibility applies the org-wide default.

Why does moving an experiment fail with a 409 error?▼

A 409 occurs when the experiment is already owned by an organization or when its slug collides with an existing experiment in the target org. For slug collisions, rename the experiment slug first, then retry the move.

Does the original creator lose access after moving an experiment?▼

No. The creator keeps full control through their auto-role membership and owner grant, and billing attribution (owner_subject) is unchanged. The move only adds organization reach.