CF scientific-schematics
Create publication-quality scientific diagrams using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.1 Pro Preview for quality review. Only regenerates if quality is below threshold for your document type. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.
Create publication-quality scientific diagrams using Nano Banana 2 AI with smart iterative refinement.
As a process F 32/100 · No process to follow — References files that are not bundled: references/diagram_types.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
medium Dangerous commands
cmd-shell-rcreferences/QUICK_REFERENCE.md:12Writes to a shell startup fileecho 'export OPENROUTER_API_KEY="sk-o…key"' >> ~/.bashrc # or ~/.zshrc
-
medium Dangerous commands
cmd-shell-rcreferences/README.md:250Writes to a shell startup fileecho 'export OPENROUTER_API_KEY="your_key"' >> ~/.bashrc
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Edit Bash
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5751 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/diagram_types.md
Process rating: all ten parameters 32/100
- 0Tools and files. 1 referenced file(s) missing: references/diagram_types.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 6 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Steps. 162 steps, 6 vague phrases
- 70Execution cost. Instruction body is 5751 tokens
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -32 of 3 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 355: enough signal without eating the budget
- +4Structure: 48 headings
- +3Step-by-step instructions: 162 items
- +4Has examples (21 code blocks)
- +4Reference files are cited in the instructions (1 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.