AF doe-plan
Evidence-backed bioprocess DOE planning for fermentation and upstream optimization. Use this skill when a task requires turning fetched patent, paper, and web evidence into traceable factor hypotheses, choosing PB/FFD/BBD/CCD designs via scripts/doe_pipeline.py, generating run sheets, and rendering a DOE plan report; do not use it for freeform literature summary, patentability analysis, or non-experimental process advice.
As a process F 71/100 · Will not run — References files that are not bundled: ../mcp-setup/PATSNAP_MCP_SETUP.md, ../docs/companion-private-source.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../mcp-setup/PATSNAP_MCP_SETUP.md - warning
missing-refreference to a missing file: ../docs/companion-private-source.md
Process rating: all ten parameters 71/100
- 0Tools and files. 2 referenced file(s) missing: ../mcp-setup/PATSNAP_MCP_SETUP.md, ../docs/companion-private-source.md
- 0Progress reporting. Says nothing while it works
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 83 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2057 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 425: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 83 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +3All 5 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.