SKILLEMALL.ai
GitHub ↗ RU Sign in

CC ginkgo-cloud-lab

Guides protocol selection, input preparation, pricing checks, and browser ordering on Ginkgo Bioworks Cloud Lab (cloud.ginkgo.bio). Applies to cell-free, E. coli, and Pichia protein expression; HiBiT, A280, and LabChip readouts; IVT mRNA/circRNA synthesis; thermal shift assays; Echo-MS methods; SPR target onboarding; plate-reader assay onboarding; and fluorescent pixel art.

K-Dense-AI/claude-scientific-skills Agent Skills author: K-Dense-AI MIT 19 files body ≈ 2 650 tokens Open the sourcegithub.com↗ analyzed 11 h ago

Guides protocol selection, input preparation, pricing checks, and browser ordering on Ginkgo Bioworks Cloud Lab (cloud.ginkgo.bio). Applies to cell-free, E.…

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureInfrastructureAI 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
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
68
Run on models
none yet
Process rating
C
51/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

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 · 0

✓ No critical or high findings

Files scanned: 19. 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")

Process rating: all ten parameters 51/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 3 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Steps. 22 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2650 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
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • -5TODO / placeholder text left in the skill
  • +2Single-language instructions
  • +3Description length 376: enough signal without eating the budget
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 22 items
  • +4Reference files are cited in the instructions (18 of 18)
  • +1License stated

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