← Back to Skills Marketplace
Trigger Evaluator
by
EcosincronIA
· GitHub ↗
· v1.0.0
· MIT-0
291
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install trigger-evaluator
Description
Evaluate real OpenClaw trigger rules against the current database state. Use for heartbeat-style trigger checks, especially stale mission detection backed by...
Usage Guidance
This skill will run a production engine script from a hardcoded user workspace and run docker exec to query your DB container, but it does not declare those dependencies. Before installing: 1) Review the actual engine script at /home/cmart/.openclaw/workspace/scripts/stale_missions_engine.sh to confirm it is safe and idempotent. 2) Ensure you are comfortable granting the agent access to Docker (docker CLI and Docker daemon) and that the container name 'supabase-db' and DB credentials are correct for your environment. 3) Prefer a version that documents required binaries/env vars (docker, path to engine) or that bundles a read-only inspect-only mode if you only want to view trigger definitions. If you cannot inspect the engine or do not want the agent to execute production scripts, do not install or run the evaluate command.
Capability Analysis
Type: OpenClaw Skill
Name: trigger-evaluator
Version: 1.0.0
The skill is a specialized administrative utility designed to evaluate and inspect database trigger rules within an OpenClaw workspace. The primary script, scripts/trigger-evaluator.sh, acts as a wrapper for a local engine script and uses 'docker exec' to perform read-only queries against a Supabase PostgreSQL container. It demonstrates good security practice by using strict string comparison to validate the trigger name, effectively preventing command or SQL injection. While it contains a non-portable hardcoded path (/home/cmart/), its logic is transparent, limited in scope, and aligns perfectly with the stated purpose in SKILL.md.
Capability Assessment
Purpose & Capability
The skill claims to 'wrap' the real stale_missions_engine and to inspect trigger rows, which aligns with its name. However it hardcodes a workspace path (/home/cmart/.openclaw/workspace) and a production engine path rather than declaring that it requires access to that workspace or the engine. It also assumes a specific Docker container name and DB credentials. Those hardcoded assumptions are not proportional to the stated, narrow purpose and reduce transparency.
Instruction Scope
The evaluate command execs the production engine script directly (exec "$ENGINE"). That script is not bundled here; running it may read other files, mutate the database, send alerts, or perform network operations beyond simple evaluation. The SKILL.md describes only 'evaluate' and 'inspect' but does not warn that the engine may have side effects. The inspect command runs docker exec psql to read the trigger rule row which matches the described inspect purpose.
Install Mechanism
This is an instruction-only skill with no install spec, so nothing will be written to disk by an installer. That is the lower-risk option for installation mechanism.
Credentials
The skill declares no required environment variables or binaries, but the script implicitly requires: access to /home/cmart/.openclaw/workspace, an executable engine at that path, and the docker CLI plus permission to talk to the Docker daemon (to run docker exec against 'supabase-db'). It also hardcodes DB_USER/DB_NAME and a container name. These implicit privileges and hardcoded credentials are disproportionate and undocumented.
Persistence & Privilege
The skill does not request 'always: true' and is user-invocable only. Autonomous invocation is allowed (platform default). Coupled with the ability to exec a production engine script, this gives the skill potential to perform impactful actions if run autonomously — not a direct configuration flag but an operational risk to consider.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install trigger-evaluator - After installation, invoke the skill by name or use
/trigger-evaluator - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of the trigger-evaluator skill:
- Evaluates real OpenClaw trigger rules using the current database state.
- Supports "stale_missions_alert" trigger detection based on public.openclaw_* tables.
- Wraps the production script stale_missions_engine.sh for reliability.
- Includes commands to run evaluations and inspect current trigger rows.
- Does not introduce or invent new trigger logic; strictly follows implemented workspace logic.
Metadata
Frequently Asked Questions
What is Trigger Evaluator?
Evaluate real OpenClaw trigger rules against the current database state. Use for heartbeat-style trigger checks, especially stale mission detection backed by... It is an AI Agent Skill for Claude Code / OpenClaw, with 291 downloads so far.
How do I install Trigger Evaluator?
Run "/install trigger-evaluator" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Trigger Evaluator free?
Yes, Trigger Evaluator is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Trigger Evaluator support?
Trigger Evaluator is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Trigger Evaluator?
It is built and maintained by EcosincronIA (@ecosincronia); the current version is v1.0.0.
More Skills