CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-noncoding-rna

Non-coding RNA analysis — miRNAs (miRBase, miRDB targets), lncRNAs (LNCipedia, RNAcentral), circRNAs, snoRNAs, and other ncRNA classes. Distinct mechanisms per class — miRNAs repress mRNA; lncRNAs scaffold/decoy/enhance. Use for ncRNA function prediction, miRNA-target prediction, lncRNA functional annotation, and ncRNA-disease association queries.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is tooluniverse-noncoding-rna in mims-harvard/ToolUniverse

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.

Highly actionable content with live-verified tool examples, a well-sequenced five-phase workflow, and honest evidence grading, but token efficiency and organization lag: the tool table contains duplicated/mislabeled rows, a section heading is duplicated, and lengthy lookup tables and download procedures are inlined instead of split into reference files.

Suggestions

Deduplicate and correct the Core Tools table: remove the second miRBase_get_mirna and PubMed_search_articles rows, and fix the 'LNCipedia_get_lncrna_publications' and 'LNCipedia_search_ncrna_by_type'/'get_lncrna_xrefs' descriptions that currently describe other tools' functions.

Rename the first '## Limitations' section (line 226) to '## Computational Procedures (Download-and-Process)' so it no longer duplicates the true Limitations section at line 291.

Move the curated lookup tables (well-studied miRNA targets, key ncRNA-disease associations) and the TargetScan/miRTarBase download pipelines into a references/ file, keeping SKILL.md as a lean overview with one-level-deep pointers.

DimensionReasoningScore

Conciseness

Mostly efficient domain-specific guidance, but the tool table has duplicated rows with mismatched descriptions (miRBase_get_mirna listed twice, PubMed_search_articles twice, 'LNCipedia_get_lncrna_publications' labeled 'lncRNA sequence (FASTA format)'), and the '## Limitations' heading appears twice (once wrapping computational procedures). Several blocks could be tightened but the content is largely non-redundant domain knowledge.

3 / 5

Actionability

Fully executable throughout: verified live tool calls with real responses (RNAcentral URS examples, MODOMICS queries with output shown), concrete parameters (clip_min=1, taxid=9606), and complete copy-paste pandas pipelines for TargetScan download and miRTarBase processing. It even documents a verified-broken tool (MODOMICS_get_modification) with the exact failure mode and a safe alternative.

5 / 5

Workflow Clarity

A clear Phase 0–4 sequence with class-identification decision rules, an evidence-grading framework (T1–T4) acting as a validation checkpoint, and explicit fallback loops (broken tool -> search/list; download unavailable -> reference table or PubMed). Falls short of 5 because there is no explicit cross-source verification step for results (e.g., confirm a target in both ENCORI and literature before reporting).

4 / 5

Progressive Disclosure

No bundle files exist and the skill is a single ~290-line file; structure is well-sectioned, but ~60 lines of download-and-process procedures (TargetScan, miRTarBase) and long curated association tables are inlined where reference files would fit, and the duplicated 'Limitations' header hurts navigation. This sits between 'content that should be separate is inline' (3) and 'minor organization gaps' (4) but nearer the former.

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 the domain and ncRNA classes, lists concrete actions and databases, and includes an explicit 'Use for...' trigger clause in third person. Main gaps are minor — a few natural trigger terms and body-covered use cases (conservation, expression) are omitted, and 'miRDB targets' is referenced only in the description while the body uses ENCORI/miRTarBase.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('ncRNA function prediction, miRNA-target prediction, lncRNA functional annotation, and ncRNA-disease association queries') with named databases, but omits coverage present in the body (conservation and expression queries), so it falls short of the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both 'what' ('Non-coding RNA analysis — miRNAs..., lncRNAs..., circRNAs, snoRNAs...') and 'when' ('Use for ncRNA function prediction, miRNA-target prediction, lncRNA functional annotation, and ncRNA-disease association queries') with concrete trigger phrases, third-person voice throughout.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('miRNAs', 'lncRNAs', 'circRNAs', 'non-coding RNA', 'targets', 'disease association'), matching what users would say; a few natural variations (e.g., 'biomarker', 'conserved', specific miRNA names) are missing.

4 / 5

Distinctiveness Conflict Risk

Clear ncRNA-analysis niche with class-specific triggers (miRNA targets, lncRNA annotation, ncRNA-disease associations); minimal overlap with sibling RNA-seq or CRISPR skills, which the body further disambiguates.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mims-harvard/ToolUniverse

Path

plugins/tooluniverse/skills/tooluniverse-noncoding-rna/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.