dakboard
PassAudited by ClawScan on May 1, 2026.
Overview
The skill is coherent with its DAKboard management purpose and only shows expected use of a DAKboard API key to list or update devices and push display data.
Before installing, make sure you are comfortable giving the skill access to your DAKboard API key and allowing it to update screens or push display data when you ask it to. Avoid sending sensitive information as metrics or fetch data unless you intend it to appear on DAKboard.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Anyone or any agent process using this skill with the API key can interact with the user's DAKboard account within the API's permissions.
The skill needs account-level API credentials for DAKboard. This is expected for the stated integration, but the user should understand that the key authorizes actions against their DAKboard account.
Before using this skill, you must set your DAKboard API key as an environment variable.
Use a dedicated or least-privileged DAKboard API key if available, keep it out of logs and shared environments, and revoke it if the skill is no longer needed.
If invoked with the wrong device or screen ID, the skill could change what appears on a DAKboard display.
The script includes mutating API operations that can update a device's displayed screen, which is purpose-aligned but should be user-directed.
cmd_update_device(args): ... make_request("PUT", f"/devices/{device_id}", data={"screen_id": args.screen_id})Review device IDs and screen IDs before requesting updates, especially for shared or public displays.