← Back to Skills Marketplace
2065
Downloads
1
Stars
1
Active Installs
2
Versions
Install in OpenClaw
/install aida
Description
Conversational interface for AIDA to get building status, control devices, optimize objectives, and run diagnostics via secure REST APIs.
README (SKILL.md)
AIDA Skill for OpenClaw
Skill Name
aida
Description
Conversational interface for AIDA (AI-driven smart building automation platform).
Supported Intents
- aida.status → Get live building status
- aida.control → Control devices (lights, shades, HVAC)
- aida.optimize → Optimize building objectives
- aida.diagnostics → Run preventive diagnostics
Example Utterances
- "AIDA, what's the building status?"
- "Optimize for energy savings."
- "Turn off lights on floor 3."
- "Run diagnostics on this zone."
AIDA Objectives Mapping
- Comfort Optimization
- Energy Optimization
- Preventive Maintenance
API Expectations
The skill expects AIDA to expose REST endpoints:
- GET /status
- POST /control
- POST /optimize
- GET /diagnostics
All calls are authenticated via bearer token.
Usage Guidance
This skill implements HTTP calls to an AIDA API and requires two environment variables (AIDA_API_URL and AIDA_API_KEY), but the registry metadata and SKILL.md do not declare those names — a mismatch you should resolve before installing. Before you proceed: (1) verify and update the SKILL.md/manifest to list required env vars and intended endpoint(s); (2) ensure AIDA_API_URL points to a trusted internal HTTPS endpoint (not an arbitrary public server); (3) store the API key securely (do not put it in a broadly-scoped env if other skills/processes can read it); (4) review the included index.js yourself (it only performs simple fetch calls) and confirm you trust the package owner; (5) confirm how your OpenClaw runtime will install node dependencies. If you cannot confirm the intended AIDA host and secure handling of the API key, do not install or run the skill.
Capability Analysis
Type: OpenClaw Skill
Name: aida
Version: 1.0.0
The skill bundle is benign. It provides a conversational interface to an AIDA smart building platform, making authenticated API calls to a configurable endpoint (`AIDA_API_URL`) using an environment variable for the API key (`AIDA_API_KEY`) as seen in `skills/aida/index.js`. This network access is essential for its stated purpose. There is no evidence of data exfiltration, malicious execution, persistence mechanisms, prompt injection attempts in `SKILL.md`, or obfuscation. Dependencies are standard and legitimate (`node-fetch` in `package.json`).
Capability Assessment
Purpose & Capability
SKILL.md and the code both implement an AIDA building-management integration (status, control, optimize, diagnostics) which is coherent with the skill name. However the registry metadata lacked a description and did not declare any required credentials or env vars, while the code clearly expects AIDA_API_URL and AIDA_API_KEY.
Instruction Scope
The runtime instructions say calls are authenticated via a bearer token and expect REST endpoints; they do not name the exact environment variables or say how the token is supplied. The code actually reads process.env.AIDA_API_URL and process.env.AIDA_API_KEY — the missing declaration is scope creep/omission and could lead to surprising secret access if the operator sets those env vars globally.
Install Mechanism
There is no install spec (instruction-only), but the package.json lists a single dependency (node-fetch). This is lightweight and expected for a JS HTTP client; the lack of an install step means runtime dependency resolution/packaging is up to the platform and should be verified.
Credentials
The code requires two environment values (AIDA_API_URL and AIDA_API_KEY) but the skill registry metadata declares no required env or primary credential. Requesting a bearer token for API access is reasonable for this purpose, but the omission of these env vars from the metadata is inconsistent and increases risk of accidental secret exposure or misconfiguration.
Persistence & Privilege
The skill is not always-enabled and uses the platform default of allowing autonomous invocation; it does not request persistent system-level privileges or modify other skills. No unusual persistence or privilege escalation was observed.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install aida - After installation, invoke the skill by name or use
/aida - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
AIDA Skill 1.0.1 Changelog
- Expanded SKILL.md with a summary and use case details for enterprise smart buildings.
- Clarified supported contexts (live demos, pilot deployments, production integration).
- Improved phrasing and API expectations for better clarity and alignment with AIDA's objectives.
- Minor documentation updates in README.md and manifest metadata.
v1.0.0
Initial release of the AIDA conversational skill for OpenClaw:
- Provides a conversational interface for AIDA's smart building automation.
- Supports live status queries, device control, building optimization, and preventive diagnostics.
- Maps intents to AIDA objectives: comfort, energy, and maintenance.
- Integrates with AIDA via REST endpoints requiring bearer token authentication.
- Includes sample utterances for quick start.
Metadata
Frequently Asked Questions
What is aida?
Conversational interface for AIDA to get building status, control devices, optimize objectives, and run diagnostics via secure REST APIs. It is an AI Agent Skill for Claude Code / OpenClaw, with 2065 downloads so far.
How do I install aida?
Run "/install aida" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is aida free?
Yes, aida is completely free (open-source). You can download, install and use it at no cost.
Which platforms does aida support?
aida is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created aida?
It is built and maintained by AK-Khalis (@ak-khalis); the current version is v1.0.0.
More Skills