chronicle

Plugin chronicle from marketplace methodic in methodic-research/skills. Commands read from the repo's manifest — 21 days ago.

Skills (38)

• chronicle-author-variation

  Use this skill when the user wants a new variation whose config the AGENT writes by applying a requested change — phrases like "make a variation that doubles the width", "author a variation with lr 1e-3", "create a variation that swaps the dataset to X". This is the LLM-authoring counterpart to `chr

• chronicle-bundle-variation

  Use this skill when an agent has external training code from a third-party git repo or loose packaged code outside Chronicle's managed experiment repo, and wants a managed Menlo Park worker to install and run it. Example requests: "bundle my code and run it on a worker", "package this external repo

• chronicle-bind-repo

  Use this skill when the user wants their OWN GitHub repository connected to a Chronicle experiment as a live two-way sync — phrases like "bind my repo", "attach my repo to the experiment", "use my own GitHub repo", "keep my repo in sync with Chronicle", "I want the agent's work in my repository". Bi

• chronicle-checkpoint-resume

  Use this skill when an agent/runner with its OWN training code needs to make a Chronicle run durable and reproducible — phrases like "snapshot the environment", "upload checkpoints as it trains", "resume training from the last checkpoint", "continue the crashed run", "preserve this checkpoint". It o

• chronicle-dataset

  Use this skill when the user or an agent flow wants to upload dataset bytes or training data to a Chronicle experiment, attach data as an experiment or variation input, load or download an existing dataset, register a dataset by reference to gs:// or s3:// bytes, or describe and update dataset metad

• chronicle-feed

  Use this skill when the user (or an agent acting for them) wants to read their Chronicle activity feed — phrases like "check my feed", "what needs my attention", "anything waiting on me", "are any agents blocked on me", "what's in my inbox", "anything awaiting approval", "what happened on my experim

• chronicle-import-repo

  Use this skill when the user has an EXISTING body of work — a local research repository, a paper-in-progress with code, a directory of experiments — and wants it turned into a Chronicle experiment. Phrases like "import this repo into Chronicle", "set up an experiment from this repo", "turn this proj

• chronicle-register-dataset

  Use this skill when the user or an agent flow wants to register a dataset that already lives at a gs:// or s3:// URI, author or correct its searchable metadata layer, or list and filter the dataset catalog. Example requests: "register the dataset already in gs://...", "catalog this turbulence corpus

• chronicle-reproduce-arxiv

  Use this skill when the user wants to reproduce or build on a published arxiv paper in Chronicle — phrases like "reproduce this arxiv paper", "reproduce arXiv:2301.12345", "set up an experiment to replicate this paper's results", "import this paper and its code", "can we reproduce the headline resul

• chronicle-run-variation

  Use this skill when an agent/runner that brought its OWN training code wants to EXECUTE a committed Chronicle variation and record the run — phrases like "run this variation", "train variation 2 and report it", "execute the committed variation and log to W&B". It is training-AGNOSTIC: it drives the

• chronicle-share

  Use this skill when the user wants to share a single Chronicle **asset** — a report, dataset, figure, or any uploaded file — independent of the experiment it belongs to. Phrases like "share this report with @alice", "give the ml-team read access to this dataset", "make this report public", "make jus

• chronicle-collections

  Use this skill ONLY when the user explicitly asks to organize research into a collection — "make a collection for structural loads", "add these papers to the structural-loads collection", "group these experiments under hydrodynamics", "associate this experiment with the hydrodynamics collection", "s

• chronicle-delete-asset

  Use this skill when the user (or a cleanup flow) wants to permanently delete Chronicle **assets that are not linked to any experiment** — orphaned uploads: phrases like "delete these datasets", "clean up the assets I uploaded by mistake", "purge the orphaned uploads", "remove that abandoned pending

• chronicle-delete-experiment

  Use this skill when the user wants to permanently delete one or more **open (uncommitted)** Chronicle experiments — phrases like "delete this experiment", "remove that draft", "I/the agent created too many experiments, clean them up", "consolidate these experiments", "throw away the experiments I'm

• chronicle-distill

  Use this skill when the user wants to synthesize an experiment's findings ACROSS ALL its variations into a single review-gated report — phrases like "distill the experiment", "synthesize the findings", "write the takeaways across all variations", "summarize what every variation showed", "give me the

• methodic-feedback

  Use this skill in two situations. (1) The user asks to send feedback, report a problem, or request a feature — "file feedback", "report this", "request a feature", "this flow is confusing", "tell the Methodic team". (2) PROACTIVELY, without being asked, whenever a gap or issue is encountered mid-tas

• fix-error-queue

  Use this skill when the user wants to drain the Chronicle fix queue locally — phrases like "fix the next error", "work on a queued bug", "let me PR an error-report fix". Claims one open root_cause from the fix-queue, reads the triage agent's writeup from the linked GitHub issue, attempts a fix on a

• chronicle-fork-variation

  Use this skill when the user wants to take an existing (usually committed) variation and create a new variation derived from it — phrases like "fork variation 2", "branch off this committed variation and let me modify it", "I want to tweak v1 but keep it intact". Different from `chronicle-prep-varia

• chronicle-history-explorer

  Use this skill when the user wants to explore Chronicle experiment history read-only — phrases like "what experiments exist about X", "show me the lineage of experiment Y", "explore the history", "what have we tried in this area", "where did this experiment come from". The skill combines semantic se

• chronicle-import-reports

  Use this skill when the user wants to import one or more research-report PDFs into a Chronicle organization's library — phrases like "import these papers", "add this folder of PDFs to the org", "register these research reports for the team", "bulk import the reading list". Each PDF becomes an org-sc

• chronicle-mint-git-token

  Use this skill when the user wants raw push/pull access to a Chronicle experiment's git repo for a manual workflow — phrases like "give me a git token", "I want to push to the experiment repo from my IDE", "what's the clone URL for experiment X". Returns a 1-hour install token + the HTTPS clone URL.

• chronicle-move-experiment

  Use this skill when the user wants to transfer a Chronicle experiment out of their personal space and into an organization — phrases like "move this experiment to my org", "transfer this to the Acme organization", "make this experiment org-wide", "put this under the team", "consolidate my personal e

• chronicle-prep-variation

  Use this skill when the user wants to start a new variation off an existing Chronicle experiment — phrases like "create a new variation", "start a fresh variation", "let me try a tweak of variation 1". The skill handles the full prep: mints a git token, clones the experiment repo, creates an agent-f

• chronicle-propose-experiment

  Use this skill when the user wants to turn a hypothesis into a new Chronicle experiment — phrases like "propose an experiment", "create an experiment for this hypothesis", "let's set up an experiment to test X", "spin up an experiment from what we just discussed". The skill drafts the hypothesis (sh

• chronicle-publications

  Use this skill when the user wants to register or cite a published work by its DOI, BibTeX, or arXiv id — "cite this paper", "add this DOI as a citation", "register this BibTeX", "reference arXiv:… in this experiment", "cite the paper this builds on", "cite this search result". A publication is a pu

• chronicle-rebind-variation-git

  Use this skill to switch an existing **open** variation from a bundled `code_artifact` to **git-managed** code: the user has pushed a branch/ref to the experiment's repo and wants to bind it to a variation that was created with a bundle (`chronicle-bundle-variation`), dropping the now-stale bundle.

• report-agent-error

  Use this skill when an agent got something wrong and it could recur — either the REASONING (a bad inference about the research) or the EXECUTION (a missing credential, an unset env var, steps in the wrong order, the right call against the wrong scope). Formerly report-reasoning-error; it now covers

• chronicle-research-lessons

  Use this skill in three situations. (1) PROACTIVELY, without being asked, the moment you realize you have REPEATEDLY made the same bad assumption while working an experiment, or the researcher EXPLICITLY OR IMPLICITLY corrects a wrong premise of yours ("no — the boundary mask is inverted", or a redi

• chronicle-research-survey

  Use this skill when the user wants to survey prior art before starting work — phrases like "survey the literature on X", "what's been tried for Y", "research turbulence before I design an experiment", "is there prior art on this". The skill does a two-source survey: (a) Chronicle's INTERNAL corpus —

• chronicle-retract-experiment

  Use this skill when the user (or an agent flow) wants to take a **committed or concluded** Chronicle experiment — or a single variation — out of use while preserving the record: phrases like "retract this experiment", "this result turned out to be wrong", "flag this as invalid", "mark these findings

• review-agent-errors

  Use this skill when someone wants to work through the agent-error review queue — phrases like "pull the review queue", "review the reported errors", "what's waiting for review", "give me a recommendation on these reports". Pulls reasoning and operational error reports awaiting review, gathers the ev

• review-catalog-proposals

  Use this skill when someone wants to work through proposed catalog entries — phrases like "review the proposed failure modes", "what's waiting for promotion", "should we promote this check". Pulls failure-mode and operational-check entries at status `proposed`, checks each against the reports behind

• chronicle-review-imports

  Use this skill to review/triage research-report PDFs previously imported into a Chronicle org — phrases like "review the imported reports", "check the import for problems", "which imported equations/tables were flagged", "approve the imported reports". It inspects each import's server-side extractio

• sagemaker

  Use this skill when you need to make a training project run correctly as a Chronicle-launched Amazon SageMaker training job — phrases like "prepare this variation for SageMaker", "run this on SageMaker", "train on spot", "make it resumable on SageMaker". It owns three SageMaker-specific things: decl

• chronicle-status

  Use this skill when the user wants a quick read on what's happening with a Chronicle experiment — phrases like "what's running on experiment X", "any failures recently", "show me the status of my experiments", "what's going on with v2's run". Returns a structured snapshot: lifecycle state, recent ru

• chronicle-tags

  Use this skill ONLY when the user explicitly asks to tag something or filter by tag — "tag this as turbulence", "tag these experiments turbulence", "what's tagged turbulence", "find assets tagged X", "search only things tagged Y". A tag is a lightweight, scope-namespaced keyword attached to ANY asse

• triage-error-queue

  Use this skill when the user wants to drain the Chronicle error-report triage queue locally — phrases like "triage the error queue", "process one error report", "let me look at incoming bugs". Claims one pending_triage error_report, gathers context (GitHub Issues search, Vertex semantic matches, cod

• chronicle-write-report

  Use this skill when the user (or an agent flow) wants to attach a written research document to a Chronicle experiment or variation — a post- experiment takeaways/findings write-up, a general research note, or any document where the math and figures matter. Phrases like "write up the findings", "docu

MCP servers (1)

• chronicle

  runs: sh ${CLAUDE_PLUGIN_ROOT}/mcp/launch.sh

Similar plugins