d-molecule-ray-tracer

Generate photorealistic rendering scripts for PyMOL and UCSF ChimeraX.

Quality

57%

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 ./scientific-skills/Data Analysis/3d-molecule-ray-tracer/SKILL.md

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 genuinely actionable for invoking the renderer but is padded with generic boilerplate and contains a dangling references/ pointer. Trimming template sections and either providing or removing the references directory would improve both conciseness and progressive disclosure.

Suggestions

Remove the generic template sections (When to Use bullets 2-3, empty "See ## above" pointers, Output Requirements, Error Handling, Input Validation, Response Template) that restate what Claude already knows, to recover conciseness.

Fix the dangling references/ pointer: either add the referenced files (PyMOL techniques, ChimeraX lighting, colorblind palettes, journal guidelines) or drop the section so navigation is not broken.

Replace the generic Workflow with renderer-specific steps that include a real validation checkpoint (e.g. load the generated .pml/.cxc in PyMOL/ChimeraX and confirm it runs) to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body carries substantial template boilerplate that does not earn its tokens: generic "When to Use" bullets that do not fit a ray tracer, empty "See ## Features/Usage/Workflow above" pointers, and stock Output Requirements/Error Handling/Input Validation/Response Template sections Claude already knows; this matches the anchor 2 "noticeably verbose; several unnecessary padded sections."	2 / 5
Actionability	Concrete executable commands (python scripts/main.py --pdb 1mbn --preset cover), a full Parameters table, an Advanced Usage block, and an Output Example give mostly copy-paste-ready guidance; not 5 because referenced artifacts (requirements.txt, references/) are absent.	4 / 5
Workflow Clarity	A 5-step Workflow is present but reads as generic template ("Confirm the user objective... Return a structured result"), and validation is limited to a py_compile quick-check rather than verifying generated scripts run in PyMOL/ChimeraX; checkpoints are implicit, matching anchor 3.	3 / 5
Progressive Disclosure	Section headers provide navigable structure and scripts/main.py is a real referenced bundle file, but the "See references/ for..." pointer targets a directory that does not exist and the content is otherwise monolithic in SKILL.md, leaving references present but not clearly/signally backed.	3 / 5
	Total	12 / 20 Passed

Description

65%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 to a well-defined niche and uses natural trigger terms, but it omits any explicit "when to use" guidance, capping its completeness. Adding a Use-when clause referencing molecular figures/covers would raise the score.

Suggestions

Append a "Use when..." clause, e.g. "Use when creating publication-quality or cover molecular images with PyMOL or UCSF ChimeraX."

Add a few natural synonyms/trigger phrases such as "molecular figures", "ray tracing", or "journal cover renders" to broaden keyword coverage.

Optionally list 1-2 more concrete actions (e.g. "apply cinematic lighting presets") to lift specificity from 3 toward 4-5.

Dimension	Reasoning	Score
Specificity	Names the molecular-rendering domain and one concrete action ("Generate photorealistic rendering scripts"), but lists only a single action rather than several, matching the anchor 3 example; not 4 because coverage is not broad.	3 / 5
Completeness	The description clearly answers "what" (generate rendering scripts for PyMOL/ChimeraX) but provides no "Use when..." trigger clause, so per the rubric guidance a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Natural domain terms "PyMOL", "UCSF ChimeraX", "rendering scripts", and "photorealistic" are exactly what a researcher would say, giving good keyword coverage; not 5 because synonyms like "publication figures" or "ray tracing" are absent.	4 / 5
Distinctiveness Conflict Risk	Tying the skill to two specific molecular-visualization tools (PyMOL, UCSF ChimeraX) carves a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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/3d-molecule-ray-tracer/SKILL.md
Commit: 63c61d3

Reviewed: 4 hours 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.