← Back to Skills Marketplace
wu-uk

safety-interlocks

by wu-uk · GitHub ↗ · v0.1.0 · MIT-0
cross-platform ✓ Security Clean
77
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install hvac-control-safety-interlocks
Description
Implement safety interlocks and protective mechanisms to prevent equipment damage and ensure safe control system operation.
README (SKILL.md)

Safety Interlocks for Control Systems

Overview

Safety interlocks are protective mechanisms that prevent equipment damage and ensure safe operation. In control systems, the primary risks are output saturation and exceeding safe operating limits.

Implementation Pattern

Always check safety conditions BEFORE applying control outputs:

def apply_safety_limits(measurement, command, max_limit, min_limit, max_output, min_output):
    """
    Apply safety checks and return safe command.

    Args:
        measurement: Current sensor reading
        command: Requested control output
        max_limit: Maximum safe measurement value
        min_limit: Minimum safe measurement value
        max_output: Maximum output command
        min_output: Minimum output command

    Returns:
        tuple: (safe_command, safety_triggered)
    """
    safety_triggered = False

    # Check for over-limit - HIGHEST PRIORITY
    if measurement >= max_limit:
        command = min_output  # Emergency cutoff
        safety_triggered = True

    # Clamp output to valid range
    command = max(min_output, min(max_output, command))

    return command, safety_triggered

Integration with Control Loop

class SafeController:
    def __init__(self, controller, max_limit, min_output=0.0, max_output=100.0):
        self.controller = controller
        self.max_limit = max_limit
        self.min_output = min_output
        self.max_output = max_output
        self.safety_events = []

    def compute(self, measurement, dt):
        """Compute safe control output."""
        # Check safety FIRST
        if measurement >= self.max_limit:
            self.safety_events.append({
                "measurement": measurement,
                "action": "emergency_cutoff"
            })
            return self.min_output

        # Normal control
        output = self.controller.compute(measurement, dt)

        # Clamp to valid range
        return max(self.min_output, min(self.max_output, output))

Safety During Open-Loop Testing

During calibration/excitation, safety is especially important because there's no feedback control:

def run_test_with_safety(system, input_value, duration, dt, max_limit):
    """Run open-loop test while monitoring safety limits."""
    data = []
    current_input = input_value

    for step in range(int(duration / dt)):
        result = system.step(current_input)
        data.append(result)

        # Safety check
        if result["output"] >= max_limit:
            current_input = 0.0  # Cut input

    return data

Logging Safety Events

Always log safety events for analysis:

safety_log = {
    "limit": max_limit,
    "events": []
}

if measurement >= max_limit:
    safety_log["events"].append({
        "time": current_time,
        "measurement": measurement,
        "command_before": command,
        "command_after": 0.0,
        "event_type": "limit_exceeded"
    })

Pre-Control Checklist

Before starting any control operation:

  1. Verify sensor reading is reasonable

    • Not NaN or infinite
    • Within physical bounds
  2. Check initial conditions

    • Measurement should be at expected starting point
    • Output should start at safe value
  3. Confirm safety limits are configured

    • Maximum limit threshold set
    • Output clamping enabled
def pre_control_checks(measurement, config):
    """Run pre-control safety verification."""
    assert not np.isnan(measurement), "Measurement is NaN"
    assert config.get("max_limit") is not None, "Safety limit not configured"
    return True

Best Practices

  1. Defense in depth: Multiple layers of protection
  2. Fail safe: When in doubt, reduce output
  3. Log everything: Record all safety events
  4. Never bypass: Safety code should not be conditionally disabled
  5. Test safety: Verify interlocks work before normal operation
Usage Guidance
This is an instruction-only safety guide that appears coherent with its purpose, but treat the code as pseudo-code: add missing imports (e.g., numpy), define current_time/config, and replace assert checks with robust error handling. Thoroughly review and unit/integration-test these interlocks in a safe simulation or test environment before deploying to live equipment. Ensure hardware-level fail-safes and certified safety mechanisms remain in place (software interlocks are complementary, not a substitute). Confirm where safety logs are stored and that log handling does not leak sensitive operational data. If you need higher assurance, have a control-systems engineer or safety auditor review and adapt the snippets to your platform and safety standards.
Capability Analysis
Type: OpenClaw Skill Name: hvac-control-safety-interlocks Version: 0.1.0 The skill bundle provides legitimate documentation and Python code patterns for implementing safety interlocks in HVAC control systems. The code focuses on sensor validation, output clamping, and emergency cutoff logic (SKILL.md), with no evidence of malicious intent, data exfiltration, or prompt injection.
Capability Assessment
Purpose & Capability
The name/description match the SKILL.md content. The instructions focus on safety checks, clamping outputs, logging events, and pre-control checks — all appropriate for an interlocks guidance document. No unrelated services, binaries, or credentials are requested.
Instruction Scope
Instructions remain within scope but are illustrative rather than complete: snippets reference numpy (np), current_time, and config variables without imports/definitions, and use assert statements that could crash a running system. Logging is advised but storage/transport destination is unspecified. These are quality/robustness issues rather than scope creep.
Install Mechanism
No install spec and no code files — instruction-only skill. This minimizes surface area since nothing is downloaded or written to disk by the skill package itself.
Credentials
No environment variables, credentials, or config paths are requested. The guidance expects a local 'config' object and sensor inputs — which is proportional to the stated purpose.
Persistence & Privilege
always is false and the skill does not request persistent/system-level privileges or modifications. Autonomous invocation is allowed by platform default but is not combined with broad access here.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install hvac-control-safety-interlocks
  3. After installation, invoke the skill by name or use /hvac-control-safety-interlocks
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Bulk publish from all-task-skills-dedup
Metadata
Slug hvac-control-safety-interlocks
Version 0.1.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is safety-interlocks?

Implement safety interlocks and protective mechanisms to prevent equipment damage and ensure safe control system operation. It is an AI Agent Skill for Claude Code / OpenClaw, with 77 downloads so far.

How do I install safety-interlocks?

Run "/install hvac-control-safety-interlocks" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is safety-interlocks free?

Yes, safety-interlocks is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does safety-interlocks support?

safety-interlocks is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created safety-interlocks?

It is built and maintained by wu-uk (@wu-uk); the current version is v0.1.0.

💬 Comments