regulatory-elements
Skill20 starsChanged 8 months agoAGPL-3.0View on GitHub
Discover and characterize regulatory elements (enhancers, promoters, silencers, insulators, super-enhancers) using ENCODE data and the cCRE catalog. Use when the user wants to find candidate regulatory elements, identify active enhancers in a tissue, map promoter states, classify chromatin states with ChromHMM, identify super-enhancers with ROSE, understand the functional validation hierarchy (CRISPR > MPRA > reporter), or characterize non-coding genomic regions. Covers the full workflow from ENCODE cCRE lookup through chromatin state segmentation to functional validation and enhancer-gene linkage. Use this skill for ANY regulatory element discovery, classification, or characterization task.
In this repository46 other files it gives its agents.
- accessibility-aggregationSkill
- batch-analysisSkill
- bioinformatics-installerSkill
- cellxgene-contextSkill
- cite-encodeSkill
- clinvar-annotationSkill
- compare-biosamplesSkill
- cross-referenceSkill
- data-provenanceSkill
- disease-researchSkill
- download-encodeSkill
- ensembl-annotationSkill
- epigenome-profilingSkill
- functional-screen-analysisSkill
- geo-connectorSkill
- gnomad-variantsSkill
- gtex-expressionSkill
- gwas-catalogSkill
- hic-aggregationSkill
- histone-aggregationSkill
- integrative-analysisSkill
- jaspar-motifsSkill
- liftover-coordinatesSkill
- methylation-aggregationSkill
- motif-analysisSkill
- multi-omics-integrationSkill
- peak-annotationSkill
- pipeline-atacseqSkill
- pipeline-chipseqSkill
- pipeline-cutandrunSkill
- pipeline-dnaseseqSkill
- pipeline-guideSkill
- pipeline-hicSkill
- pipeline-rnaseqSkill
- pipeline-wgbsSkill
- publication-trustSkill
- quality-assessmentSkill
- scientific-writingSkill
- scrna-meta-analysisSkill
- search-encodeSkill
- setupSkill
- single-cell-encodeSkill
- track-experimentsSkill
- ucsc-browserSkill
- variant-annotationSkill
- visualization-workflowSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.