track-experiments skillA
track-experiments is agent-read markdown (skill) from ammawla/encode-toolkit: Track ENCODE experiments locally with publications, citations, and provenance. Use when the user wants to build a collection of experiments, manage citations, compare experiments, or track data provenance..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Track ENCODE Experiments ## When to Use - User wants to save/bookmark ENCODE experiments for later reference - User needs to build a collection of experiments for a project - User asks to "track", "save", or "bookmark" an experiment - User wants to manage citations and publications for ENCODE data - User needs to compare experiments for compatibility - User wants to export their experiment collection as CSV/TSV/JSON - User asks about data provenance (linking derived files to ENCODE sources) Help the user manage their local collection of ENCODE experiments. This skill covers the full lifecycle of experiment management: discovery, tracking, annotation, citation, comparison, provenance, and export. ## Tracking Capabilities 1. **Track an experiment**: Use `encode_track_experiment` to save experiment metadata, publications, and pipeline info locally. - Automatically extracts GEO accessions and PMIDs from experiment metadata - Fetches associated publications with authors, journal, DOI - Stores 18 metadata fields per experiment (see schema below) - Idempotent: re-tracking the same accession updates metadata without creating duplicates …
Read the whole file at its exact version.
How to install
mdr add ammawla/encode-toolkit/track-experiments@git:20260921.7231da8mdr add ammawla/encode-toolkit/track-experiments@sha256:0809a4d26f8955a9Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_57dzlgf3fetqumls)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260921.7231da8 latest | 2026-09-21 | 7231da8 | 41,363 B | A | view · diff |
| git:20260920.6050003 | 2026-09-20 | 6050003 | 41,357 B | A | view · diff |
| git:20260920.ce7840d | 2026-09-20 | ce7840d | 38,809 B | A | view · diff |
| git:20260321.d9029d0 | 2026-03-21 | d9029d0 | 38,825 B | A | view · diff |
| git:20260312.be32706 | 2026-03-12 | be32706 | 38,819 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (41363 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ammawla/encode-toolkit · 20 stars · license AGPL-3.0 · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_57dzlgf3fetqumls GET https://markdownregistry.com/api/v1/resolve?ref=ammawla/encode-toolkit/track-experiments GET https://markdownregistry.com/api/v1/blob/0809a4d26f8955a90e992530b1396423675c0913277108cac8ad33b636a3119b
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.