functional-screen-analysis skillA
functional-screen-analysis is agent-read markdown (skill) from ammawla/encode-toolkit: Analyze ENCODE functional genomics screens including CRISPR screens, MPRA (Massively Parallel Reporter Assays), and STARR-seq. Find screen data in ENCODE, process results, identify functional elements, and integrate with epigenomic annotations..
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
# Analyze ENCODE Functional Genomics Screens ## When to Use - User wants to find or analyze CRISPR screen, MPRA, or STARR-seq data from ENCODE - User asks about "functional screens", "CRISPR perturbation", "reporter assay", or "enhancer validation" - User needs to identify functionally validated regulatory elements from screen results - User wants to integrate screen results with epigenomic annotations (ChIP-seq, ATAC-seq peaks) - Example queries: "find CRISPR screen data in ENCODE", "analyze MPRA results for enhancer activity", "which regulatory elements have functional validation?" Discover and interpret functional validation data from CRISPR screens, MPRA (Massively Parallel Reporter Assays), and STARR-seq experiments in the ENCODE catalog. These assays directly test whether candidate regulatory elements have functional activity, complementing the correlative evidence from ChIP-seq, ATAC-seq, and Hi-C. ## Scientific Rationale **The question**: "Which of the candidate regulatory elements identified by ENCODE actually have functional activity, and what genes do they regulate?" …
Read the whole file at its exact version.
How to install
mdr add ammawla/encode-toolkit/functional-screen-analysis@git:20260312.665e731mdr add ammawla/encode-toolkit/functional-screen-analysis@sha256:04ce0530f1bc9c2ePin 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_eoc2n5kxurfxumn5)
1 badge views in 30 days
Versions
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 (32882 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_eoc2n5kxurfxumn5 GET https://markdownregistry.com/api/v1/resolve?ref=ammawla/encode-toolkit/functional-screen-analysis GET https://markdownregistry.com/api/v1/blob/04ce0530f1bc9c2e919ced1f957b07f999249aff8f401062c1c8202d15784ea4
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.
More from ammawla/encode-toolkit
Every file in ammawla/encode-toolkit