CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

arboreto

Infer gene regulatory networks (GRNs) from gene expression data using scalable algorithms (GRNBoost2, GENIE3). Use when analyzing transcriptomics data (bulk RNA-seq, single-cell RNA-seq) to identify transcription factor-target gene relationships and regulatory interactions. Supports distributed computation for large-scale datasets.

Quality

84%

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 well-organized, highly actionable body with executable code, algorithm-selection guidance, and useful troubleshooting. The dominant defect is progressive disclosure: the skill points users to four bundle files that do not exist, so the offloading strategy fails in practice; a small amount of duplicated content and one pseudocode snippet keep it just short of top marks elsewhere.

Suggestions

Create the referenced bundle files (references/basic_inference.md, references/algorithms.md, references/distributed_computing.md, scripts/basic_grn_inference.py) or remove the dangling references so navigation does not dead-end.

Replace the undefined `analyze_consensus(networks)` call in the Reproducibility section with a working consensus-filtering snippet (e.g., merging networks and keeping links appearing across a majority of seeds).

Consolidate the duplicate install instructions and merge the three near-identical Common Use Cases code blocks into one parameterized example to reduce token cost.

DimensionReasoningScore

Conciseness

The body is code-dense with almost no re-teaching of known concepts (no "what is RNA-seq" padding), and sections are tight. It is not a 5 because installation instructions appear twice (Quick Start and a separate Installation section) and the three Common Use Cases code blocks are near-duplicates that could be consolidated. Not a 3 because there is no substantial unnecessary prose beyond these minor redundancies.

4 / 5

Actionability

Nearly all guidance is executable: concrete import statements, working grnboost2/genie3 calls, a ready-to-run CLI invocation, and an output-format table. It misses a 5 because the Reproducibility "consensus" example calls an undefined `analyze_consensus(networks)` (non-executable pseudocode), and the promised ready-to-run script `scripts/basic_grn_inference.py` does not exist in the bundle. Not a 3 because the vast majority of code is copy-paste ready with real parameters.

4 / 5

Workflow Clarity

The load -> infer -> save sequence is clear in Quick Start, critical pitfalls are flagged ("Always use `if __name__ == '__main__':` guard because Dask spawns new processes"), and a Troubleshooting section covers error recovery for memory, performance, Dask, and empty results. It misses a 5 because there is no explicit validation checkpoint on the output (e.g., verify the network is non-empty before saving) — recovery guidance is reactive rather than built into the workflow.

4 / 5

Progressive Disclosure

Section structure is good and references are clearly signaled with purpose ("**See**: `references/basic_inference.md`", "**For detailed algorithm comparison...**: `references/algorithms.md`"), but the referenced bundle files do not exist — no `references/`, `scripts/`, or `assets/` directories are present, so all four cited paths (`references/basic_inference.md`, `references/algorithms.md`, `references/distributed_computing.md`, `scripts/basic_grn_inference.py`) are dangling. This breaks navigation, which is more than the "minor organization gaps" of a 4, but the in-body structure itself is solid rather than minimal, so it sits above the 2 anchor.

3 / 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 capability statements, named algorithms, explicit data-type triggers, and a proper "Use when..." clause in third-person voice. The only gap is a few natural adjacent trigger terms (SCENIC/pySCENIC, regulon) that users of this domain commonly say.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Infer gene regulatory networks (GRNs) from gene expression data", "identify transcription factor-target gene relationships and regulatory interactions", "Supports distributed computation" — and names the specific algorithms (GRNBoost2, GENIE3), giving comprehensive coverage of the skill's capability. It is not a 4 because no material capability gap remains unstated for this domain.

5 / 5

Completeness

It explicitly answers both parts: the what ("Infer gene regulatory networks (GRNs) from gene expression data using scalable algorithms (GRNBoost2, GENIE3)") and the when ("Use when analyzing transcriptomics data (bulk RNA-seq, single-cell RNA-seq) to identify transcription factor-target gene relationships"). Both are concrete and explicit, matching the top anchor exactly; not 4 because the when-clause is specific rather than generic.

5 / 5

Trigger Term Quality

Good keyword coverage with synonyms: "gene regulatory networks (GRNs)", "gene expression data", "transcriptomics", "bulk RNA-seq", "single-cell RNA-seq", "transcription factor-target gene relationships". It falls short of the 5 anchor because commonly said adjacent terms like "SCENIC/pySCENIC" and "regulon" — natural entry phrases for this exact task — are missing.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (GRN inference from transcriptomic data using named algorithms) with distinct triggers (RNA-seq, GRNs, transcription factors) that would not plausibly route to a different skill. Minimal conflict risk; clearly the top anchor rather than 4, where some overlap with a closely related skill would be expected.

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

referenced_paths_exist

Referenced path issues: 5 missing

Warning

Total

15

/

16

Passed

Repository

Microck/ordinary-claude-skills

Path

skills_all/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.