SKILLEMALL.ai
GitHub ↗ RU Sign in

BB binding-affinity

Empirical affinity estimates, ligand energy inspection, docking-score consensus, and batch virtual screening. Full MM/GBSA requires a validated external workflow.

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

Empirical affinity estimates, ligand energy inspection, docking-score consensus, and batch virtual screening.

As a process B 72/100 · Nearly there — weak spots: inputs and preconditions

ProcedureInfrastructureSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
B
72/100
Nearly there
Inputs and preconditions w 11
0
When it triggers w 12
50
Failures and branches w 10
50
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.
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 162 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "dependencies"
  • note edit-residue the text marks something as outdated (lines 272): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 72/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. No external tools needed
  • 100Steps. 32 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2774 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress
  • low 10 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
  • -41 reference files, but SKILL.md never points to them: the model will not open them
  • -31 of 5 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 162: enough signal without eating the budget
  • +4Structure: 26 headings
  • +3Step-by-step instructions: 32 items
  • +3Output format is stated explicitly
  • +4Has examples (9 code blocks)
  • +1License stated

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