synthesis

Proposes and queues next experiment variations grounded in Chronicle lineage, evaluation, and literature.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deciding what to try next in an ongoing research experiment requires synthesizing what worked, what failed, and what the literature says — a slow, error-prone manual process. This Skill automates that ideation pass on a Chronicle experiment while keeping the human as the approval gate: nothing is committed or queued without explicit acceptance. ## Core Features & Use Cases - Grounded evaluation: Loads the experiment record (lineage, variations, runs, lessons) and invokes the evaluate-results skill for a what-worked / what-didn't read judged against pre-registered hypotheses. - Literature grounding: Optionally invokes literature-review to survey external work scoped to the gap the evaluation exposed, registering citations on the anchor experiment. - Pre-registered proposals: Drafts next variations (or child experiments) each with a required hypothesis and expected outcome, then queues only the ones the user accepts via chronicle.propose_variation or the variation-authoring skills. - Use Case: After a round of training runs on an experiment plateaus, ask for a synthesis pass — the agent evaluates the variations, checks the failure-mode catalog, proposes three regularization-focused variations with hypotheses, and queues the two you approve. ## Quick Start Ask the agent to run a synthesis pass on your current Chronicle experiment and propose what to try next.

Frequently Asked Questions about synthesis

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

FAQPage Schema
How do I decide what experiment variations to run next?▼

Run a synthesis pass on your Chronicle experiment: it loads the lineage, runs, and lessons, invokes evaluate-results for a what-worked read, optionally surveys the literature, then drafts proposals with hypotheses and expected outcomes for you to accept or reject.

How does the synthesis skill queue approved proposals?▼

Config-only changes are queued with a single chronicle.propose_variation call carrying the config, hypothesis, and expected outcome. Code changes go through the variation-authoring skills first, since a variation must be committed before its run is created.

Does the synthesis skill work without the chronicle plugin installed?▼

No. Every platform mechanic — experiment reads, variation creation, citation registration, activity reporting — is a chronicle-plugin skill or chronicle.* MCP tool. Without both chronicle and research plugins installed, the skill stops and tells you to install them.

Can the synthesis skill commit or queue experiments automatically?▼

No. The human is the approval gate: proposals are presented as a list with hypothesis, expected outcome, and cost/risk notes, and only explicitly accepted ones are queued. It never commits the experiment itself or blanket-queues unaccepted proposals.

Why does propose_variation get rejected during a synthesis pass?▼

Rejections happen when the parent experiment is not yet committed or when the required hypothesis and expected_outcome pre-registration fields are missing. Commit the experiment with the user's approval, or fill the fields from the proposal draft, then retry.