BF plc-skill
General PLC development, explanation, review, refactoring, debugging, and troubleshooting skill across IEC 61131-3 style industrial control work. Use when the request involves PLC logic, sequence control, state machines, alarms, interlocks, timers, counters, I/O mapping, Structured Text (ST), Ladder Diagram (LD), Function Block Diagram (FBD), Sequential Function Chart (SFC), program structure, code review, maintainability, or commissioning/debugging. Route through the common PLC layer first, then prefer the matching vendor path when the user mentions Mitsubishi, Siemens, Omron, Allen-Bradley/Rockwell, Schneider, Delta, Keyence, Panasonic, Beckhoff, or Codesys ecosystems, software, CPU families, device models, or vendor-specific terminology. Do not prefer this skill for generic electronics, pure wiring-only work without logic context, broad industrial networking without control-program context, or high-confidence safety conclusions without confirmed field conditions.
As a process F 60/100 · Will not run — References files that are not bundled: references/common/scope-and-trigger-rules.md, references/common/task-router.md, references/common/query-to-doc-routing.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.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Dangerous commands
cmd-privilegeINSTALL.md:250Privilege escalation / world-writable permissionssudo chown -R $USER ~/.openclaw/workspace/skills/
Files scanned: 79. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/common/scope-and-trigger-rules.md - warning
missing-refreference to a missing file: references/common/task-router.md - warning
missing-refreference to a missing file: references/common/query-to-doc-routing.md - warning
missing-refreference to a missing file: references/common/plcopen-and-iec-notes.md - warning
missing-refreference to a missing file: references/common/st-style-guide.md - warning
missing-refreference to a missing file: references/common/st-output-style.md - warning
missing-refreference to a missing file: references/common/program-templates.md - warning
missing-refreference to a missing file: references/common/scan-cycle-and-output-ownership.md - warning
missing-refreference to a missing file: references/common/response-fallback-rules.md - warning
missing-refreference to a missing file: references/common/safety-boundaries.md - warning
missing-refreference to a missing file: references/common/vendor-pitfalls-and-pro-tips.md - warning
missing-refreference to a missing file: references/common/version-control-and-code-review.md
Process rating: all ten parameters 60/100
- 0Tools and files. 12 referenced file(s) missing: references/common/scope-and-trigger-rules.md, references/common/task-router.md, references/common/query-to-doc-routing.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 124 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1912 tokens
- 100Running it twice. No mutating operations
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)
- +3Description length 980: 120–800 characters recommended
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 9 headings
- +3Step-by-step instructions: 124 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (4 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.