SKILLEMALL.ai
GitHub ↗ RU Sign in

CB pylabrobot

Develops and reviews PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations. Supports PyLabRobot protocols and API questions; keep physical execution behind an explicit operator safety gate.

K-Dense-AI/claude-scientific-skills Agent Skills author: K-Dense-AI MIT 16 files · 7 scripts body ≈ 2 791 tokens Open the sourcegithub.com↗ analyzed 13 h ago

Develops and reviews PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations.

As a process B 70/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice

AnalyzerSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
83/100
safety, quality, tests
Safety 60%
89
Quality 40%
74
Run on models
none yet
Process rating
B
70/100
Nearly there
Inputs and preconditions w 11
30
Running it twice w 4
30
Result and completion w 14
40
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 7

✓ No critical or high findings

Medium and low: 7
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Write Edit Bash
  • low Secrets in code secret-high-entropy-token references/analytical-equipment.md:81
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    `Expe…end` and `ExperimentalSparkBackend`.
    detector
  • low Secrets in code secret-high-entropy-token references/analytical-equipment.md:134
    High-entropy token-like string (may be an id, hash or a credential)
    from pylabrobot.scales import Mett…end
  • low Secrets in code secret-high-entropy-token references/resources.md:46
    High-entropy token-like string (may be an id, hash or a credential)
    hami…ter,
  • low Secrets in code secret-high-entropy-token references/resources.md:60
    High-entropy token-like string (may be an id, hash or a credential)
    tip_carrier[0] = tips = hami…ter(name="tips")
  • low Secrets in code secret-high-entropy-token SKILL.md:151
    High-entropy token-like string (may be an id, hash or a credential)
    hami…ter,
  • low Secrets in code secret-high-entropy-token SKILL.md:162
    High-entropy token-like string (may be an id, hash or a credential)
    tips = hami…ter(name="tips")

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note edit-residue the text marks something as outdated (lines 179): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 70/100

  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 3 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 31 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2791 tokens
  • 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
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -32 of 7 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 250: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 31 items
  • +4Has examples (3 code blocks)
  • +4Reference files are cited in the instructions (7 of 7)
  • +1License stated

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