CtrlK
BlogDocsLog inGet started
Tessl Logo

circos-plot-generator

Generate Circos configuration files for circular genomics data visualization. Supports genomic variations (SNPs, CNVs, structural variants), cell-cell communication networks, and custom track configurations for publication-ready circular plots.

50

Quality

56%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Data Analysis/circos-plot-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 highly actionable with concrete code and commands, but it is markedly verbose and monolithic — reusing tables and fabricated example outputs — while its workflow lacks an explicit validate->fix->retry loop and its references are mislabeled.

Suggestions

Trim redundant content: collapse the per-section 'Best Practices' and 'Common Issues' blocks and remove fabricated 'Output Example' result summaries from the Common Patterns so each token earns its place.

Add an explicit validate->fix->retry feedback loop to the rendering workflow (e.g., validate config syntax, render, on failure diagnose and re-run) so workflow clarity can exceed the cap of 3.

Fix the References section to point to the real references/runtime_checklist.md instead of stating 'No reference files currently available', and move the Color Scheme Reference / Parameters / Troubleshooting material into separate reference files to reduce the inlined wall of text.

DimensionReasoningScore

Conciseness

The ~1150-line body is noticeably verbose: capabilities are restated in tables after prose, repeated 'Best Practices'/'Common Issues' blocks appear for every section, and 'Common Patterns' include fabricated-looking output examples ('Key findings visible', 'Publication ready') that pad tokens without adding instruction; it falls below the mostly-efficient 3 anchor.

2 / 5

Actionability

Most guidance is executable — concrete CLI commands ('python scripts/main.py --data ... --type variation'), parameter tables, and Python examples referencing real symbols (CircosConfig, CHROMOSOME_SIZES, COLOR_SCHEMES) — with minor gaps such as an unclosed code fence (line 44) and an inline-defined generate_and_render function that is not in scripts/main.py.

4 / 5

Workflow Clarity

A sequenced Workflow exists and there are checkpoint commands (py_compile Quick Check, Audit-Ready Commands), but for the batch/rendering operation there is no explicit validate->fix->retry feedback loop, and the feedback_loops note caps workflow_clarity at 3 for such operations.

3 / 5

Progressive Disclosure

The body is structured with headers, but bulk content (color references, parameter tables, troubleshooting) that belongs in separate files is inlined, references are not clearly signaled — the References section even states 'No reference files currently available' while references/runtime_checklist.md exists — so it is below the good-structure 4 anchor.

3 / 5

Total

12

/

20

Passed

Description

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

The description is specific and distinct, naming concrete capabilities and a clear niche, but it omits any explicit 'Use when...' trigger guidance, which caps its completeness and limits natural trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause naming the user phrases that should trigger this skill (e.g., 'Use when the user asks for Circos plots, circular genomics visualization, or SNP/CNV structural-variant plots').

Include common synonyms and file extensions users might say — 'Circos', '.conf', 'karyotype', 'ideogram' — to strengthen trigger-term coverage.

Clarify the primary action ('Generate configuration files') versus supported feature domains so the breadth reads as comprehensive rather than one action plus features.

DimensionReasoningScore

Specificity

Lists several concrete actions and domains — 'Generate Circos configuration files', 'Supports genomic variations (SNPs, CNVs, structural variants)', 'cell-cell communication networks', and 'custom track configurations' — with only minor coverage gaps; not a fully comprehensive enumeration of all track types, so it sits below 5.

4 / 5

Completeness

The 'what' is clearly stated, but there is no explicit 'when should Claude use it' trigger clause, and the judging guideline caps completeness at 3 when an equivalent 'Use when...' guidance is missing.

3 / 5

Trigger Term Quality

Relevant domain terms are present ('Circos', 'genomics', 'SNPs', 'CNVs', 'structural variants', 'cell-cell communication') but it lacks a natural 'Use when...' phrasing and common synonyms/file extensions users would say, so it is not the 4-level good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (Circos circular genomics plots) with distinct triggers and minimal overlap with other skills, matching the clear-niche anchor.

5 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1163 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
aipoch/medical-research-skills
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.