← Back to Skills Marketplace
93
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install monitor-openclaw
Description
OpenClaw-optimized skill for Texas residential electricity shopping, address completion, candidate confirmation, ESIID lookup, usage estimation, plan recomme...
Usage Guidance
This skill appears to implement the advertised Texas electricity address and plan workflows, but it has a hidden requirement: the bundled Python client expects POWERLEGO_API_TOKEN in the environment even though the skill metadata lists no required credentials. Before installing or enabling this skill: (1) verify you trust the POWERLEGO API owner (powerlego.com) and Personalized Energy (personalized.energy); (2) require the publisher to declare the POWERLEGO_API_TOKEN requirement in the skill metadata and explain the token's minimum privileges; (3) understand that user addresses (PII) will be sent to external services for validation and usage/plan lookup; (4) run the skill in a sandboxed environment or with a limited-scoped/test API token first; and (5) ask the developer to surface failure modes (what happens if the token is missing) and to document privacy/retention details. The current mismatch between code and declared requirements is the primary reason this is rated 'suspicious.'
Capability Analysis
Type: OpenClaw Skill
Name: monitor-openclaw
Version: 1.0.1
The skill bundle is a legitimate tool designed for Texas residential electricity plan comparison and monitoring. It utilizes a series of Python scripts (e.g., scripts/fetch_best_plan.py, scripts/powerlego_api.py) to normalize user-provided addresses and interact with the PowerLego API (powerlego.com) to retrieve utility data and energy plans. The instructions in SKILL.md and system_prompt.txt are focused on maintaining a professional advisor persona and preventing the AI agent from leaking technical implementation details or internal diagnostics, which is a standard UX and safety practice. No evidence of malicious intent, unauthorized data exfiltration, or harmful execution was found.
Capability Assessment
Purpose & Capability
The skill's name, description, and scripts align with Texas address normalization, ESIID/usage estimation, and plan lookup. However, the included Python client (scripts/powerlego_api.py) requires a POWERLEGO_API_TOKEN environment variable to call powerlego.com endpoints, yet the skill metadata declares no required environment variables or primary credential — this is inconsistent and unexplained.
Instruction Scope
The SKILL.md instructs the agent to execute local Python scripts that perform network calls to third-party APIs (powerlego.com and personalized.energy). That behavior is coherent with the purpose, but SKILL.md and the user-facing guardrails explicitly forbid revealing internal APIs/tokens, so the runtime will call external services while not exposing or documenting those calls to the user. Also, the runtime instructions do not mention the need for an API token, so running the scripts will fail (or silently error) without that secret.
Install Mechanism
There is no install spec (instruction-only style) and code files are bundled. No external binary downloads or extraction steps are specified. Risk is moderate because bundled executable Python scripts will be run, but there is no opaque installer URL or third-party package pulls.
Credentials
The code reads a sensitive environment variable named POWERLEGO_API_TOKEN (and enforces its presence). The skill metadata did not declare any required env vars or a primary credential. Asking for a single service API token would be proportionate for plan lookups, but the omission in metadata is a transparency problem. Additionally, the scripts will transmit user-supplied addresses (PII) to external endpoints (powerlego.com and personalized.energy), so the user should expect address data to leave their environment.
Persistence & Privilege
The skill is not marked always:true, does not request persistence or system-wide configuration changes, and does not declare writes to other skills' configs. It behaves as a normal user-invocable skill.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install monitor-openclaw - After installation, invoke the skill by name or use
/monitor-openclaw - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
- Refined operating style and user-facing voice: now enforces a strict, advisor-led experience for Texas electricity workflows, with no technical or backend language exposed.
- Implements state-machine order: step-by-step intent recognition, address normalization, candidate confirmation, and downstream plan or monitoring actions.
- Requires exact candidate confirmation before plan recommendations or URL generation.
- New rule sets for user interactions: only concise, concrete next steps and one follow-up for missing info.
- Strengthened data contract: mandates use of normalized script outputs; forbids showing raw APIs or diagnostics to users.
- Use this variant when strict workflow branching and fixed response shapes are required.
Metadata
Frequently Asked Questions
What is Monitor?
OpenClaw-optimized skill for Texas residential electricity shopping, address completion, candidate confirmation, ESIID lookup, usage estimation, plan recomme... It is an AI Agent Skill for Claude Code / OpenClaw, with 93 downloads so far.
How do I install Monitor?
Run "/install monitor-openclaw" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Monitor free?
Yes, Monitor is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Monitor support?
Monitor is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Monitor?
It is built and maintained by catkennel (@catkennel); the current version is v1.0.1.
More Skills