← Back to Skills Marketplace
239
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install blueair-openclaw-skill
Description
Use when managing Blueair air purifiers, checking indoor air quality, or responding to respiratory discomfort complaints. Acts as a domain expert for indoor...
README (SKILL.md)
Blueair Expert (Indoor Air Quality Specialist)
You are a senior specialist in indoor air quality and Blueair hardware. Your goal is to help the user maintain a healthy breathing environment with minimal friction.
Core Capabilities
- Environmental Insight: Interpret PM2.5, VOC, Temperature, and Humidity data correctly.
- Device Mastery: Control fan speed, auto mode, child lock, and standby states.
- Proactive Health: Suggest actions when sensors detect poor air quality, even if the user didn't ask directly.
Rules for Interaction
1. Unified Household View
When asked about status, always run the local CLI script:
node dist/get_status.js
Aggregate the results into a concise "household summary" rather than listing technical JSON.
2. Expert Interpretation (Non-Technical)
Do not just report numbers. Translate them into health impact:
- PM2.5 \x3C 12: Excellent
- PM2.5 12-35: Good
- PM2.5 35-75: Moderate (Suggest turning on)
- PM2.5 > 75: Unhealthy (Strongly suggest maximum speed)
3. Contextual Reasoning
If the user says they are "sleepy" or "stuffy", check VOC and CO2 (if available) or simply check if the fan is in Auto mode.
Workflow Patterns
Checking Status
- Run
node dist/get_status.jsinside the skill directory. - Summarize: "Room [A] is Excellent, Room [B] is a bit stuffy (High VOC)."
- Suggest: "Shall I boost the fan in Room [B]?"
Implementing Controls
- Confirm the intent.
- Run
node dist/set_state.js \x3Cuuid> \x3Cattribute> \x3Cvalue>with appropriate UUID and mapping:- "Turn off" ->
node dist/set_state.js \x3Cuuid> standby true - "Auto mode" ->
node dist/set_state.js \x3Cuuid> automode true - "Max speed" ->
node dist/set_state.js \x3Cuuid> fanspeed 3(check model-specific speed ranges, typically 1-3)
- "Turn off" ->
Pre-requisites & Auth
If the script returns a "Credentials missing" error, politely ask the user to provide their Blueair login email and region, or guide them to configure ~/.blueair/config.json.
Usage Guidance
This package appears to be a legitimate Blueair client, but there are a few things to check before installing:
- Source trust: the skill's Source/Homepage is unknown. Prefer skills published from a known Github/org or author. Ask the publisher for provenance or a repo link.
- Install behavior: although the registry says 'instruction-only', the bundle contains package.json and compiled JS — you will need to run 'npm install' which will install dependencies from the public npm registry. Review package-lock.json if supply-chain risk concerns you.
- Credentials: the scripts read credentials from ~/.blueair/config.json (plaintext) or BLUEAIR_USERNAME/PASSWORD env vars. Consider using a dedicated low‑privilege Blueair account or using env vars and a secure secrets store rather than a plaintext file.
- Network endpoints: the code talks to Gigya and Blueair API Gateway endpoints (config.js contains public Gigya API keys and AWS API IDs). That is expected for this client, but verify these endpoints look correct for Blueair and that no other unexpected remote hosts are contacted.
- Proactive actions: the agent is designed to suggest/perform actions (e.g., change fan speed) when it detects poor air quality. Confirm you want an agent that can take actions without an explicit command, or require confirmation before changing device state.
If you want higher assurance: request the upstream repository URL and a reproducible build, manually audit scripts/api/, or run test-login.js with a throwaway Blueair account in an isolated environment to observe behavior. If you are uncomfortable with installing npm packages or storing credentials in plaintext, do not install the skill.
Capability Analysis
Type: OpenClaw Skill
Name: blueair-openclaw-skill
Version: 0.1.1
The skill bundle is a legitimate tool for managing Blueair air purifiers via an MCP server or CLI scripts. It interacts with official Blueair/Gigya endpoints (e.g., accounts.us1.gigya.com and execute-api.us-east-2.amazonaws.com) to authenticate and control devices. Credentials are handled locally through environment variables or a configuration file (~/.blueair/config.json), and the SKILL.md instructions are strictly aligned with the stated purpose of air quality management. No evidence of data exfiltration, malicious execution, or harmful prompt injection was found.
Capability Assessment
Purpose & Capability
The code (get_status, set_state, BlueairAwsApi, Gigya client, and region routing) aligns with the stated purpose of managing Blueair devices and reading sensors. The author included Gigya/AWS config (public API keys + API gateway IDs) in config.js which is expected for a client talking to Blueair's cloud APIs. No unrelated cloud providers, exotic binaries, or other service credentials are requested in the code.
Instruction Scope
SKILL.md instructs the agent to run local CLI scripts (node dist/get_status.js and node dist/set_state.js) and to use ~/.blueair/config.json or env vars for credentials. That scope is limited to device status/control. Two items to note: (1) the skill's metadata and README encourage storing username/password in ~/.blueair/config.json (plaintext on disk) which is a privacy risk; (2) SKILL.md says the skill may act proactively (suggest actions even if the user didn't ask), which is behavioral scope creep you should be comfortable with.
Install Mechanism
The registry entry claims 'No install spec — instruction-only', but the package contains package.json, package-lock.json, compiled dist/ files and TypeScript sources — i.e., this is a code bundle that expects 'npm install' and running node scripts. That mismatch is an incoherence: the skill is not purely instruction-only. The install method is npm (dependencies from the public npm registry), which is a moderate trust surface but expected for Node CLI projects. There are no arbitrary URL downloads or inline/extracted archives.
Credentials
The code legitimately requires Blueair account credentials (username/password) and optionally BLUEAIR_REGION; these are proportional to the function. However, the registry metadata listed 'required env vars: none' while SKILL.md indicates 'credentials_required: true' and the scripts read ~/.blueair/config.json or BLUEAIR_USERNAME/PASSWORD. Also the README recommends storing credentials on disk in plaintext; you should be aware of that and prefer env vars or a dedicated low‑privilege account.
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and does not contain code that attempts persistent system-wide changes beyond reading ~/.blueair/config.json and opening network connections to Blueair/Gigya/API Gateway endpoints. It sets up a local MCP server in dist/index.js but that runs only if you start it.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install blueair-openclaw-skill - After installation, invoke the skill by name or use
/blueair-openclaw-skill - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.1
blueair-openclaw-skill v0.1.1
- Added compiled distribution files in the dist/ directory, supporting API clients and CLI scripts for device control and status.
- Updated scripts to use dist/ paths instead of scripts/dist/.
- Enhanced documentation in SKILL.md to specify required credentials and installation steps.
- Clarified instructions for running status and control commands.
- Improved metadata with fields for required credentials and setup steps.
v0.1.0
- Initial release of blueair-expert for managing Blueair air purifiers and interpreting indoor air quality.
- Provides expert summary of household air, translating sensor data (PM2.5, VOC, etc.) into clear health recommendations.
- Supports device control (fan speed, mode changes, standby, child lock) via CLI scripts.
- Offers proactive suggestions based on air quality and user-reported discomfort.
- Guides setup if Blueair credentials are missing.
Metadata
Frequently Asked Questions
What is Blueair Expert?
Use when managing Blueair air purifiers, checking indoor air quality, or responding to respiratory discomfort complaints. Acts as a domain expert for indoor... It is an AI Agent Skill for Claude Code / OpenClaw, with 239 downloads so far.
How do I install Blueair Expert?
Run "/install blueair-openclaw-skill" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Blueair Expert free?
Yes, Blueair Expert is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Blueair Expert support?
Blueair Expert is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Blueair Expert?
It is built and maintained by you96 (@you96); the current version is v0.1.1.
More Skills