CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-epigenomics-chromatin

Histone-modification ChIP-seq, ATAC-seq accessibility, chromatin state, and TF binding analysis from ENCODE, Roadmap Epigenomics, ChIP-Atlas. Use for chromatin-state-by-tissue queries, TF-binding-by-region, regulatory landscape mapping, and ENCODE-cCRE annotations. For DNA methylation use tooluniverse-epigenomics; for RNA-seq use tooluniverse-rnaseq-deseq2.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced domain skill: every tool has concrete parameters, ID-format gotchas, executable examples, retry loops, and an evidence-tier integration framework. Its weaknesses are redundancy — textbook histone-mark biology, a duplicated tool entry, and repeated reasoning logic — and a monolithic structure that inlines the entire API reference rather than splitting it into reference files.

Suggestions

Cut or compress the 'Reasoning: Histone Marks' dictionary to only the non-obvious guidance (bivalent promoter reporting rule, inference rule); Claude already knows that H3K4me3 marks active promoters and H3K27me3 marks Polycomb repression.

Move the Phase 0–7 tool parameter reference into a references/ file (e.g., references/tool_reference.md) and keep only the question-type classification, reasoning rules, key format gotchas, and fallback table in SKILL.md.

Deduplicate the overlapping guidance: ReMap_get_transcription_factor_binding is documented in both Phase 2 and Phase 6, and the cCRE-overlap/motif-disruption steps appear in both 'eQTL Interpretation' and 'Variant Regulatory Impact' — consolidate into one cross-referenced section.

DimensionReasoningScore

Conciseness

Mostly efficient — tool parameters, ID-format notes, and tight code examples are high-value — but it includes unnecessary explanation Claude already knows (the histone-mark dictionary: "H3K4me3 = active promoter", "H3K27me3 = Polycomb repression"), documents ReMap_get_transcription_factor_binding twice (Phase 2 and Phase 6), and repeats cCRE-overlap/motif-disruption logic across the eQTL and variant-impact reasoning sections. More than minor trimming is needed, so not 4; the bulk of the doc is tool-specific rather than padded, so not 2.

3 / 5

Actionability

Fully executable guidance: copy-paste-ready calls with real values (tu.tools.UCSC_get_encode_cCREs(chrom="chr17", start=7668421, end=7687490), RegulomeDB_query_variant(rsid="rs4994")), exact parameter names for every tool, required-ID formats (ENSG00000012048.20, chr17_43705621_T_C_b38), and output-parsing snippets covering the common cases.

5 / 5

Workflow Clarity

Clear sequence: classify the question first (types a–d), then Phase 0–8, with error-recovery feedback ("If 0 results, retry with assay_type='polyA plus RNA-seq'", anatomy-term fallbacks, "first hit may not match" filter warning) and a fallback-strategy table. Falls short of 5 because validation checkpoints are embedded in prose rather than explicit validate-before-proceed gates; well above 3 given the systematic retry and fallback structure.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but the ~230-line body inlines the full tool-parameter API reference (Phases 0–7) in SKILL.md with no reference files at all — matching the anchor example of ~200 lines of API reference that belongs in a separate file. Not 4 because the bulk reference content is not split out; not 2 because structure and navigation within the file are solid.

3 / 5

Total

15

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it names a distinct niche with concrete capability areas and data sources, gives an explicit "Use for..." trigger clause with specific query types, and proactively routes adjacent domains (methylation, RNA-seq) to sibling skills. Only minor improvements possible in natural-term synonym coverage and verb-forward action phrasing.

DimensionReasoningScore

Specificity

Lists four concrete capability areas ("Histone-modification ChIP-seq, ATAC-seq accessibility, chromatin state, and TF binding analysis") plus named data sources (ENCODE, Roadmap Epigenomics, ChIP-Atlas). Not a 5 because capabilities are stated as domain nouns rather than a comprehensive list of distinct actions; well above 3 given the breadth of specific coverage.

4 / 5

Completeness

Explicitly answers both what ("...analysis from ENCODE, Roadmap Epigenomics, ChIP-Atlas") and when ("Use for chromatin-state-by-tissue queries, TF-binding-by-region, regulatory landscape mapping, and ENCODE-cCRE annotations") with concrete trigger phrases, exactly matching the top anchor.

5 / 5

Trigger Term Quality

Natural domain trigger phrases are present ("chromatin-state-by-tissue queries, TF-binding-by-region, regulatory landscape mapping, and ENCODE-cCRE annotations", plus ChIP-seq/ATAC-seq in the what-clause). A few natural terms users would say are missing (e.g., "transcription factor" spelled out, "histone marks", "chromatin accessibility"), so it falls short of the comprehensive-synonym anchor at 5.

4 / 5

Distinctiveness Conflict Risk

Clear chromatin/TF-binding niche with explicit de-confliction redirects to the closest sibling skills ("For DNA methylation use tooluniverse-epigenomics; for RNA-seq use tooluniverse-rnaseq-deseq2"), minimizing overlap risk. Not 4 because the explicit redirects eliminate even minor conflict with related epigenomics skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

mims-harvard/ToolUniverse

Path

plugin/skills/tooluniverse-epigenomics-chromatin/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.