CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cerna-analysis

Use when building a ceRNA regulatory network from a key gene list by combining bundled miRNA-mRNA and miRNA-lncRNA database files, with flat-file CSV exports and PDF visualization in a single output directory. NOT for: differential expression, single-cell analysis, enrichment analysis, or workflows without a key gene list.

Quality

83%

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

67%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.

Well-organized, lean, and largely executable content with a clear workflow and an exemplary reference-navigation table. Its main defect is that the docs advertise capabilities the bundle cannot fulfill: the sample-data path used in the primary examples and most non-default dataset modes reference files that are not shipped, so those commands fail at runtime.

Suggestions

Ship the missing database files (starbase_miRNA_mRNA.csv, miRDB_miRNA_mRNA.csv, miRTarbase_miRNA_mRNA.csv) in references/database/, or restrict --mirna_dataset to the modes the bundle actually supports.

Create tests/data/gene.txt (referenced by the navigation table, the Usage example, and the Testing section) or point the examples at an input path that exists.

Consolidate the igraph dependency note, which is repeated in the navigation table, after the Usage block, and in the error table, into one place to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is efficient — tables for arguments, outputs, and errors; no explanation of biology Claude already knows; code examples are terse. Minor trimmable redundancy: the igraph dependency note appears three times (the 'When to Read External Files' table, the note after Usage, and the SKILL_DEPENDENCY_MISSING row), and 'When to Use' restates the frontmatter description. This fits anchor 4 ('efficient; minor instances of over-explanation that could be trimmed') rather than 5, where every token would earn its place.

4 / 5

Actionability

Commands are concrete and complete-looking (full argument table with defaults, input-format rules, error codes), but the flagship Usage and Testing examples run `Rscript scripts/main.R --key_genes tests/data/gene.txt` and no `tests/data/` exists in the bundle, and 5 of the 7 documented `--mirna_dataset` modes (starbase, mirdb, mirtarbase, and all three pairwise) point to database files (starbase_miRNA_mRNA.csv, miRDB_miRNA_mRNA.csv, miRTarbase_miRNA_mRNA.csv) that are absent from references/database/, so those copy-paste invocations fail at runtime with SKILL_FILE_NOT_FOUND. That is 'missing key details' beyond the 'minor gaps' of anchor 4, so it sits at anchor 3 despite the otherwise strong concrete guidance.

3 / 5

Workflow Clarity

The four-step workflow is clearly sequenced with real checkpoints: Step 1 'Validate parameter choices... Verify the database directory and required files', Step 3 'Stop with SKILL_INVALID_DATA if no lncRNA interactions remain', plus an error table with cause/solution pairs and escalation ('IF error persists, READ: references/troubleshooting.md') and post-run verification commands. It falls short of anchor 5 because the retry/fix loop lives only in the error table rather than inline in the workflow, and the documented dataset-mode options cannot actually pass Step 1's file verification against the shipped bundle.

4 / 5

Progressive Disclosure

Good structure with a 'When to Read External Files' table that clearly signals each one-level-deep reference (algorithm.md, cli-guide.md, troubleshooting.md — all present) with purpose; detail is appropriately deferred and core usage/args kept inline. Not anchor 5 because navigation points at paths that do not exist in the bundle: `tests/data/` (listed in the navigation table) and three of the seven documented database files, which breaks 'easy navigation' and accurate discovery.

4 / 5

Total

15

/

20

Passed

Description

92%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: concrete actions, explicit use and non-use triggers, and a clearly fenced niche. Third-person imperative form with no first/second-person voice. The only weakness is slightly thin synonym coverage for trigger terms.

Suggestions

Add common synonyms such as 'competing endogenous RNA (ceRNA) network' and 'ceRNA network analysis' so users phrasing the task differently still trigger the skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions: "building a ceRNA regulatory network from a key gene list", "combining bundled miRNA-mRNA and miRNA-lncRNA database files", "flat-file CSV exports and PDF visualization in a single output directory" — input, data sources, outputs, and output structure are all specified. This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage' for this niche; it is not score 4 because there are no meaningful coverage gaps.

5 / 5

Completeness

It explicitly answers both questions: what ("building a ceRNA regulatory network... by combining bundled miRNA-mRNA and miRNA-lncRNA database files, with flat-file CSV exports and PDF visualization") and when ("Use when building a ceRNA regulatory network from a key gene list"), plus explicit negative triggers ("NOT for: differential expression, single-cell analysis, enrichment analysis, or workflows without a key gene list"). Both 'what' and 'when' are concrete and explicit, matching anchor 5; a 4 would require the 'when' to be less specific, which it is not.

5 / 5

Trigger Term Quality

Good keyword coverage with domain-natural terms a target user would say: "ceRNA regulatory network", "key gene list", "miRNA-mRNA", "miRNA-lncRNA", "CSV exports", "PDF visualization". It falls short of anchor 5 because common synonyms are missing — the spelled-out "competing endogenous RNA", "ceRNA network analysis", or file-format phrasages that users might naturally use instead.

4 / 5

Distinctiveness Conflict Risk

The ceRNA-network-from-key-genes niche is highly distinctive and the explicit NOT-for list (differential expression, single-cell, enrichment) fences off the adjacent skills most likely to collide. Clear niche with distinct triggers and minimal conflict risk, matching anchor 5 rather than 4's 'minor overlap risk'.

5 / 5

Total

19

/

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

aipoch/medical-research-skills

Path

awesome-med-research-skills/Data Analysis/cerna-analysis/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.