aida
Scanned@AK-Khalis
npx machina-cli add skill @AK-Khalis/aida --openclawAIDA 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.
Overview
AIDA provides a conversational interface to an AI-driven smart building platform. It lets you fetch live building status, control devices like lights, shades, and HVAC, optimize objectives for comfort or energy, and run diagnostics through secure REST endpoints.
How This Skill Works
Users issue natural language intents (status, control, optimize, diagnostics). The skill maps each intent to a REST call (GET /status, POST /control, POST /optimize, GET /diagnostics) using bearer token authentication, parses the API response, and returns a concise, actionable result.
When to Use It
- You need a quick view of the current building status
- You want to adjust devices (lights, shades, HVAC) via chat
- You aim to optimize objectives like comfort or energy usage
- You need to run preventive diagnostics on a zone or system
- You require authenticated, remote control of building systems
Quick Start
- Step 1: Say a command to AIDA (status, control, optimize, or diagnostics).
- Step 2: AIDA authenticates and calls the matching REST endpoint (GET /status, POST /control, POST /optimize, GET /diagnostics).
- Step 3: Review the response and take any required follow-up actions.
Best Practices
- Always verify the bearer token is valid before issuing requests
- Use precise device IDs, zones, and targets (e.g., floor/zone) in commands
- Confirm status before applying controls to avoid unintended changes
- Limit optimization requests to specific objectives and time windows
- Handle API error responses gracefully and retry with proper backoff
Example Use Cases
- AIDA, what's the building status?
- Turn off lights on floor 3.
- Optimize for energy savings across the building.
- Run diagnostics on this zone.
- Set HVAC to 72 degrees in Zone 2.