protein-diagram

Publication-quality protein analysis diagrams. Domain architecture maps, secondary structure annotation, Ramachandran plots, contact maps, multiple sequence alignment visualization, and protein feature tracks.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./backend/cli/skills/visualization/protein-diagram/SKILL.md

Quality

Content

82%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 a well-structured, highly actionable skill with executable examples for all six bundled scripts and clear routing guidance. Its main shortcoming is redundancy in restating the capability list and slightly long inline reference material.

Suggestions

Remove the duplicated capability enumeration in the intro paragraph since the 'When to Use' section and frontmatter already list it.

Consider moving the Style Guide and Input Formats tables into a references/ doc to shorten SKILL.md and improve progressive disclosure.

Add a brief verification hint (e.g. check the output file exists / open the SVG) after the rendering commands.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with lean, copy-paste code blocks, but the six-capability list is repeated across the description, intro paragraph, and 'When to Use' section, which could be trimmed.	4 / 5
Actionability	Every workflow ships fully executable, copy-paste-ready commands with concrete flag values covering the common cases for all six scripts.	5 / 5
Workflow Clarity	Each script's single-action usage is unambiguous and clearly organized, with a routing 'Important' section; minor gap is the absence of any output verification, though these are non-destructive rendering operations.	4 / 5
Progressive Disclosure	Well-organized sections with clear one-level-deep references to real scripts/draw_*.py files; structure is good, though Style Guide and Input Formats could optionally move to a reference file to slim the main body.	4 / 5
	Total	17 / 20 Passed

Description

75%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 distinctive, naming six concrete protein-diagram capabilities in a clear niche. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which leaves the activation context implicit.

Suggestions

Add an explicit trigger clause, e.g. 'Use when generating publication-quality protein structure or sequence diagrams from PDB/FASTA inputs.'

Include natural file-extension triggers such as .pdb, .cif, .fasta, and .aln to improve trigger-term coverage.

Mention common synonyms (e.g. 'secondary structure plots', 'phi/psi plots') alongside the technical terms.

Dimension	Reasoning	Score
Specificity	Lists six concrete capabilities (domain architecture maps, secondary structure annotation, Ramachandran plots, contact maps, MSA visualization, feature tracks), giving comprehensive coverage of distinct actions.	5 / 5
Completeness	Clearly answers 'what' with concrete capabilities, but provides no explicit 'Use when...' or equivalent trigger guidance for when Claude should invoke it, which caps completeness at 3.	3 / 5
Trigger Term Quality	Good natural-domain terms (Ramachandran plots, contact maps, domain architecture, multiple sequence alignment) that structural-bioinformatics users would say, but lacks file extensions like .pdb/.fasta and common synonyms.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (publication-quality protein diagrams) with distinct triggers and low conflict risk relative to sibling visualization skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: synthetic-sciences/openscience
Path: backend/cli/skills/visualization/protein-diagram/SKILL.md
Commit: 7dabbf0

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.