CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

d-molecule-ray-tracer

Generate photorealistic rendering scripts for PyMOL and UCSF ChimeraX.

Quality

67%

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/3d-molecule-ray-tracer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 core usage material (commands, parameter table, preset table, output example) is strong and executable, and the workflow has sensible checkpoints including a fallback path. However, the body is heavily padded with duplicated commands, broken 'see above' template artifacts, and generic scaffolding sections, while its References section points to files that do not exist in the bundle.

Suggestions

Remove the template boilerplate — the broken 'See `## Features`/`## Usage`/`## Workflow` above' pointers, the duplicated py_compile and requirements.txt blocks, and the off-topic 'data analysis tasks / documented fallback path' bullets in When to Use.

Fix the progressive-disclosure problem: either create the `references/` files the References section promises (PyMOL techniques, ChimeraX lighting, colorblind palettes, journal guidelines) or delete the dangling References and requirements.txt mentions.

Cut the generic meta sections (Security Checklist, Risk Assessment, Lifecycle Status, Response Template, Output Requirements) or move them out of SKILL.md, keeping only what changes Claude's behavior for this task.

DimensionReasoningScore

Conciseness

The ~320-line body is noticeably padded with template artifacts and duplication: "python -m py_compile scripts/main.py" appears three times, "pip install -r requirements.txt" appears in two separate prerequisite sections, and broken boilerplate lines like "See `## Features` above for related details." and "See `## Workflow` above for related details." add no value. Generic scaffolding sections (Security Checklist, Risk Assessment, Output Requirements, Response Template, Lifecycle Status) and off-topic 'When to Use' bullets about 'data analysis tasks that require explicit assumptions, bounded scope' pad the token budget well beyond what the task needs. This sits between score 2 ('several unnecessary explanations or padded sections') and score 3; the volume of duplicated and irrelevant boilerplate places it noticeably below the midpoint, and it is not score 1 because it never explains concepts Claude already knows — the parameter and preset tables are dense and useful.

2 / 5

Actionability

The body provides fully executable, copy-paste-ready commands ("python scripts/main.py --pdb 1mbn --preset cover", multi-flag advanced examples) plus a complete parameter table with types/defaults and a preset comparison table, matching 'Mostly executable guidance; concrete code or commands with minor gaps'. It falls short of score 5 because the References section points to a `references/` directory that does not exist in the bundle, `requirements.txt` is referenced but missing, and the Example Usage includes an environment-specific path ("cd \"20260318/scientific-skills/Data Analytics/3d-molecule-ray-tracer\"") that will not resolve for users. It is above score 3 because nothing is pseudocode — every command shown is runnable.

4 / 5

Workflow Clarity

The Workflow section gives a clear 5-step sequence with explicit checkpoints (confirm objective/constraints, validate scope and 'stop early if the task would require unsupported assumptions', fallback path on failure), reinforced by a Quick Check ("python -m py_compile scripts/main.py") and an Error Handling section stating 'report the failure point, summarize what still can be completed safely, and provide a manual fallback'. This matches 'Clear sequence with most checkpoints present; minor validation gaps' — the gap being that no step verifies the generated .pml/.cxc script actually runs in the target software (Evaluation Criteria lists this only as unchecked boxes). It is below score 5 because validation of the final artifact is implied rather than an explicit feedback loop in the workflow steps.

4 / 5

Progressive Disclosure

Structure exists (a genuinely used, real script path `scripts/main.py`, plus parameter/preset tables), but the body is a ~320-line monolith that inlines generic meta-content (security checklists, lifecycle status, response templates) that belongs elsewhere or nowhere, and the References section signals four reference documents ('PyMOL-specific rendering techniques', 'ChimeraX lighting documentation', 'Colorblind-friendly palettes', 'Journal submission guidelines') that do not exist in the bundle — the `references/` directory is absent. This matches 'Some structure but could be better organized; references present but not clearly signaled; content that should be separate is inline'; it is above score 2 because real structure and a working script reference exist, but below score 4 because the flagged references are dangling.

3 / 5

Total

13

/

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 concise, third-person, and highly distinctive thanks to the named software targets, but it only covers a single action and provides no 'Use when' trigger guidance. Adding an explicit trigger clause and one or two more concrete capabilities (e.g., presets, ray-tracing, publication-quality figures) would lift completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants publication-quality or photorealistic molecular images, mentions PyMOL or ChimeraX, or asks to render a protein/structure figure.'

Enumerate 1-2 more concrete actions (e.g., 'apply ray-tracing, depth of field, and cinematic lighting presets; output ready-to-run .pml/.cxc scripts') to raise specificity.

Include natural synonyms like 'molecular visualization', 'protein structure figures', and 'journal cover images' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Generate photorealistic rendering scripts for PyMOL and UCSF ChimeraX" names the domain (molecular rendering for two specific tools) and one concrete action (generate rendering scripts), but stops there — no mention of ray-tracing, presets, lighting, or publication workflows. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; it is above score 2 because a concrete action is stated, but below score 4 because only a single action is covered.

3 / 5

Completeness

The 'what' is clear — generate photorealistic rendering scripts for two named tools — but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description. Per the judging guideline, a missing explicit trigger clause caps completeness at 3, matching the anchor 'Has a clear what but when is missing or only weakly implied'; it cannot be 4 because zero 'when' guidance exists.

3 / 5

Trigger Term Quality

"photorealistic", "rendering scripts", "PyMOL", and "UCSF ChimeraX" are all terms a user with this need would naturally say — the software names in particular are strong triggers. A few natural terms are missing ("molecular visualization", "protein structure", "publication figures"), which keeps it just below the comprehensive coverage of score 5 but above score 3's 'missing common variations' since the dominant triggers are present.

4 / 5

Distinctiveness Conflict Risk

The pairing of "PyMOL and UCSF ChimeraX" with "photorealistic rendering scripts" carves out a clear niche with minimal overlap risk — virtually no other skill would trigger on a request to render a molecular structure in these tools. This matches the score-5 anchor 'Clear niche with distinct triggers; minimal conflict risk'; score 4 would require actual overlap with a closely related skill, which is not evident.

5 / 5

Total

15

/

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/3d-molecule-ray-tracer/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.