AA research-project-designer
Use this skill for ANY task involving Computer-Aided Drug Design (CADD), computational chemistry, structural bioinformatics, molecular modeling, or AI-driven drug discovery. Trigger whenever the user mentions: docking, binding pockets, MD simulation, molecular dynamics, SASA, electrostatics, Poisson- Boltzmann, PDB files, force fields, AlphaFold, protein-ligand interaction, druggability, free energy perturbation (FEP), cryptic pockets, desolvation penalty, pharmacophore, or asks to design/audit/debug any computational biology or biophysics workflow — even if they don't explicitly frame it as a "research design" task. Also trigger when the user shares NumPy/MDAnalysis/ RDKit/OpenMM code and asks for optimization, debugging, or peer review.
As a process A 81/100 · Runs to the end — weak spots: progress reporting
How to improve
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 81/100
- 0Progress reporting. Says nothing while it works
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 995 tokens
- 100Running it twice. No mutating operations
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)
- +1No license
- +2Single-language instructions
- +3Description length 748: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 7 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.