AD iaiops-water
Water-treatment edition of iaiops — waterworks / wastewater plants / pump stations: Modbus-TCP/RTU (dosing skids, analyzers, flow meters), OPC-UA (plant SCADA / PLC read), HART-IP process instrumentation (pH, turbidity, conductivity, level, flow transmitters), plus the cross-protocol brain (downtime root-cause, data quality watchdog, OEE). Use when the task mentions water treatment, 水处理, 水厂, 污水, pH, 浊度, turbidity, 电导率, conductivity, dissolved oxygen, 加药, dosing pump, 泵站, pump station, aeration / 曝气, or lift station. Read-first; this edition's tool surface is read-only.
Water-treatment edition of iaiops — waterworks / wastewater plants / pump stations: Modbus-TCP/RTU (dosing skids, analyzers, flow meters), OPC-UA (plant SCADA…
As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 49): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 45/100
- 0Result and completion. Does not say what the result is
- 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. 1 mutating operations with no state check
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 34 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1584 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
- +1No license
- +2Single-language instructions
- +3Description length 575: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 34 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.