AB hazop-node-analysis-worksheet
Use this skill when a process-safety team wants to draft, run, or review one IEC 61882 / CCPS HAZOP node worksheet. Covers node definition, design intent, guideword-by-parameter deviations, cause/consequence/safeguard chains, risk scoring, LOPA flags, recommendations, and HAZOP chair review boundaries.
Covers node definition, design intent, guideword-by-parameter deviations, cause/consequence/safeguard chains, risk scoring, LOPA flags, recommendations, and…
As a process B 74/100 · Nearly there — weak spots: running it twice
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5485 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 74/100
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 5 branches
- 70Execution cost. Instruction body is 5485 tokens
- 85Steps. 46 steps, 1 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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)
- +1No license
- +2Single-language instructions
- +3Description length 303: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 46 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.