CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rowan

Cloud-based quantum chemistry platform with Python API. Preferred for computational chemistry workflows including pKa prediction, geometry optimization, conformer searching, molecular property calculations, protein-ligand docking (AutoDock Vina), and AI protein cofolding (Chai-1, Boltz-1/2). Use when tasks involve quantum chemistry calculations, molecular property prediction, DFT or semiempirical methods, neural network potentials (AIMNet2), protein-ligand binding predictions, or automated computational chemistry pipelines. Provides cloud compute resources with no local setup required.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A well-built skill body: consistent, executable workflow examples with a clear submit-wait-fetch pattern, real error-handling guidance, and a verified one-level-deep reference bundle. The main improvements are removing the redundant 'Common Patterns' section, fixing non-executable placeholders (missing stjames install, [x, y, z] pocket), and moving more API detail into the existing reference files.

Suggestions

Add `stjames` to the installation command (e.g., `uv pip install rowan-python stjames`) and replace placeholder values in Pattern 2 (`pocket = {"center": [x, y, z]}` and undefined `compound_library`) with concrete values so every example is copy-paste executable.

Cut the 'Common Patterns' section or reduce it to non-duplicative recipes — Pattern 1 and Pattern 3 restate the Core Workflows examples almost verbatim, padding the token budget without new information.

Move the Workflow Management code and RDKit-native function lists into references/api_reference.md and references/rdkit_native.md, keeping only a pointer in SKILL.md, and add an explicit status check (e.g., `if workflow.status == "failed"`) before accessing `workflow.data` in the main workflow examples.

DimensionReasoningScore

Conciseness

The body is dominated by executable code with almost no explanation of concepts Claude already knows, fitting the 'efficient; minor instances of over-explanation' anchor. The 'Common Patterns' section (Pattern 1 repeats the pKa workflow, Pattern 3 repeats the conformer search) and the marketing-flavored 'Why Rowan' bullets are the trimmable padding that keeps it below score 5.

4 / 5

Actionability

Core workflows give copy-paste-ready code with the full submit → wait_for_result → fetch_latest → access-data cycle, plus install and auth steps, matching score 4 ('minor gaps'). It is not score 5 because some examples are not directly executable: `stjames` is imported throughout but missing from the install command, and Pattern 2 uses placeholders like `pocket = {"center": [x, y, z]}` and an undefined `compound_library`.

4 / 5

Workflow Clarity

Every workflow follows the same explicit submit → wait → fetch → read-data sequence, and the Error Handling section adds status checks ('if workflow.status == "completed"'), a timeout, and exception handling, giving most checkpoints. It falls short of score 5 because the main workflow examples access `workflow.data` without an explicit status/failed check — validation lives only in a separate section — which is the 'minor validation gaps' pattern of score 4, not the absent-validation pattern of score 3.

4 / 5

Progressive Disclosure

The six referenced files (api_reference.md, workflow_types.md, rdkit_native.md, molecule_handling.md, proteins_and_organization.md, results_interpretation.md) all exist, are described inline, and contain no nested pointers, so references are one level deep and well signaled. Score 4 rather than 5 because the body itself carries substantial API detail inline (full Workflow Management code, RDKit function lists, Computational Methods) that belongs in the reference files under the 'content appropriately split' anchor.

4 / 5

Total

16

/

20

Passed

Description

88%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 strong description: concrete capabilities with named tools, an explicit 'Use when...' trigger clause, and third-person voice. Its only weaknesses are the absence of file-extension/synonym triggers and slightly generic quantum-chemistry trigger terms that could overlap with a local DFT skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'pKa prediction, geometry optimization, conformer searching, molecular property calculations, protein-ligand docking (AutoDock Vina), and AI protein cofolding (Chai-1, Boltz-1/2)' — with named tools, matching the comprehensive-coverage anchor. It goes beyond the score-4 anchor ('minor gaps in coverage') by naming specific models and methods; there are no vague filler phrases.

5 / 5

Completeness

It explicitly answers 'what' ('Cloud-based quantum chemistry platform with Python API' plus enumerated capabilities) and 'when' with a concrete trigger clause: 'Use when tasks involve quantum chemistry calculations, molecular property prediction, DFT or semiempirical methods, neural network potentials (AIMNet2), protein-ligand binding predictions, or automated computational chemistry pipelines.' This matches the score-5 anchor; score 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Good natural-term coverage a domain user would actually say: 'quantum chemistry calculations', 'pKa prediction', 'docking', 'conformer searching', 'DFT', 'molecular property prediction'. It falls short of the score-5 anchor, which expects synonyms and file extensions — terms like 'tautomers', 'binding affinity', or '.pdb/.sdf' inputs are absent — but exceeds the score-3 anchor ('missing common variations') since it covers most workflow-level vocabulary.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (a specific cloud platform, with AutoDock Vina, Chai-1, Boltz, AIMNet2 named), but generic triggers like 'tasks involve quantum chemistry calculations' or 'DFT' would also fire for a local quantum-chemistry tool skill, so there is minor overlap risk with closely related skills. That fits the score-4 anchor better than score 5's 'minimal conflict risk'.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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/coding/rowan/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.