SKILLEMALL.ai
GitHub ↗ RU Sign in

BC bionemo-nims

Run NVIDIA BioNeMo NIMs through the hosted scientific_capability tool with your own NVIDIA API key. Boltz-2 and OpenFold2/OpenFold3 structure prediction, MSA Search alignments, DiffDock docking, ProteinMPNN sequence design, RFdiffusion backbones, GenMol and MolMIM molecule generation, Evo 2 genomic sequence modeling. Use when a request names one of these models, "BioNeMo", "NIM", or asks for a hosted structure, docking or design prediction; not for self-hosted containers on Modal (see protein-binder-design).

synthetic-sciences/OpenScience Hermes author: synthetic-sciences Apache-2.0 1 file body ≈ 795 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Run NVIDIA BioNeMo NIMs through the hosted scientificcapability tool with your own NVIDIA API key.

As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

IntegrationDesigntype 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%
77
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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.
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 513 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "summary"
  • note frontmatter-key unknown frontmatter key "role"

Process rating: all ten parameters 56/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 30Running it twice. 1 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 6 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 795 tokens
  • 100Progress reporting. Reports progress

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
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 513: enough signal without eating the budget
  • +4Structure: 4 headings
  • +3Step-by-step instructions: 6 items
  • +1License stated

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