CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

arboreto

Infer gene regulatory networks (GRNs) from gene expression matrices using GRNBoost2 or GENIE3; use when analyzing bulk or single-cell RNA-seq to identify TF→target regulatory relationships.

Quality

81%

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.

The body is well-structured with executable, bundle-accurate commands and correctly signaled one-level-deep references. Its main weaknesses are redundancy between sections (and with the reference files), hedged language where the script's actual behavior could be stated plainly, and unsurfaced script options.

Suggestions

Merge "Key Features" and "Implementation Details" into one section, mentioning each references/ file once, and move the GRNBoost2-vs-GENIE3 pros/cons entirely to references/algorithms.md instead of duplicating them inline.

Replace hedged statements like "exact expectations depend on scripts/infer_network.py" and "(if exposed by the script)" with the script's actual interface: genes-as-columns orientation, the --separator flag, and its default grnboost2.

Add a one-line note on input preparation for single-cell data (e.g., aggregate/pseudobulk or use the aggregated matrix) so the "as needed" step is concrete.

DimensionReasoningScore

Conciseness

Mostly efficient, but with noticeable tightening opportunities: "Key Features" and "Implementation Details" repeat each other (e.g., "see references/algorithms.md" and "refer to references/algorithms.md"; distributed computing referenced twice), algorithm pros/cons stated in the body duplicate what references/algorithms.md already covers, and hedged filler like "(if exposed by the script) typically control Dask scheduling" and "exact expectations depend on scripts/infer_network.py" pads without informing. It is above anchor 2 (only some, not extensive, unnecessary explanation) but not the lean anchor 4.

3 / 5

Actionability

The two bash invocations of scripts/infer_network.py are concrete, executable, and match the actual script's flags (--input/--output/--algo with grnboost2|genie3), and dependencies are listed. Below anchor 5 because of minor gaps: the script's --separator option and TF-list expectations are never surfaced, and the "Key Parameters" section offers hedged, non-executable guidance ("Additional runtime/cluster parameters (if exposed by the script)...") instead of the real flags.

4 / 5

Workflow Clarity

For this simple single-action skill the workflow (run one command, get a ranked edge list) is unambiguous with both algorithm variants demonstrated, and nothing destructive requires validation checkpoints. However, input preparation is only vaguely indicated — "single-cell RNA-seq data (after normalization/aggregation as needed)" — and the input orientation is hedged ("rows typically represent samples/cells... exact expectations depend on..."), leaving minor gaps that keep it below a fully clean 5.

4 / 5

Progressive Disclosure

Good structure against the actual bundle: both referenced files (references/algorithms.md, references/distributed_computing.md) exist, are one level deep, and are clearly signaled from the body, with the overview kept short. Not anchor 5 because the body partially duplicates the reference files' content (algorithm comparison, Dask scaling) rather than purely pointing to it, and each reference is mentioned twice rather than consolidated.

4 / 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: third-person, concise, and explicit about both what it does and when to use it, with concrete domain and tool triggers. The only gaps are minor — a few missing synonyms and no file-extension mentions.

DimensionReasoningScore

Specificity

The description names the domain and concrete specifics: "Infer gene regulatory networks (GRNs) from gene expression matrices using GRNBoost2 or GENIE3" with output framed as "TF→target regulatory relationships". It is not quite anchor 5 because the action set is essentially one task executed via two named algorithms rather than multiple distinct concrete actions (no file-extension or output-format specifics).

4 / 5

Completeness

It explicitly answers both questions: what — "Infer gene regulatory networks (GRNs) from gene expression matrices using GRNBoost2 or GENIE3"; when — "use when analyzing bulk or single-cell RNA-seq to identify TF→target regulatory relationships". This matches the anchor-5 example pattern of a concrete capability statement followed by an explicit 'use when' clause; it is clearly above anchor 4, where the 'when' would be less specific — here both data modalities and the analytical goal are named.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "gene regulatory networks", "GRN", "GRNBoost2", "GENIE3", "bulk" and "single-cell RNA-seq", "gene expression matrices", "TF→target". It falls short of anchor 5's comprehensive coverage with synonyms and file extensions — e.g., no expression-matrix file formats (.tsv/.csv), no "regulatory network inference" phrasing, and related common terms like "SCENIC" or "co-expression" are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche (GRN inference from RNA-seq) with highly specific tool names (GRNBoost2, GENIE3) and domain triggers (TF→target, bulk/single-cell RNA-seq) that virtually no other skill would claim. Minimal conflict risk; well above anchor 4's 'minor overlap risk with closely related 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

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/arboreto/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.