CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

motif-logo-generator

Generate publication-quality sequence logos for DNA or protein motifs.

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/motif-logo-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 has a genuinely useful core (CLI usage, options, output interpretation, a runnable sanity-check command) buried under generic template boilerplate and self-referential filler. Its most serious defect is that the documented CLI and Python API do not match the packaged script, making the primary documented usage unexecutable as written. Pruning the boilerplate and reconciling the docs with the actual script would lift the skill substantially.

Suggestions

Reconcile the documented interface with the packaged script: either document the actual CLI (--sequences file, --format ascii|weblogo, --demo) or implement the advertised --input/--type/--title options, and remove the nonexistent "from motif_logo_generator import generate_logo" API example.

Delete template filler — Risk Assessment, Security Checklist, Lifecycle Status (stale 2026-03-06 date), duplicated Prerequisites/Usage sections, and "See ... above" cross-references that point to sections located below — keeping only logo-relevant content.

Remove the hardcoded personal install path ("/Users/z04030865/..."), fix the bogus "20260318/scientific-skills/..." cd path, and either add the referenced requirements.txt to the bundle or drop the reference.

DimensionReasoningScore

Conciseness

Roughly half the body is template boilerplate unrelated to logo generation: "Scope-focused workflow aligned to...", the Risk Assessment table, Security Checklist, and Lifecycle Status sections, plus duplicated Prerequisites/Installation and Usage sections, and stale time-sensitive data ("Next Review Date: 2026-03-06"). It matches anchor 2 (noticeably verbose, several padded sections) rather than 1 because the core Usage, Quick Start, and Output content is real and reasonably tight.

2 / 5

Actionability

The documented commands look concrete ("python scripts/main.py --input sequences.fasta --output logo.png --type dna") but do not match the packaged script, whose actual CLI is --sequences <file>, --format {ascii,weblogo}, --output, --demo; the documented --input/--type/--title/--width/--colorscheme options would error, and the "from motif_logo_generator import generate_logo" API and requirements.txt do not exist in the bundle. This matches anchor 3 (concrete guidance but incomplete/missing key details); not 4 because the primary documented interface is not executable against the bundle, not 2 because py_compile and --help commands are real and runnable.

3 / 5

Workflow Clarity

A workflow is listed ("Confirm the user objective...", "Validate that the request matches the documented scope...") but the steps are generic template language, the only concrete checkpoint is "python -m py_compile scripts/main.py", and the process is restated three times (Workflow, Example Usage run plan, Response Template) with no validation of the generated logo itself. This matches anchor 3 (steps listed, validation gaps, checkpoints missing or implicit).

3 / 5

Progressive Disclosure

The single referenced bundle file scripts/main.py exists and is clearly signaled, but requirements.txt is referenced and absent from the bundle, cross-references point the wrong direction ("See ## Prerequisites above" and "See ## Usage above" point to sections located below), and the 270-line monolithic body inlines navigation-noisy boilerplate. This matches anchor 3 (some structure but could be better organized, references not fully sound).

3 / 5

Total

11

/

20

Passed

Description

53%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 concise, domain-specific description with a clear single-sentence "what", weakened by the complete absence of any "when to use" trigger guidance and by thin coverage of capabilities (no mention of input formats or output types). The niche domain keeps conflict risk low.

Suggestions

Append a trigger clause, e.g. "Use when the user asks for sequence logos, motif visualization, or conservation plots from aligned DNA or protein sequences."

Mention concrete input/output details (FASTA input; .png/.pdf/.svg output) so the "what" covers capability breadth, not just one action.

Include one or two common synonyms such as "PWM" or "position weight matrix" to improve trigger matching against natural user phrasing.

DimensionReasoningScore

Specificity

"Generate publication-quality sequence logos for DNA or protein motifs" names the domain and one concrete action (generate sequence logos), but mentions no inputs (FASTA), outputs (.png/.pdf/.svg), or styling options. It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive); not 4 because only a single action is listed, not 2 because the action is concrete rather than generic.

3 / 5

Completeness

The description clearly answers "what" ("Generate publication-quality sequence logos for DNA or protein motifs") but contains no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the "when" is entirely absent rather than just under-specified.

3 / 5

Trigger Term Quality

Natural terms "sequence logos", "DNA", "protein", "motifs" are present, but common variations users actually say — "PWM", "position weight matrix", "WebLogo", "conservation" — are missing. This matches anchor 3 (some relevant keywords, missing common variations or synonyms).

3 / 5

Distinctiveness Conflict Risk

The motif sequence logo niche is clearly distinct from general plotting or bioinformatics skills, but without explicit trigger phrases it retains minor overlap risk with generic visualization skills. Mostly distinct with minor overlap matches anchor 4; not 5 because the 5-anchor example includes explicit, distinct trigger phrasing.

4 / 5

Total

13

/

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/Data Analysis/motif-logo-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.