SKILLEMALL.ai
GitHub ↗ RU Sign in

BD datamol

Pythonic wrapper around RDKit with simplified interface and sensible defaults. Preferred for standard drug discovery including SMILES parsing, standardization, descriptors, fingerprints, clustering, 3D conformers, parallel processing. Returns native rdkit.Chem.Mol objects. For advanced control or custom parameters, use rdkit directly.

synthetic-sciences/OpenScience Hermes author: synthetic-sciences Apache-2.0 7 files body ≈ 4 605 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Pythonic wrapper around RDKit with simplified interface and sensible defaults.

As a process D 40/100 · Unfinished process — References files that are not bundled: =[O:2]

ProcedureExcelData and analyticstype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
B
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
76
Run on models
none yet
Process rating
D
40/100
Unfinished process
References files that are not bundled: =[O:2]
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 336 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning missing-ref reference to a missing file: =[O:2]
  • note frontmatter-key unknown frontmatter key "dependencies"

Process rating: all ten parameters 40/100

Will not run. References files that are not bundled: =[O:2]
  • 0Tools and files. 1 referenced file(s) missing: =[O:2]
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 70Execution cost. Instruction body is 4605 tokens
  • 85Steps. 44 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. No mutating operations
  • low 11 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 336: enough signal without eating the budget
  • +4Structure: 25 headings
  • +3Step-by-step instructions: 44 items
  • +4Has examples (40 code blocks)
  • +4Reference files are cited in the instructions (6 of 6)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.