Engine

v1.0.0

Rule engine reference — decision tables, Rete algorithm, forward/backward chaining, and business rule management. Use when evaluating business rules, buildin...

⭐ 0· 162·1 current·1 all-time

bybytesagain4@xueyetianya

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

high confidence

✓

Purpose & Capability

The name/description (rule engine reference) matches the included assets: an instruction-only SKILL.md and a bash script that prints documentation sections. There are no unrelated environment variables or external binaries required.

✓

Instruction Scope

SKILL.md instructs the agent to run local commands (scripts/script.sh <command>) which correspond to the documented cmd_* functions in the provided script. The only configuration mentioned is ENGINE_DIR (~/.engine/), which is reasonable for local data storage. The visible instructions do not ask the agent to read unrelated files, call external endpoints, or access secrets.

✓

Install Mechanism

No install spec is provided (instruction-only), so nothing is downloaded or written to disk by an installer. The packaged bash script is run locally; this is low-risk but still requires the user to execute local code.

✓

Credentials

The skill declares no required environment variables or credentials. The single configuration variable ENGINE_DIR is appropriate for a documentation/tooling skill and is proportionate to the stated purpose.

✓

Persistence & Privilege

The skill is not forced-always and is user-invocable (normal). It does not request elevated privileges in the visible code and does not modify other skills or global agent settings.

Assessment

This skill appears to be a local documentation/reference tool implemented as a bash script and is coherent with its description. Before installing or running it, inspect the full scripts/script.sh (the provided snippet is large and was truncated here) to confirm there are no network calls, file writes to sensitive locations, or shell commands that execute other binaries with elevated privileges. Run the script in a sandbox or container if you want to be cautious. If you plan to let an agent invoke this autonomously, remember it will execute a local shell script—avoid granting the agent elevated OS privileges and verify the repo/author (bytesagain.com) if you need provenance.

Like a lobster shell, security has layers — review code before you run it.

latestvk97c2j9ptw1m03srvxs7yy9ceh83bxzr

162downloads

0stars

1versions

Updated 1mo ago

v1.0.0

MIT-0

Engine — Rule Engine & Decision Logic Reference

Quick-reference skill for rule engines, decision tables, and business rule patterns.

When to Use

Implementing business rules that change frequently
Building decision trees or scoring systems
Choosing between rule engine approaches
Designing policy engines for access control or pricing
Separating business logic from application code

Commands

`intro`

scripts/script.sh intro

Overview of rule engines — types, benefits, when to use.

`patterns`

scripts/script.sh patterns

Rule engine patterns — forward chaining, backward chaining, Rete.

`tables`

scripts/script.sh tables

Decision tables — structure, completeness, and implementation.

`dsl`

scripts/script.sh dsl

Domain-specific languages for rules — syntax approaches and examples.

`tools`

scripts/script.sh tools

Rule engine tools — Drools, OPA, json-rules-engine, and more.

`scoring`

scripts/script.sh scoring

Scoring and ranking engines — weighted rules, multi-criteria decisions.

`testing`

scripts/script.sh testing

Testing rule engines — coverage, conflict detection, regression.

`checklist`

scripts/script.sh checklist

Rule engine implementation checklist.

`help`

scripts/script.sh help

`version`

scripts/script.sh version

Configuration

Variable	Description
`ENGINE_DIR`	Data directory (default: ~/.engine/)

Powered by BytesAgain | bytesagain.com | hello@bytesagain.com

Comments

Loading comments...