Generate publication-quality sequence logos for DNA or protein motifs from FASTA files or raw sequence lists.
78
Quality
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/Data analysis/motif-logo-generator/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted description with excellent specificity and domain-appropriate trigger terms that bioinformatics users would naturally use. The main weakness is the absence of an explicit 'Use when...' clause, which limits Claude's ability to know exactly when to select this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about sequence logos, motif visualization, consensus sequences, or needs to visualize DNA/protein alignments.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Generate publication-quality sequence logos' for 'DNA or protein motifs' from 'FASTA files or raw sequence lists'. Multiple specific capabilities are clearly stated. | 3 / 3 |
Completeness | Clearly answers 'what' (generate sequence logos from FASTA/sequences) but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied through the input types mentioned. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'sequence logos', 'DNA', 'protein', 'motifs', 'FASTA files', 'raw sequence lists'. These are domain-appropriate terms bioinformatics users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche - 'sequence logos', 'DNA/protein motifs', and 'FASTA files' are very specific to bioinformatics visualization. Unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides strong actionable guidance with executable CLI examples and comprehensive parameter documentation. However, it suffers from verbosity through generic workflow steps and response templates that don't add specific value to sequence logo generation. The core technical content (usage, parameters, error handling) is solid, but the surrounding structure adds unnecessary tokens.
Suggestions
Remove or significantly compress the generic workflow steps (2, 4, 5, 6) that apply to any task, keeping only logo-specific steps like input validation and sequence length verification.
Move the Response Template and Fallback Template sections to a separate reference file or remove them entirely, as they describe general response formatting rather than logo generation specifics.
Consolidate the Input Validation section's refusal message into a shorter form - Claude doesn't need the full redirect message spelled out verbatim.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity, particularly in the workflow section which includes generic steps (confirm user objective, return structured result) that don't add value specific to logo generation. The response template and fallback template sections add bulk without being essential for the core task. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear parameter documentation, concrete FASTA input examples, and specific output descriptions. The usage examples are copy-paste ready and the parameter table is comprehensive. | 3 / 3 |
Workflow Clarity | The workflow mixes generic task management steps with actual logo generation steps, making the sequence unclear. While validation is mentioned, the workflow lacks explicit checkpoints between steps and the numbered steps don't clearly map to the actual execution flow of running the script. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the skill is somewhat monolithic with response templates and fallback structures that could be separate references. The quick check, usage, and parameters sections are well-structured, but the document includes boilerplate that inflates its length. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
ca9aaa4
Table of Contents
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.