CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

62%

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

38%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 contains genuinely useful domain reference material (track formats, color schemes, troubleshooting), but it is buried in a bloated, self-contradictory document with template filler, an inaccurate CLI reference that would fail as written, and no meaningful use of the bundle's references/ directory. It needs aggressive pruning and relocation of detail content into reference files.

Suggestions

Cut the SKILL.md body to a lean overview (quick start, CLI reference verified against scripts/main.py's argparse, pointers to detail files), and move Common Patterns, Troubleshooting, Quality Checklist, and Color Scheme Reference into separate files under references/ linked one level deep.

Fix the Parameters/Usage section to match the actual CLI: --color-scheme (not --colors), no --radius flag, --type choices variation/cell-comm/custom, --output default '.', and document --render and --config.

Delete the duplicated template sections (When to Use / Key Features / Implementation Details that repeat the description verbatim or cross-reference misplaced anchors) and resolve the contradictory dependency statements (Python version, yaml requirement, 'no external packages').

DimensionReasoningScore

Conciseness

The ~1,160-line body is heavily padded: the frontmatter description is repeated verbatim in 'When to Use' and 'Key Features'; sections point at each other with wrong anchors ('See ## Prerequisites above' while Prerequisites appears ~1,000 lines later); dependencies are stated twice with contradictions (Python 3.10+ vs 3.7+, yaml required vs 'No external packages required'); and generic template filler ('Scope-focused workflow', 'Output discipline') fills several sections. Not 1 because the second half carries genuine domain content (track data formats, color schemes, troubleshooting) rather than re-teaching concepts Claude already knows.

2 / 5

Actionability

There is substantial concrete guidance (Python API examples, complete CLI workflow with correct flags, input format tables), but the 'Parameters' table and 'Basic Usage' section document flags that do not exist in scripts/main.py ('--colors' vs the actual '--color-scheme', '--radius', '--type cell-communication' vs the actual 'cell-comm', default 'circos.svg' vs the actual '.'), so those commands fail as written. This is a systematic reference-section mismatch rather than a minor gap, placing it at anchor 3 rather than 4.

3 / 5

Workflow Clarity

A concrete three-step Complete Workflow Example (create sample data, generate config, render) exists alongside validation smoke checks (py_compile, --help) and quality checklists, but the primary 'Workflow' section is abstract template text, there is no validate-fix-retry feedback loop, and workflow guidance is scattered across redundant sections ('Workflow', 'Implementation Details', 'Complete Workflow Example'). Sequence present but checkpoints implicit — anchor 3.

3 / 5

Progressive Disclosure

Over 1,100 lines of material that clearly belongs in separate reference files (Common Patterns, Troubleshooting, Color Scheme Reference, Parameters, Quality Checklist) are inlined in SKILL.md. Worse, the body claims '(No reference files currently available for this skill)' while references/runtime_checklist.md actually exists in the bundle and is never linked, so the reference is both buried and misrepresented — anchor 2.

2 / 5

Total

10

/

20

Passed

Description

70%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, specific, third-person description with good natural trigger terms and a clear niche, but it lacks any explicit 'Use when...' clause, which caps completeness at 3 and leaves invocation guidance implicit.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks for Circos plots, circular genome plots, or wants to visualize SNPs, CNVs, structural variants, or cell-cell communication networks as circular figures."

Mention the concrete output artifacts (circos.conf, data track files, rendered PNG/SVG) so the 'what' includes the deliverable, not just the action.

Add common synonyms such as "circular plot" and "chromosome ideogram" to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

"Generate Circos configuration files" is a concrete action, and the description enumerates several specific capabilities ("genomic variations (SNPs, CNVs, structural variants), cell-cell communication networks, and custom track configurations"), matching anchor 4's 'several specific actions; minor gaps'. Not 5 because it omits capabilities covered in the body (rendering, ideograms) and relies on 'Supports...' clauses rather than multiple action verbs.

4 / 5

Completeness

The 'what' is clear (generate Circos configuration files for the listed data types), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines. Not 4 because the 'when' is entirely absent rather than merely implicit or weakly present.

3 / 5

Trigger Term Quality

Includes natural terms users would say: "Circos", "circular genomics data visualization", "SNPs", "CNVs", "cell-cell communication networks", "publication-ready circular plots". Not 5 because common variations like "circos plot", "chromosome ideogram", and "circular visualization" as a synonym for the tool name are missing.

4 / 5

Distinctiveness Conflict Risk

Circos circular genomics visualization is a clear niche with distinct, specific triggers (SNPs, CNVs, structural variants, cell-cell communication); minimal conflict risk with other skills. Matches anchor 5's clear niche with distinct triggers.

5 / 5

Total

16

/

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.

Validation — 14 / 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

Path

scientific-skills/Data Analysis/circos-plot-generator/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.